Most products fail not because they lack features, but because they confuse needs with wants. Features are needs — they live in the solution context. Outcomes are wants — they live in the bigger context. And customers care far more about their wants than their needs.

The Story

After weeks of problem discovery interviews, the insights were clear. Founders were not lacking frameworks or tools. They knew about Lean Startup, Jobs-to-be-Done, and a dozen other methodologies. The problem was putting it all into practice consistently, while managing the crushing context-switching tax of startup life.

This led to the most important design decision in LEANSpark: wants before needs. Originally, we had been thinking about building discrete workflow tools — an elevator pitch generator, a business model assessment, a specific stress test. These are needs. They are the broccoli of startup validation — good for you, but not what gets founders excited in the morning.

What founders actually want is traction. If you have not launched, how do you go from idea to first paying customers? If you have launched, how do you acquire more? Time-boxing that outcome to 90 days made the promise specific and actionable: helping founders run 90-day validation cycles became the primary job to be done for LEANSpark.

Using the Customer Forces model, I visualized this as a hill. The desired outcome — traction in 90 days — sits at the top. To get there, founders need to do hard things: create business models, stress-test them, talk to customers, design experiments, run campaigns. Each of those is a friction point on the path to the summit. The secondary jobs to be done became about reducing friction around those hard things, not adding more features.

This reframing shaped the Demo-Sell-Build landing page: a clear UVP targeting the want (validate faster, build with confidence), with three core features addressing the top three friction points — learning the framework, stress-testing business models, and running 90-day experiments.

With the product direction set, we shifted to achieving Product/Launch Fit. Most founders think launch day is about finishing the MVP and doing a big-bang release. But there is much more to it. We designed the value delivery journey using a Progress Reward Loop — mapping what a customer can experience in the first 30 seconds, first few minutes, first hours, days, and weeks. We worked through pricing models that balanced value-based pricing against real AI usage costs. And we planned a batched rollout — 10 customers at high-touch concierge, then 100 in semi-automated cohorts, then 1,000 at self-serve — with each batch giving us time to learn, fix issues, and improve.

The 100X Founder workshop emerged from this same principle. Rather than just handing founders a tool, we offered a 13-week cohort-based program to guide teams through a complete 90-day validation cycle using LEANSpark — the done-with-you layer on top of the do-it-yourself product.

Key Frameworks

  • Wants vs. Needs: Features are needs (solution context); outcomes are wants (bigger context). Good products target the want as the destination and remove friction from the needs standing in the way.
  • Product/Launch Fit: The short game before Product/Market Fit. Scale in 10x stages — 10 customers (high-touch, manual), 100 (semi-automated, cohort-based), 1,000 (automated, self-serve) — proving you can deliver value at each level before scaling further.
  • The Progress Reward Loop: Map the customer journey from first touch to habit formation using a doubling progression. What value can you deliver in 30 seconds, a few minutes, a few hours, a day, a week?

Key Takeaways

  • Target the want (traction), not the need (features). Founders do not wake up wanting to run a stress test — they want paying customers.
  • Features equal needs, outcomes equal wants. Good product design reduces friction on the path to the desired outcome rather than adding more features.
  • Product/Launch Fit is the short game before Product/Market Fit — prove you can deliver value to 10, then 100, then 1,000 customers before trying to scale.
  • Batched rollouts beat big-bang launches because each batch gives you time to learn and improve before the next wave of customers arrives.
  • The best launches combine a self-serve product tier with a done-with-you coaching tier — meeting customers where they are in their readiness to adopt.