Free guide
Start here
What the Path is, how it's organised, which parts are free, and which track to start with.
Free
The Path is the route to Springspot: the point where your design, platform and marketing systems are connected to AI through MCPs, so one operator or a small team can run the store.
The idea under all of it is simple. Set the foundation up right, give AI the rules, then just talk. Most of the Path is about the first two. The talking is the easy part once they’re done.
How the Path is organised
There are five tracks, one for each Springspot checkpoint:
- Design system in Figma
- Connect Claude to Figma
- Platform MCP (Shopify first)
- Marketing MCP (Klaviyo)
- Process mapping and automation
Every track has the same six parts, so once you know your way around one, you know your way around all of them.
| Part | What it covers | Access |
|---|---|---|
| Overview | What the checkpoint is, and why it matters | Free |
| Requirements | What you need in place before you start | Free |
| Build guide | The build, step by step | Paid |
| Templates and assets | Figma files, prompts, MCP configs, process maps | Paid |
| Workflows | Day-to-day recipes once the checkpoint is built | Paid |
| Checklist | What earns a 4, so you know when you’re done | Free |
What’s free, and why
The rule is simple. Anything that explains what or why is free. Anything you could follow step by step to build it is in the Path.
So you can read every overview, every list of requirements and every checklist, across all five tracks, without paying. That’s enough to decide whether this is worth doing, see where you stand, and plan the work.
The build guides, templates and workflows are where the trial and error has already been done for you. That’s what the Path is for.
The recommended order
Design system first. Processes last.
- Design system first, because everything visual depends on it, and connecting AI to design only works when there’s a system for it to follow.
- Connect Claude to Figma straight after, since it’s built directly on the system.
- Platform and marketing can run in either order, or side by side. Start with whichever one costs you the most time today.
- Processes last, because you can’t run a workflow through tools that aren’t connected yet. Writing your workflows down can start any time, though, and it’s worth doing early.
You don’t have to finish one track before starting the next. But a checkpoint built on a missing foundation usually ends up being rebuilt.
Use the Score to pick your starting track
The Springspot Score rates each checkpoint from 0 to 4:
| Rating | Meaning |
|---|---|
| 0 | Not started |
| 1 | Partial, ad hoc |
| 2 | In place, not connected to AI |
| 3 | Connected, used sometimes |
| 4 | Connected and part of how work gets done |
Your total out of 100 gives you a level, and the Score points you at your weakest checkpoint. That’s usually the track to start with.
One exception: if your score lands in Grounded (25 or under), start with the design system, whatever else the Score says. Without it, the other checkpoints have nothing to stand on.
How to work through a track
- Read the overview, and decide whether this checkpoint matters for your store right now.
- Go through the requirements, and collect what’s missing before you build anything.
- Read the checklist before you build, so you know what a 4 looks like.
- Build it, with the build guide, templates and workflows.
- Come back to the checklist, and take the Score again.
Solo or small team
The Path is written for two kinds of operation: a single operator running the whole store, and a director of ecommerce with a couple of operators. The tracks are the same for both. Where the work differs, each overview says how.
Next: take the Score to find your starting track.