Founder-Market-Engineering Fit Scorecard

Purpose

Use this scorecard to decide whether you are a credible learning instrument for one market wedge. Before product-market fit, the founder must reach the customer, interpret the work, earn trust, create first value, ask for a commitment, and live with the consequences. An advantage makes one of those acts cheaper or more truthful.

A weak result is not a judgment on the market or the founder. It says that this founder’s present route through this market is blocked, expensive, or dependent on capability that does not yet exist.

When To Use

Use it before committing to a wedge or recruiting design partners. Use it again when discovery reveals a trust boundary, buyer, exception, integration, or support burden that was absent from the original idea.

Score the proposed first version, not the company you hope to become. Changing the customer, promise, data boundary, distribution path, or manual work changes the bet and deserves a new scorecard.

Inputs

Bring customer conversations, a description of the current workflow, names or a credible route to the first users, the proposed wedge, a sketch of how first value will be delivered, and the likely sales and support work.

At the top of the page, write:

• Customer: the person who encounters the problem and the person who can authorize change.
• Painful workflow: one recurring situation, including the current alternative.
• First wedge: the smallest result you propose to deliver and what it deliberately leaves outside.
• Next unknown: the decision this work must make less uncertain.

An answer about a broad market cannot be scored honestly. “Independent agencies producing weekly client reports from project notes” is usable. “Software for agencies” is not.

Template

Score each path from 0 to 3. The number is shorthand for the condition, not a measurement of personal ability.

For each row, write observable evidence and the next move. “I know the industry” is a claim. “I can ask five operations leads to reconstruct last week’s failed handoff with me” is evidence.

Do not grant a future hire, advisor, partner, contractor, audience, or integration a score it has not earned. Put it in the last column as a compensation claim, then name how you will test that claim. A useful compensation keeps the founder close to the evidence. One that owns all the customer access or interpretation hides the gap.

Interpretation

Do not add the scores. Fit is a profile, and one blocked path can dominate several advantages. Strong engineering does not offset an unreachable buyer. Warm access does not make an unsafe first product responsible. Enthusiasm does not make the market’s ordinary support work tolerable.

Circle three things:

1. The advantage: one 3 that materially lowers the cost of reaching evidence.
2. The governing gap: the 0 or 1 most likely to distort the next decision.
3. The compensation test: one action that could change the governing gap without requiring a product build.

If you cannot identify an advantage, the idea may still deserve discovery, but the scorecard has not shown why this founder should pay the opportunity cost of pursuing it.

Worked Profile: The Agency Report Wedge

In this modeled profile, a founder who built internal agency tools wants to produce client-ready weekly reports from scattered project notes. She can contact six agency owners, recognizes the politics behind late updates, and can assemble a draft manually behind a thin upload form.

Her access and interpretation are advantages. Trust and first value are usable because the initial customers know her and every report remains subject to account-lead review. Sale and distribution are repairable: six conversations are enough for discovery, not yet a repeatable path beyond her network.

The broad idea is blocked at operation. Each agency uses different sources, every report needs founder judgment, and the promise quietly expands from document assembly into an ongoing writing service. A high total would conceal that failure.

The scorecard should change the wedge. She limits the first test to one project-note export, one report format, and five weekly cycles. The account lead approves every draft. She will continue only if the same transformations recur and review time falls without growing correction work. The narrower bet converts operation from blocked to repairable while leaving the weak distribution path visible.

Decision Rule

Finish with one of four decisions:

• Pursue: an advantage shortens the path to evidence, no 0 blocks responsible learning, and every 1 has a bounded next move.
• Narrow: fit exists for one customer, workflow, channel, data boundary, or manual service but not for the broad idea.
• Repair: a specific act of access, study, trust-building, or borrowed capability could change the profile; perform it before serious build work.
• Do not start: you cannot reach the customer, interpret the work, earn necessary trust, deliver first value responsibly, sell the result, or support its consequences.

Write the next action beside the decision. “Research more” is not an action. “Observe three account leads assemble Friday reports and compare the handoffs they correct” is.

Common Mistakes

The optimistic error is scoring interest as evidence. Reading about a market does not establish access, workflow judgment, or customer trust.

The engineering error is scoring the finished system instead of the next honest result. The question is not whether you could eventually build the platform. It is whether your present technical and operating choices can produce decision-grade evidence safely.

The strategic error is treating compensation as delegation. An advisor can challenge your interpretation; they cannot understand the customer on your behalf. A contractor can close a bounded implementation gap; a contractor-built product cannot supply missing demand.

Finally, do not improve a score by changing the story. Improve it by changing the wedge, earning access, observing the work, reducing the trust boundary, or proving that a compensation actually holds.