Go-to-Market Readiness Assessment SOP

A go-to-market readiness assessment SOP is the final gate before you spend real money or months of effort on bringing your product to market. It takes about a week to gather evidence and one half-day session to score. The area nobody checked is the one that sinks a launch: no tracking, no support plan, a price nobody tested. This SOP puts every area on one scorecard and asks for proof behind every score.

What is the go-to-market readiness assessment SOP and when should you use it?

A go-to-market readiness assessment is a scored review of everything that must work when customers start arriving: who you sell to, what you say, how they find you, how they buy, how they get started, what it costs and who answers when something breaks. Each area gets a score based on evidence from real customers, and a decision rule turns the scores into go, delay or narrow.

It sits at the end of the Go-to-Market Validation category and pulls together the results of the other SOPs. Scope check: the product launch strategy validation SOP tests the launch plan itself; this SOP checks whether the whole business is ready to carry it.

Use it:

• Two to four weeks before a public launch, with time left to fix gaps.
• Before a large ad budget or a first sales hire.
• Before a fundraise, because investors ask the same questions.
• When co-founders disagree about whether you are ready.

What do you need before you start?

• Results from earlier SOPs: interview notes, test results, funnel numbers, pricing data.
• A launch date and goal, even if provisional.
• One outsider: a mentor, adviser, experienced founder or friendly customer who will score honestly.
• A shared sheet or Notion page with the scorecard below.
• Half a day with the whole founding team in one room or call.

How do you run it, step by step?

1. Set the decision and the date

Write the decision you are making ("public launch on 1 December with €5,000 of ads") and the date you will decide. A readiness check with no decision attached drifts into a general worry session.

2. Score 10 areas from 0 to 2

Use the 10 areas in the template. 0 means no evidence, 1 means evidence from opinions or a small test, 2 means evidence from real customers paying, signing up or replying. Scoring 2 because you "feel confident" is the most common way this SOP fails.

3. Attach evidence to every score

Next to each score, link the proof: a test result, a funnel chart, a call recording, a signed pilot. The evidence ratio (scores backed by a link divided by all scores) tells you how much of your readiness is real. Aim for 100%.

4. Have an outsider score independently

Send the evidence to your outsider and ask them to score without seeing your numbers. Compare. Any area where you differ by 2 points needs a conversation, because one of you is missing something.

5. Run a pre-mortem

Gary Klein's pre-mortem method, published in Harvard Business Review, asks the team to imagine that the launch has already failed badly and to write down every reason why. Klein cites earlier research by Deborah Mitchell, Jay Russo and Nancy Pennington showing that this kind of prospective hindsight improves people's ability to identify reasons for future outcomes by 30%. Give everyone 5 minutes alone, then collect the reasons in one list.

6. Plan fixes for every 0 and the top risks

Every area at 0 gets an owner, a fix and a date. The top 3 pre-mortem risks that the scorecard didn't catch get the same. Fixes must be small enough to finish before launch, or the launch moves.

7. Apply the decision rule

Go when no area scores 0 and the total is 15 or more out of 20. Narrow when the total passes but one or two areas are weak: launch to one segment, one channel or one country. Delay when any area scores 0 on the launch date. Write the decision and its reasons on one page.

Template you can copy

GO-TO-MARKET READINESS SCORECARD
Score: 0 = no evidence | 1 = opinion or small test | 2 = real customer evidence

Area                         | Our score | Outsider | Evidence link | Fix if < 2
1. Customer profile          |           |          |               |
2. Problem evidence          |           |          |               |
3. Positioning and message   |           |          |               |
4. Pricing                   |           |          |               |
5. Acquisition channel       |           |          |               |
6. Sales or signup flow      |           |          |               |
7. First-value flow          |           |          |               |
8. Support and operations    |           |          |               |
9. Measurement and tracking  |           |          |               |
10. Legal, payments, terms   |           |          |               |
TOTAL (max 20)               |           |          |               |

Evidence ratio: scores with a link / 10 = __%

PRE-MORTEM
"It is 3 months after launch and it failed badly. Why?"
Reason | Area | Likelihood 1-3 | Impact 1-3 | Covered by scorecard? | Fix

DECISION RULE
GO: no 0s and total >= 15 | NARROW: total >= 15 with weak areas |
DELAY: any 0 on launch date
Decision: ...   Owner: ...   Date: ...

Worked example: a B2B scheduling tool before launch

This case is illustrative. A three-person team plans a public launch of a staff-scheduling tool for childcare centres with €5,000 of LinkedIn ads. Their first scoring session gives a total of 13 of 20, with two zeros: measurement (no tracking on the signup flow) and support (nobody owns incoming questions). Their outsider, a founder who has run two launches, scores pricing 1 instead of their 2, because the price was tested on only 3 customers.

The pre-mortem adds a risk the scorecard missed: launch traffic arrives, but nobody can tell which ads bring paying customers, so the team keeps funding the wrong ones. That maps to the measurement zero.

They spend 9 days fixing the gaps: event tracking on every signup step, a shared support inbox with a 4-hour response rule, and 6 more pricing conversations. The rescore comes to 16 of 20 with no zeros. Pricing is still a 1, so they narrow: launch to childcare centres in one region with half the ad budget, and expand after 30 days of data.

What should you measure, and when do you stop?

Stop when the decision rule gives a clear answer and the one-page decision is written. Rescore once after fixes, then launch or delay. Endless rescoring is a way to avoid launching.

Which mistakes should you avoid?

• Scoring on confidence. Without an evidence link, the score is 0 or 1.
• Scoring alone. Founders grade their own work too kindly; the outsider is part of the method.
• Fixing everything before launch. Fix zeros and top risks; narrow the launch for the rest.
• Skipping the boring areas. Tracking, support and payment terms feel dull, and a gap there can cost you the data from the whole launch.
• Treating "go" as permanent. Rescore 30 days after launch with real data.

How can AI speed this up?

Paste your evidence (test summaries, funnel numbers, notes) into an AI assistant and ask it to score each area with the 0 to 2 rubric and explain each score. Ask it to run its own pre-mortem and list failure reasons you missed. It makes a decent second outsider. The human check: AI only sees what you paste, so it can't spot the evidence you don't have. A person who has launched before still scores independently.

Where does this SOP fit in your validation plan?

This is the last SOP in the go-to-market sequence:

1. Prove the words with marketing message testing and the channel with customer acquisition channel validation.
2. Prove you can close and activate customers with sales process validation and customer onboarding validation.
3. Check every deal earns money with unit economics validation.
4. Rehearse the launch with product launch strategy validation, then run this assessment as the final gate.

See all 10 Go-to-Market Validation SOPs. The free startup checklist creator turns your fix list into a launch checklist, and the F/MS pitch playbook helps when the same evidence goes into an investor deck.

FAQ

What does go-to-market readiness mean?

Every part of the business that customers touch, from first contact to first value and support, works and has evidence behind it. A finished product alone doesn't make you ready.

What is a pre-mortem?

A session where the team imagines the project has already failed and lists every reason why. Gary Klein described it in Harvard Business Review as a way to surface risks people hesitate to raise.

Can I launch with a low readiness score?

You can launch narrow: one segment, one channel, a small budget. A full launch with a zero on the scorecard spends money where you can't see the results.

Who should score the assessment?

The founding team plus at least one outsider who has launched before. Customers can score the areas they see, such as message and first-value flow.