Feasibility — the old risk is dead
Feasibility isn't 'can I code it.' It's 'can I execute the whole model' — reasoned backwards from the goal. And the better you build, the more this dimension can fool you.
Your job: reason backwards from the goal to the smallest thing that proves the promise.
Plan feasibility Read `business_model://current`. Build a 10X traction roadmap from first paying customer → 10 → 100 → 1,000, staged to the MSC, and describe the smallest Demo-Sell-Build test that validates the promise before building. claude mcp add --transport http leanspark https://leanspark.ai/mcp Connect first →
What you get back
Builds a 10X Traction Roadmap (first customer → 10 → 100 → 1,000) staged backwards from your MSC, plus a Demo-Sell-Build plan so you validate the promise before building the product — scoring feasibility against the model, not just the code.
A staged roadmap to your goal and the smallest solution that proves it — with the real risk surfaced when feasibility comes back green.
The last core test is Feasibility, and it comes with a twist. Feasibility isn’t really “can I write the code.” It’s can I execute the whole business model — and you reason about it backwards: Timeline → Team → Solution. Start from the goal, then the team it takes, then the smallest solution. Three checks: a 10X Traction Roadmap (a staged path to your MSC), a staged go-to-market (ten customers, then a hundred, then a thousand), and Demo-Sell-Build (validate the promise before you build the thing).
Here’s the picture of the roadmap: you don’t leap to $10M — you climb to it in powers of ten. Month three: your first paying customer — the validation milestone, before you’ve built much at all. Year one: ten customers, $100K. Year two: a hundred customers, $1M. Year three: a thousand customers, $10M — your MSC. Each step is 10× the last. For Steve the deer, that’s literally 10, then 100, then 1,000 deer — the roadmap and the animal line up. The discipline is to play the hockey stick deliberately — hand-pick your first ten, systematize the next hundred, scale to the thousand — instead of praying for a launch-day spike.
A green feasibility score is not a green light. Can Steve build no-code AR/VR? Honestly — yeah. It’s hard, but buildable, and with AI it’s more buildable every month. So feasibility scores fine — and that is exactly the danger. For most of startup history “can I build it” was THE risk. That era is over. AI made building cheap, which made it the most tempting place to start — and the better you are at building, the easier it is to build the wrong thing beautifully. Feasibility passing is the test confirming your risk is somewhere else entirely.