Market Timing and Wedge Selection
In quantum, the same idea can be a company, a research project, or a donation to the field depending on when you start it. This chapter is about choosing the narrow entry point — the wedge — that creates evidence before the future arrives.
Timing is part of the product. A wedge that cannot produce evidence on a mortal timescale has the same problem as a wrong one.
By the end of this chapter you will be able to choose and defend a quantum company wedge by matching technical readiness, customer urgency, capital intensity, team edge, and timing risk — and to write the wedge as a test plan rather than a vision statement.
Core concepts: startup wedge selection, investment proof gates, company diligence.
A wedge is an evidence machine
A startup wedge is a narrow entry point where a team can create evidence before trying to own a broad market. Wedge selection is unusually hard in quantum because many end markets depend on future hardware. The wedges that work do one of three things: create value now, generate credible evidence toward future value, or own a bottleneck that customers already need solved.
Timing belongs inside the product definition. Too early is as dangerous as technically wrong — both end the company, and the early one ends it more slowly and more expensively. Too broad hides the absence of a buyer. A good wedge memo names the customer, the pain, the baseline, the technical dependency, the proof artifact, the moat, and the kill criterion, in language a stranger could test.
Two scores that force the timing question
Opportunity expected value — probability of technical success times value if success, minus the cost of waiting and the cost of capital — drags timing and cost into a conversation that would rather discuss the size of the prize. A wedge with magnificent value-if-success and a decade of waiting is often dominated by a smaller wedge that pays its way in evidence.
The decision score — claim quality and proof progress against risk and kill-criteria pressure — measures the wedge's trajectory rather than its story. A wedge improves when proof progress rises and kill-criteria pressure falls. If neither number has moved in six months, the wedge is not working, whatever the pitch says.
Worked example: the developer-platform wedge
A team wants to build a quantum developer platform. The weak thesis says the market will be large. The strong wedge says: our buyer is research teams running hardware-aware benchmarks; the pain is reproducibility and workflow drift; the baseline is scripts and notebooks; the first artifact is a reproducible benchmark harness; the proof gate is repeated external use; the kill criterion is no retained usage after a defined trial period.
Two claims follow. First, a narrow wedge produces evidence faster than a broad platform thesis — the harness can be in users' hands this quarter, the platform cannot. Second, the first proof artifact should test willingness: to use, to pay, to integrate, or to rely. An artifact that tests none of those is a demo.
Where the memo goes wrong
The first trap is choosing a wedge because it sounds like the future. Future relevance is not enough; the wedge must create present evidence or reduce a present bottleneck. "This will matter when fault tolerance arrives" is a research position, not a company.
The second trap is hiding capital intensity. Hardware-heavy wedges need more money and more time before proof arrives. Software wedges are cheaper but less defensible. Infrastructure wedges can be defensible but face slow customer cycles. The honest memo writes the capital number next to the proof gate it buys.
The engineering view
For a computer scientist, wedge selection resembles choosing an MVP that tests the riskiest assumption — with the discipline to pick the right assumption. If the risk is customer demand, the MVP must not be a toy. If the risk is technical feasibility, the MVP must not be a sales deck. Mismatching the artifact to the risk is how teams spend a year learning nothing.
Write the wedge as a test plan: assumption, artifact, measurement, pass condition, fail condition, next action. Quantum startups need this discipline more than most, because hype makes broad claims look cheaper than they are — and broad claims are exactly the ones that cannot be tested.
What this buys you in diligence
A build decision should name what can be proven in months, not years. A wait decision is often correct when the wedge depends on hardware that is not ready — waiting is a strategy, not a failure of nerve. An invest decision should require a wedge that can create evidence without the whole quantum future arriving at once.
The wedge memo is also the fairest way to compare founders: two teams with the same vision can differ enormously in the quality of their first six months.
Exercise
Write a wedge memo. Produce a memo with target customer, problem, technical dependency, timing thesis, and first proof artifact.
- Submit: the memo, plus three proof gates and one kill criterion for the first six months.
- Check: apply opportunity expected value and the decision score. State the capital the first proof gate requires, and the calendar date by which it should be observable.
- Decide: choose build, partner, invest, monitor, wait, or avoid — and name the evidence that changes the label.
- Repair: if your wedge description could belong to any quantum startup, redo it after Chapter 73.
Check your understanding
Without notes: produce a wedge memo with target customer, problem, technical dependency, timing thesis, and first proof artifact.
A passing memo names a customer a stranger could phone, an artifact that tests willingness to use or pay, and a kill criterion the team would actually honor.
Oral defense: argue, in two minutes, that a specific broad quantum vision should be narrowed — then name the one wedge you would keep.
If you get stuck
If your wedge lacks source labels, customer specificity, proof gates, or kill criteria, revisit Chapter 73 (The Quantum Company Landscape) to see which company categories even admit wedges, and Chapter 72 (When to Build, Partner, Wait, or Avoid) for the decision labels the wedge feeds.