Skip to content

Solo Founder Product Engineering Handbook

Market Attractiveness for Solo Founders Matrix

Compare markets by pain, reach, budget, sales cycle, support load, build burden, trust burden, and solo-founder survivability.

Purpose

A market can be large, painful, and growing yet still be a poor first market for one person. The customers may be hard to reach, the buyer may sit behind procurement, or the smallest honest product may require too much integration and support.

Use this matrix to choose a beachhead market: the first bounded group in which you can investigate the pain, reach buyers, deliver value responsibly, and repeat the learning loop. It is not a total-addressable-market calculator. It compares the conditions that determine whether a solo founder can get close enough to a market to learn.

Name Markets You Could Actually Enter

Compare two to four candidates. Define each as a customer, painful workflow, and relevant boundary such as geography, company size, toolchain, or trigger event.

“Manufacturing” is too broad to score. “Maintenance managers at regional food processors who need an approved contractor after a packaging-line failure” exposes a workflow and some of the burden hidden by the category.

Write one sentence for each candidate:

  • Candidate: customer + painful workflow + boundary.
  • Entry path: how you can reach the first qualified people repeatedly.
  • First result: the smallest useful outcome you could deliver before building a broad product.

If the entry path or first result cannot be named, keep the candidate but mark that condition unknown. Do not repair a vague market by giving it an average score.

Build the Evidence Record

Bring discovery notes, observed workarounds, outreach results, buying signals, and a rough trace of delivery from onboarding through support. Write the event or observation that earned every score. Use U when evidence is absent.

Score from 1 to 5, always in the same direction: 1 obstructs a solo entry; 5 supports it.

  • Pain and recurrence: 1 is an occasional irritation; 5 is costly or risky work that recurs.
  • Workflow visibility: 1 rests on opinions; 5 appears in observable tasks, documents, handoffs, or failures.
  • Reachability: 1 has no repeatable route to qualified people; 5 has a channel you can use now.
  • Buyer and budget: 1 has no clear authority or money source; 5 has a named buyer and an existing spend, savings, revenue, or risk case.
  • Sales and procurement: 1 requires long or multi-gate approval; 5 permits a bounded founder-led decision or pilot.
  • Delivery and support: 1 creates bespoke implementation, emergencies, or many exceptions; 5 produces bounded, repeating work.
  • Build and integration: 1 needs a broad system or critical dependencies before value; 5 allows a narrow result using software, existing tools, and honest manual work.
  • Trust and regulation: 1 makes the first promise unsafe or beyond present capability; 5 has clear safeguards you can meet.
  • Retention: 1 is curiosity or rare use; 5 belongs to a recurring workflow, habit, or obligation.
  • Founder advantage: 1 lacks access, credibility, judgment, or skill; 5 has a present advantage that shortens the route to evidence.
  • Timing and competition: 1 faces a closing window or no credible opening; 5 has a specific change or neglected seam that creates entry now.
  • Expansion: 1 ends after one small transaction; 5 leads naturally to adjacent value after the first workflow earns trust.

Compare the Shape, Not the Total

Put a score and a short evidence note in each cell—for example, 4 — seven buyers use the same weekly export. The note matters more than the number.

Condition Candidate A Candidate B Candidate C Candidate D
Pain and recurrence
Workflow visibility
Reachability
Buyer and budget
Sales and procurement
Delivery and support
Build and integration
Trust and regulation
Retention
Founder advantage
Timing and competition
Expansion

Do not add the columns. A total lets an attractive future compensate for a blocked present. Strong expansion cannot make unreachable buyers reachable, and intense pain cannot make a first promise safe.

Read each column in this order. Is the pain real and visible? Can you reach a buyer and learn within your runway? What system and operating burden precede the first result? Circle the condition that most limits each candidate.

An unknown can be the governing constraint. If a short discovery test could resolve it, write the test instead of guessing the score. If several conditions depend on funding, hires, partnerships, certifications, or distribution you do not have, the market may be attractive without being enterable now.

Make the Market Decision

Choose the candidate with the strongest evidence-backed route to repeated learning and responsible first value. That is not always the candidate with the lightest engineering. A harder build can be rational when pain, reach, budget, and founder advantage are unusually strong and the first result can be bounded.

Finish with this record:

  • Beachhead market: the customer, workflow, and boundary selected.
  • Evidence that earned the choice: the two or three observations that distinguish it from the alternatives.
  • Governing constraint: the condition most likely to defeat entry.
  • Compensation or boundary: how the first test reduces that constraint without pretending it away.
  • Rejected or postponed markets: why each lost now, and what evidence or changed condition would reopen it.
  • Next discovery action: one action, a date, and the result that would confirm or overturn the choice.

Worked Comparison

Suppose a founder is exploring contractor sourcing for equipment maintenance. This is a modeled example, not market evidence. Three candidates remain after initial discovery: one equipment class at regional food processors, general building systems for commercial property managers, and critical equipment for hospital facilities teams.

Hospital failures may carry the greatest cost, but procurement, verification, response expectations, and the consequences of a poor match could block a responsible solo entry. Property managers may be easier to reach, yet “general building systems” produces too many equipment types and exceptions to teach one repeatable delivery pattern. The regional food-processor candidate may deserve the next test if the founder has a credible trade-group route, sees the same failure and sourcing workflow recur, and can restrict the promise to qualified options rather than emergency repair.

That does not make the selected market best in the abstract. It identifies where this founder can obtain decisive evidence without concealing trust and operating work. The next action might be to reconstruct five recent failures and manually source three bounded requests. If requirements do not repeat, supply cannot be verified, or fulfillment depends on all-hours founder response, the beachhead narrows again or closes.

Common Mistakes

Market size is context, not proof of entry. Estimate it only after defining the segment narrowly enough to count plausible customers and value. A large category cannot rescue weak reach or unclear buying authority.

Do not score from category reputation. “Healthcare has budget,” “small business is easy to sell to,” and “AI is growing” are stories until a specific buyer, workflow, and event make them observable.

Do not hide enterprise requirements under “later.” If procurement, integration, privacy, reliability, compliance, or support blocks the first useful result, it belongs in the present comparison.

Finally, do not choose a market merely because its product is easiest to code. The purpose of a beachhead is to create fast, honest learning about painful work and willingness to change—not to reward a convenient implementation.

Field Reference

Leave the page with one bounded entry test, a stated reason each alternative lost, and the most dangerous unknown exposed. If every candidate still looks attractive, sharpen the segments or collect evidence where the comparison is blank.