A Training Studio's Roadmap, in Progress
Most case studies show a finished project. This one does not, because the work is not finished and will not be for a while. Unjammer runs on its own Lean AI Framework, and every client engagement, including this one, moves through the same five pillars the framework measures: Operations, Team Logic, Succession, Digital Twin, and Client Journey. How long a full Roadmap takes depends on the business: its budget, who does the implementing, and how fast it wants to move. Some finish the scope in a year or less, others take longer. There is no fixed timeline, and it is better to say so plainly than to dress up a partial engagement as a finished one.
The client is a small gym and training studio. The starting point was a full diagnostic: an AI Business Maturity Score of 54 out of 100, placing the studio at the "Automated" tier. The pillar breakdown showed real strength in Operations and Client Journey, moderate ground in Team Logic and Digital Twin, and the biggest gap in Succession, the pillar most owner-dependent businesses score lowest on.
The Roadmap belongs to the client
From the diagnostic, Unjammer built a five-pillar Roadmap and identified five Phase 1 opportunities, ranked by impact and value: a centralized task management system, a digital SOP and knowledge base, screen-recorded video SOPs, an automated membership pause and cancellation form, and a documented decision matrix for common exceptions.
Before any of that started, the first conversation was about alignment, not action. Tasks within a phase can be done in different orders as long as one does not depend on another, so the studio has real say in what happens next. It is their Roadmap, specific to their business, not a fixed plan from us. Many of the actions on it do not require Unjammer to carry them out at all. The owner had already said automating member level assessments was the top priority. The Roadmap agreed in principle but placed it after the foundation work, and the owner agreed to that order going in. That is a "not yet," decided together and up front, not pushback that showed up later.
Pausing before building anything
Once work began, the first action item made something clear: building on an unreviewed tech stack risked creating work that would later need to be undone. Redoing early work is waste, and avoiding waste is the Lean principle the whole framework is built on, pointed at the future instead of the present.
So the first step was a full evaluation of eight tools: three workflow automation platforms (Zapier, Make, and n8n), three task tracking tools (Trello, Notion, and Asana), and the two systems the studio already had, Google Workspace and its CRM. The CRM is built specifically for gyms, training studios, and other club type businesses, and its built-in automations are a real part of why the studio already scored well on Client Journey. The evaluation also settled which AI assistant the studio's workflows should run on: Gemini.
The finding was that the CRM's own task management already covered the need. No new software was purchased. For a team of this size, adding a typical workflow platform and a typical task tool on top of what they already pay for would cost roughly $650 to $1,400 a year, depending on the tiers chosen. That is the pitfall this work is built to catch: a business assumes it has to buy its way into being organized, when the fix is setting up what it already owns. Unjammer was not familiar with the CRM's full range going in, and is using more of it now than the studio had been.
Earning access, not assuming it
Doing any of this required the studio to add Unjammer as a user in its CRM. That took about two weeks. It is a small operational detail, and it is also a real marker: a business only hands over that kind of access once it trusts the person asking.
Where the work stands now
Right now the studio's SOPs are scattered across spreadsheets instead of living in one place. The current work is centralizing them and turning the level assessment checklist, still in Google Sheets today, into an automated version linked to the CRM, so level assessments are consistent and documented rather than dependent on memory or whoever is running that session.
That documentation gap is real, but it is the smaller of the two problems. The bigger one, the one the studio named as its top priority in the AI Blueprint, comes after the checklist. The level assessment requirements themselves are already well defined, so this is not a judgment call. The break is a manual follow-up step: updating the CRM to confirm every requirement is met and set the member up for their assessment. Staff finish the checklist, the follow-up does not always happen, and a member who is ready waits until someone happens to notice. Structuring the data now, so that follow-up can eventually trigger on its own instead of depending on someone remembering, is the reason the foundation work comes first.
Still unfinished, on purpose
As of October 2026, one of the eight Phase 1 action items is complete. This case study will be updated as each of the rest ships, rather than replaced by a new one when the engagement is "done," because it may never be done in the tidy sense. That is not a shortcoming. It is what Foundation First. AI Second. looks like as a process instead of a slogan: diagnose, build a Roadmap the client owns, pause to check the stack before building on it, earn the access needed to do the work, then build the foundation before fixing the step that keeps failing.