Market Context Assessment is a structured check on the external conditions surrounding a market: regulation, technology, economics, buyer behaviour and timing. It adapts established environmental-scanning practice, principally PESTEL, to the scale a founder can actually act on. Its purpose is to surface the forces that will decide the outcome regardless of how well the product is built.
Before committing to a market, and again whenever something external shifts. It is a scanning method rather than an analytical framework: it produces a list of forces and their direction, not a verdict.
What a market context assessment is
A market context assessment is a structured check on the external conditions around a market: regulation, technology, economics, buyer behaviour and timing.
It is ShipFit’s own method rather than an established academic framework, and it is worth saying so. It adapts standard environmental-scanning practice, principally PESTEL analysis, whose lineage runs back to Francis Aguilar’s work in 1967, and narrows it to the forces a founder can act on inside a launch decision.
The purpose is to surface the things that will decide the outcome regardless of how well the product is built. Founders spend almost all their attention on variables they control and very little on the ones they do not, and the second group frequently matters more.
- Name the enabling condition The most useful question
What became true recently? If nothing did, ask why the space is still empty.
- Five forces you do not control Regulation, tech, economics, behaviour, timing
Attention goes to the variables you control. These are the ones that decide the outcome.
- Direction, not snapshot Every force gets an arrow
You ship into the conditions that exist when you arrive, not the ones you surveyed.
- A tailwind is not a moat The expensive confusion
Conditions that let you in let everyone else in too, which is why several similar companies appear at once.
Why it matters
Most launch post-mortems name an internal cause: the product was wrong, the team was wrong, the marketing did not work. A meaningful share of failures are actually external, and the most common of those is timing.
Being early is the difficult one, because it is indistinguishable from being wrong until much later and consumes exactly the same runway. A product requiring a behaviour people have not adopted fails in a way that looks identical to a product nobody wanted, and the team learns the wrong lesson from it.
Which is the expensive part. A team that was early concludes the market does not exist, shelves the idea, and watches somebody else ship more or less the same thing three years later to considerable applause.
The five forces
What is the direction and pace of the rules, not just the current state?
Bad answer: "We are too small for anyone to care." Small delays the discovery; it does not prevent it.
Is the capability you depend on a rising floor or a fixed ceiling?
Bad answer: "Model costs will keep falling." That is a hope about one vendor, not a trend.
What is happening to your buyer's budget and headcount?
Bad answer: "The market is worth $4bn." That is size, not the buyer's ability to spend this year.
Does the habit you need already exist somewhere, badly?
Bad answer: "Once people try it they will see." You are funding a behaviour change as well as a product.
What changed recently that makes this possible now?
Bad answer: "Nobody has done it." Then ask who tried, and what happened to them.
Record a direction for each: improving, stable or deteriorating. A snapshot describes where things are, and you will arrive somewhere else.
The enabling condition
If there is one question to keep from this method, it is: what became true recently that makes this possible now?
A good answer is specific and dated. Inference costs fell by an order of magnitude. A regulation came into force. Remote work made a category of tool normal that was fringe before. Each explains both why the opportunity exists and roughly when the window opened.
The absence of an answer is the finding.
A cost that collapsed, with a date.
"Inference cost fell by roughly an order of magnitude over the last two years."
A claim about the future dressed as a change.
"AI is going to change everything." Nothing became true; something might.
A behaviour that became normal.
"Distributed teams made async written updates standard rather than unusual."
An observation about competition.
"Nobody has built this yet." Then ask who tried, and what happened to them.
A market open for a decade with nobody in it is usually a market people tried and left. Look for the companies that already failed there before concluding the space is unoccupied.
When to run it
- You are about to commit to a market you have not operated in before.
- Your idea depends on a cost, a rule or a behaviour that changed recently.
- The space looks uncontested and you do not know why.
- Something external moved: a regulation, a platform policy, a major vendor price change.
- You are raising, and will be asked why now rather than three years ago.
- You do not yet know whether the problem is real. Use The Mom Test →
- You need to size the market rather than read its conditions. Use TAM SAM SOM →
- You need to know what defends a position once taken. Use 7 Powers →
- You are choosing which segment to serve. Use Playing to Win →
Against the alternatives
What conditions outside the industry will decide this?
Gives you: Five forces with a direction each, and a named enabling condition
The same question, thoroughly, for a large organisation.
Gives you: Six categories. More complete, considerably slower
Is the structure of this industry attractive?
Gives you: Rivalry, buyers, suppliers, entrants, substitutes. Inside the industry
How big is the market?
Gives you: Three numbers. Size, which is a different question from conditions
Market context in practice: Webvan
The canonical case of a correct idea assessed against the wrong decade.
Webvan · 1996 to 2001
The right business, roughly fifteen years early, built at full scale before anyone checked.
Webvan raised around $800m and built automated distribution centres before it had established that enough people in a given postcode would buy groceries online at the price it needed to charge. It signed a $1bn construction agreement with Bechtel to roll out warehouses across twenty-six cities. It filed for bankruptcy in July 2001, having reached eight.
Instacart, launched in 2012 into a market with smartphones, broadband saturation and existing supermarket infrastructure, addressed the same demand by owning almost none of it.
The comparison gets used to argue that Webvan was simply too early. That is true, and it undersells the specific error. Being early is a condition. Committing $800m of fixed infrastructure before establishing the demand curve is a decision.
- Raised
- ~$800m
- Bechtel warehouse agreement
- $1bn
- Cities reached before bankruptcy
- 8 of 26 planned
What it shows: Market timing is not a verdict on the idea, it is a constraint on how much you may spend before the idea is confirmed. Webvan got the idea right and the spending schedule catastrophically wrong.
When it won’t help you
- It produces a list, not a verdict
Five forces with arrows on them does not tell you whether to enter. The method has no weighting, no threshold and no scoring, and two people reading the same conditions will reasonably disagree about what to do.
Instead: Use it to surface risks and to force the timing question. Get the decision from evidence about demand.
- External forecasting is unreliable
Predicting regulation, technology cost curves and buyer economics eighteen months out is genuinely hard, and confident answers here are usually less trustworthy than uncertain ones.
Instead: Record confidence alongside direction, and revisit whenever something moves rather than treating the scan as settled.
- It is easy to use as procrastination
Environmental analysis is comfortable work: it feels productive, it produces documents, and it requires no contact with a customer who might say no.
Instead: Time-box it to a day. If it is taking a week you are avoiding the conversations.
- Favourable conditions are not an advantage
Everything the scan finds in your favour is equally available to every other entrant, which is usually why several similar companies appear in the same quarter.
Instead: Treat a tailwind as an explanation of why the window opened, then answer defensibility separately.
Further reading
- Francis Aguilar, Scanning the Business Environment (1967). The origin of the practice this adapts.
- TAM SAM SOM. Sizing, once the conditions look workable.
- Disruptive Innovation. Why a favourable condition often produces several entrants at once.
- 7 Powers. What you will need once the tailwind has brought your competitors in too.
- The Mom Test. The demand evidence a context scan cannot substitute for.
How to apply Market Context Assessment
- 1
Name the enabling condition
What became true recently that makes this possible now? A cost that collapsed, a regulation that changed, a behaviour that became normal, a capability that arrived. If nothing changed, the honest follow-up is why the space is still empty, and the usual answer is that people have tried.
- 2
Check the regulatory direction, not just the current state
Regulation is the force most likely to make a well-built product unsellable. What matters is direction and pace rather than today's rules, because you will ship into the rules that exist when you arrive.
- 3
Check whether the technology you depend on is a floor or a ceiling
If your product is possible because of a capability that is improving fast, that is a floor rising under you. If it depends on a specific vendor, model or API remaining available and priced as it is today, that is a ceiling and it belongs on the risk list.
- 4
Check the economic conditions your buyer is operating under
Budgets, headcount, discretionary spend. The same product sells differently into a hiring market and a cost-cutting one, and buyer economics move faster than buyer needs.
- 5
Check whether the behaviour you need already exists
Products that require a new habit are much harder than products that attach to an existing one. Ask whether people already do a version of this, badly, somewhere else. If they do not, you are funding the behaviour change as well as the product.
- 6
Write the direction, not just the state
Every force gets an arrow: improving, stable or deteriorating. A snapshot tells you where things are, and you are building into where they will be, which is a different question and the only one that matters.
Common mistakes
- **Recording a snapshot instead of a direction.** A list of current conditions is a photograph. You will ship into the conditions that exist eighteen months from now, so every force needs an arrow.
- **Skipping regulation because you are small.** Regulation is the force most likely to make a well-built product unsellable, and being small does not exempt you, it only delays the moment you find out.
- **Treating an unusually favourable environment as an advantage.** Conditions that helped you enter helped everyone else too. A tailwind is not a moat.
- **Assuming an empty market is an opportunity.** Uncontested space is sometimes uncontested because the conditions do not support a business there yet. Ask who tried and what happened to them.
- **Depending on a vendor and calling it a technology trend.** 'AI got cheaper' is a trend. 'One provider's pricing stays where it is today' is a dependency, and confusing the two hides a real risk.
- **Producing a report rather than a decision.** The output should change what you do next: enter, wait, or change the entry point. A document that changes nothing was a research exercise.
How ShipFit operationalizes this
ShipFit runs Market Context Assessment in Stage 1 (Worth Building?), alongside TAM/SAM/SOM, Porter's Five Forces and Market Timing Analysis. It pulls current conditions from live research rather than from training data, and asks explicitly what changed to make the idea possible now. The output feeds the Stage 1 verdict rather than sitting beside it: an idea whose enabling condition nobody can name is treated as a timing risk.
ShipFit runs 55 frameworks across 9 decision stages
Market Context Assessment is one tool in a bigger toolkit. The full library covers market sizing, buyer discovery, MVP scoping, pricing, and launch.
The Mom Test
Q3Rob Fitzpatrick
Validation question methodology, real interviews, not theater
Jobs-to-be-Done
Q2-Q4Clayton Christensen
Functional, social, and emotional jobs your product fulfills
7 Powers
Q4Hamilton Helmer
Strategic moats: Scale, Network, Counter-positioning, Switching, Brand, Cornered Resource, Process
Van Westendorp PSM
Q6Feature-weighted price sensitivity analysis without guessing
Blue Ocean Strategy
Q4Kim & Mauborgne
ERRC framework: Eliminate, Reduce, Raise, Create
Fake Door Testing
Q7Pre-build behavioral validation with landing pages and apology modals
+ 49 more: TAM/SAM/SOM Analysis, Porter's Five Forces, Market Timing Analysis, Unit Economics (LTV/CAC)...
Frequently asked questions
What is a market context assessment?
How is this different from PESTEL?
What is an enabling condition?
Why does timing matter more than the idea?
Is a favourable market environment a competitive advantage?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
The JTBD framework in plain terms: the four forces of progress, the switch timeline, and how the Christensen and Ulwick schools actually differ.
The 7 Powers, each with its benefit and its named barrier, plus the Power Progression that decides which of them a startup can realistically build and when.
Most founder market research is a TAM slide that nobody believes. The numbers that actually matter are smaller, harder to defend, and tell you whether the market exists for the ten-customer version of your business.
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
How many months until the bank account hits zero?
Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.
For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.
Replit turns ideas into deployed apps in minutes. Describe it, publish it. ShipFit makes 9 decisions before you open Replit so the deploy is the right thing. ShipFit even exports a Replit-optimised prompt that encodes every decision. Use both. ShipFit first.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.