Let’s be direct about something the industry dances around: a project like this — four structured courses, custom video lessons, full curriculum architecture, learner pathways, and a branded platform handoff — used to take six months and a team twice this size.
It took 12 weeks. Here’s why.
Not because we cut corners. Not because the work was simpler than it sounds. Because our production stack is built around a core principle: AI handles volume, humans handle judgment. When you get that division of labor right, the output is faster, leaner, and better than either side could produce alone.
This is what that looked like in practice.
The framework: content → operations → visibility
Every build TIYL runs is organized around three layers. Not because it’s a clean framework to put on a slide — because these are the three places projects actually break down when there’s no system behind them.
Content is everything a learner sees and engages with: curriculum outlines, lesson scripts, video copy, branded assets. This is where most of the build time lives.
Operations is everything that keeps the build moving: file management, version control, workflow coordination across tools and team members. This is where most projects silently die.
Visibility is knowing where things stand at any given moment: what’s done, what’s in review, what’s blocked, what’s next. This is where leaders lose confidence in a build and start micromanaging — or worse, disappear.
Each layer has a different set of tools. Each tool replaced something that used to eat human hours.
The content layer: Claude + Canva
What it replaced: The traditional creative cycle — brief to outline to draft to revision — that used to take days per lesson.
What it did here:
Claude handled curriculum drafts, lesson outlines, and scripted lesson copy. Not generic AI output — structured prompts built around Sticky Fingers’ brand voice, their operator reality, and the specific learning objectives for each course. Brief to first draft in hours, not days.
Canva absorbed the design volume. Slide templates, branded visual assets, learner-facing materials — all produced at a pace that would have required a dedicated designer and a two-week production queue under the old model.
The combination didn’t replace the creative process. It compressed it. The humans on the project were still making every strategic and editorial call. They just weren’t spending their time on first drafts and asset formatting.
The honest caveat: AI-generated curriculum drafts require careful human review. Tone, accuracy, and the specificity of franchise operating reality don’t emerge from a prompt alone — they come from people who understand what a new franchisee actually needs to know on day one. That review step is not optional, and it’s not fast. But it’s faster than writing from scratch.
The operations layer: workflow tools
What it replaced: The human hours spent on file management, version control, and cross-platform coordination — the invisible overhead that compounds across a 12-week build.
What it did here:
File organization across a large asset library — naming conventions, folder structure, version tracking — was automated rather than manually maintained. On a project with four courses, multiple lesson formats, and two teams working in parallel, the difference between a clean file system and a chaotic one is measured in days, not hours.
Cross-platform coordination between Claude, Google Drive, and LearnWorlds ran through structured workflows rather than ad hoc communication. Assets moved from draft to review to final without manual handoffs slowing down each transition.
The honest caveat: Workflow automation requires upfront setup. The time you save across a 12-week build is real — but someone has to design the system before it runs. That design work is human work, and it matters. A poorly structured workflow automates the chaos rather than eliminating it.
The visibility layer: dashboards
What it replaced: The spreadsheet-based progress tracking that every project eventually defaults to and nobody trusts.
What it did here:
A custom dashboard tracked build progress across the full asset library – which courses were in draft, which were in review, which were complete, and what was blocking anything that wasn’t moving. Both the TIYL team and the Sticky Fingers client had visibility into the same real-time picture.
This matters more than it sounds. On a 12-week build with a client-side team managing approvals and a build team managing production, the most common source of delay isn’t the work — it’s the uncertainty about where the work stands. A dashboard that both sides trust removes that uncertainty. Projects move faster when nobody has to ask for a status update.
The honest caveat: Dashboards are only as useful as the discipline behind them. If the team doesn’t update the status, the visibility is fake. Human accountability is still the operating layer underneath every automation.
What the platform now lets AI do
The build was the foundation. The more interesting question is what the platform enables going forward and here AI’s role expands significantly.
New and expanded courses can be added without starting from scratch. The curriculum architecture, the brand voice, the learner pathways — all of it exists. AI accelerates every future build because the foundation is already set.
Engagement tracking shows who’s completing, who’s falling behind, and where the drop-off is. That data informs future curriculum decisions without requiring a manual audit.
Automations and workflows — progress reminders, completion triggers, certification flows run without human intervention once configured.
Marketing and communications can draw from training content directly. A lesson module becomes a newsletter. A course outline becomes a social series. The training investment pays dividends beyond the platform.
What still came from humans
This is the part most AI-forward case studies skip, and it’s the most important part.
Curriculum strategy. Deciding what a new franchisee needs to know, in what order, at what depth — that’s not a prompt. It requires people who understand the Sticky Fingers operator experience and can design a learning journey that builds real capability, not just information transfer.
Brand voice. The warmth and playfulness that make Sticky Fingers what it is don’t emerge from a generative model. Every piece of content that went into the platform was reviewed against the brand before it was finalized.
Knowing what a franchisee needs on day one. This is the hardest thing to automate and the most valuable thing a build team brings. It’s operational empathy, the ability to design training for the human who will use it under real conditions, not ideal ones.
The AI stack made the build faster, leaner, and more consistent. The humans made it work.
The framework is transferable
Content → operations → visibility. Same stack whether you’re training franchisees, onboarding employees, or educating customers. The tools may shift; the framework doesn’t.
If you’re looking at a training build and trying to figure out where AI fits and where it doesn’t; that’s exactly the conversation we run.
Build the foundation. Let AI scale it. Keep the humans where they matter.
Want to see where AI fits in your training build — and where it doesn’t?
Our team would love to hear what problem you’re currently up against and provide a solution that will move the needle forward and give your team some breathing room.
Connect with us at jade@traininyourlane.com
