Step 08 of 10 4-6 weeks· advanced
Step 8: Pilot with a Subset of Users
Move 5-10% of users to the new app exclusively. Watch their behavior. Fix what breaks. This is where the workflows nobody mentioned (because they were "obvious") surface.
Recommended prompts
Use one of these to do the work in your IDE
Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.
Recommended skills
Drop these into Claude Code for this phase
Skills auto-trigger on the right kind of request. Install once; they apply to every prompt that fits.
Recommended MCP configs
Wire these tools into Claude Code first
MCP servers give Claude Code direct access to external systems (Jira, browsers, databases). Configure once.
When you're done
Verify these in your own work before moving on
This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.
- Pilot users identified, onboarded, supported
- Daily / weekly check-ins with pilot users
- Issues triaged and prioritized
- Fixes deployed
- Pilot user satisfaction acceptable to expand
Common pitfalls
What goes wrong at this step
- No pilot phase — going from internal testing to 100% rollout misses real-world issues
- Pilot users not representative — picking "tech-friendly" users hides issues real users will hit
- Ignoring pilot feedback — if pilot users hate something, real users will too