Right-Sized Framework™

Chapter 5

I Need More Paying Customers

Solve the right problem. World-class engineering still fails without a market — earn proof before you scale.

Step InsideTake the AssessmentJump to References
System Engineering Reviews mapped to the Product Development Cycle — PMF, SRR, CoDR, CDR, TRR, PSR aligned with Plan, Design, Build, Test, Release phases.

Step Inside

Product-market fit is proof earned, not a launch moment.

Airbus built the A380, a world-class aircraft, for a hub-and-spoke market that was already disappearing. Boeing's 787 aligned with how people actually wanted to fly — point-to-point. Engineering excellence isn't enough. Fit is about what's needed, not just what's possible.

This chapter reframes the work around the four PMF risks, builds a small empowered discovery trio, runs scrappy prototypes and concierge tests, adopts Dual-Track (learning and building in parallel), and watches for the signals that fit is near: returning users who complain because they care, word-of-mouth, creative workarounds, and "don't change it yet."

The four PMF risks — all four must be cleared:

  • Value — Will they care? Is the problem real and the solution worth changing behavior for?
  • Usability — Can they use it? Have real users operated it without guidance?
  • Feasibility — Can we build it? Do we have the resources, skills, and timeline to deliver?
  • Viability — Does it work for our business? Does it fit our cost structure, model, and constraints?

In this chapter, you will learn to:

  • Frame the customer problem clearly before writing a line of code
  • Build and run a discovery trio (PM + Designer + Lead Engineer)
  • Run concierge tests and prototypes to validate before committing
  • Adopt Dual-Track so learning and building run in parallel
  • Recognize the market signals that tell you fit is near
  • Use a PMF checklist as your go/no-go before scaling

"The number one company-killer is lack of market." — Andy Rachleff

Action Plan

Eight moves toward fit.

Eight moves toward fit

  1. Frame the problem in one sentence.
    Who feels it, what the pain is, and why now. Share it widely before building anything.
  2. Form the discovery trio.
    PM + Designer + Lead Engineer. Meet twice a week. Own the problem together, not in handoffs.
  3. Identify 5–10 reference customers.
    People who feel the pain today and are actively seeking a fix. Book interviews this week.
  4. List and prioritize assumptions.
    Map your top three assumptions across Value, Usability, Feasibility, and Viability.
  5. Run one concierge or prototype test within 7–10 days.
    Capture evidence, not opinions. Expect to throw the early version away.
  6. Adopt Dual-Track.
    Keep discovery experiments flowing alongside delivery. Learning and building are not sequential — run them in parallel.
  7. Track PMF signals weekly.
    Repeat use, complaints that show care, word-of-mouth, users pushing your product beyond its intended use, "don't change it yet."
  8. Use a PMF checklist as your go/no-go before scaling.
    Don't hire, raise, or expand until the evidence is there.
Key Product Manager Qualities: Technical Expertise, Data-Driven Mindset, Strong Leadership, Effective Communication, Passion for Products, Business Savvy.
Customer Feedback Loop — a five-step cycle: Ask, Collect, Analyze & Plan, Implement, Notify.

Directed Tools and Templates

Validate fit fast.

Start with the PMF Hub for structured checklists and worksheets, then use the reference customer roster and value proposition template before committing engineering resources.

Self-Assessment

Product-Market Fit Deep-Dive

Most teams don't fail because they can't build. They fail because they build the wrong thing for the wrong market — and find out too late. Product-market fit isn't one thing, so this assessment scores five dimensions separately: you'll see which part of your fit is strong, and which part is quietly putting the rest at risk. Answer honestly — it's a mirror, not a report card.

You can also take this at community.rightsizedframework.com/communities/groups/rsf-framers-community/home.

1 = Never true · 2 = Rarely · 3 = Sometimes · 4 = Often · 5 = Consistently — answer honestly. This is a mirror, not a report card.

Problem Clarity & Customer Focus Total possible: 20

1. We can state the customer problem we're solving in a single, clear sentence.

2. We are in love with the customer's problem, not our own solution.

3. We have identified reference customers who are in real pain and actively seeking a fix right now.

4. We capture and use our customers' own words to describe their problem.

The Four Big Risks Total possible: 20

5. Value — We have evidence that customers will pay for, or change their behavior to get, our solution.

6. Usability — We have watched real users operate our solution without guidance to confirm they can actually use it.

7. Feasibility — We have confirmed our team can realistically build this within our resources and timeline.

8. Viability — We have verified the solution fits our business model, cost structure, and any regulatory constraints.

Discovery Discipline & Experimentation Total possible: 20

9. We run small, low-cost experiments to test assumptions before committing serious engineering resources.

10. We build prototypes to answer a specific question and fully expect to throw early versions away.

11. We separate learning (discovery) from building (delivery) rather than blending them into one rush to ship.

12. We measure success by validated learning and customer outcomes — not features shipped or vanity metrics.

Team Structure & Mindset Total possible: 20

13. Our product manager, designer, and lead engineer collaborate from the very start of discovery — not in handoffs.

14. Our engineers help answer "should we build it?" — not just "can we build it?"

15. Our team behaves like missionaries who own the problem, not mercenaries working a task list.

16. Leadership sets clear objectives and constraints, then trusts the team to find the path forward.

Market Signals & Fit Readiness Total possible: 20

17. Customers come back repeatedly — and complain when the product doesn't meet their expectations.

18. Our product spreads through organic word-of-mouth.

19. Users push our product beyond its intended use or ask us to extend it.

20. We have clear, evidence-based criteria for deciding we've reached fit and can shift focus to delivery.

References & Further Study

Go Deeper

  • book
    Inspired

    Marty Cagan

  • book
    The Lean Startup

    Eric Ries

  • book
    Continuous Discovery Habits

    Teresa Torres

  • article
    Product-Market Fit Playbook

    First Round Review

  • article
    SVPG Blog

    Marty Cagan

  • article
    Value Proposition Canvas

    Strategyzer

  • video
    Masters of Scale — Finding Your 1000 True Fans

    Reid Hoffman

  • video
    Lenny's Podcast — PMF with Rahul Vohra (Superhuman)

    Lenny Rachitsky

  • video
    How to Find Product-Market Fit

    Michael Seibel / Y Combinator