| name | journey |
| description | Use this skill when the user is new and doesn't know where to start, asks 'what should I do first,' 'what order do I do things in,' 'where do I begin,' 'I have an idea but don't know what's next,' or seems lost among the available skills. Also use when the user asks for a roadmap or overview of the full process from idea to launched product. This is the starting point — it routes users to the right skill for their current stage. |
The Solo Founder Journey
You don't need to know everything. You need to know what to do next. This skill tells you where you are and what skill to use.
Where Are You?
Find your current stage. Start there — don't skip ahead.
Stage 1: "I have an idea"
You know a problem exists in your field. You haven't validated whether anyone else cares enough to pay.
Do this:
- translate — Turn your professional pain into a clear problem statement
- validate — Test whether other people have this pain and will pay to fix it
Time: 1-2 weeks. Cost: $0-200.
Gate: Do NOT move to Stage 2 until you have signal that real people want this. Signal = email signups, survey responses, or pre-payments. "My friends think it's cool" is not signal.
Stage 2: "I've validated demand — what do I build?"
You have evidence people want this. Now you need to decide what the minimum product looks like.
Do this:
- customer-research — Talk to 10 potential users about their workflow
- prioritize — Decide what to build first (ruthlessly cut scope)
- plan — Write a spec AI tools can execute
Time: 1-2 weeks.
Gate: You should have a written spec that describes what the user sees and does, not a list of features. If your spec takes more than 2-4 weeks to build, cut more.
Stage 3: "I'm ready to build"
You have a spec. Time to choose your tool and build the thing.
Do this:
- brand-identity-generator — Set your visual identity so AI tools don't guess
- build — Choose your AI tool (Lovable, Claude Code, Replit, Cursor) and build
- database — Set up your data model and security
- secure — Security checklist before going live
- compliance — If you're in healthcare, finance, education, or another regulated industry
Time: 2-4 weeks for an MVP.
Gate: The app works. Happy path is functional. You've tested it yourself. It doesn't need to be perfect — it needs to be usable.
Stage 4: "It works — how do I get it live?"
The app works locally or in your dev environment. Time to put it on the internet.
Do this:
- deploy — Get it live on a custom domain
- payments — Set up Stripe for subscriptions
- legal — Terms of Service, Privacy Policy, business entity
- test — Test the full flow as if you're a new user
- monitor — Set up error tracking and uptime alerts
- go-live — Run the pre-launch checklist before letting anyone in
Time: 1-2 days for deploy. 1 week for payments + legal.
Gate: Someone can visit your URL, sign up, use the product, and pay you. go-live is your final checkpoint before opening the doors.
Stage 5: "It's live — how do I get users?"
Your product is live. Nobody knows about it yet.
Do this:
- landing-page — Build a landing page that converts
- copywriting — Write copy that speaks your audience's language
- launch — Plan and execute your launch (not just "post on Twitter")
- niche-advantage — If you're building for your own industry, use your network
- sales — Find and reach your first 10-20 customers directly
Time: 2-4 weeks of active launch effort.
Gate: You have paying customers (even 5-10) and you're learning from their usage.
Stage 6: "I have early customers — how do I grow?"
You have paying customers. Now build the engine.
Do this:
- analytics — Set up tracking so you know what's working
- growth — Design activation, retention, and referral mechanics
- conversion — Optimize your signup and upgrade flows
- email — Build welcome sequences and lifecycle emails
- content — Start creating content that attracts your audience
- seo — Plan content that ranks and drives organic signups
- feedback — Collect and act on user feedback
Time: Ongoing. This is the work from now on.
Stage 7: "I'm growing — how do I keep customers?"
You're acquiring users. Now make sure they stick.
Do this:
- retention — Reduce churn and build stickiness
- support — Build self-serve documentation
- community — If you have 100+ active users, consider a community
- pricing — Revisit pricing as you learn what users value
- optimize — Speed, code cleanup, database performance
Stage 8: "I'm established — how do I scale?"
You have product-market fit. Revenue is growing. Now scale.
Do this:
- ads — Paid acquisition once organic is working
- hiring — When to hire vs. keep using AI tools
- ai-features — Add AI-powered features to differentiate
- accounting — Get your books right as revenue grows
- finances — Financial modeling and unit economics
Quick Reference
| "I need to..." | Use this skill |
|---|
| Figure out if my idea is worth building | translate, validate |
| Decide what to build first | prioritize, plan |
| Choose an AI coding tool | build |
| Set up my database | database |
| Make it look professional | brand-identity-generator, beautify |
| Get it live on the internet | deploy |
| Check if I'm ready to launch | go-live |
| Accept payments | payments |
| Handle legal stuff | legal, compliance |
| Build a landing page | landing-page |
| Write marketing copy | copywriting |
| Plan my launch | launch |
| Reach my first customers | sales, niche-advantage |
| Set up analytics | analytics |
| Grow faster | growth, conversion |
| Write emails that convert | email |
| Create content | content, seo |
| Reduce churn | retention |
| Handle support | support |
| Run ads | ads |
| Hire a developer | hiring |
| Fix a bug | debug |
| Something broke in production | debug, monitor |
| Understand my financials | finances, accounting |
| Set pricing | pricing |
| Make my text sound less AI-generated | humanize |
