The Two-Clock Problem: What to Build While You Wait for Approval

The Two-Clock Problem: What to Build While You Wait for Approval

The stalled default in approval-paced ventures is waiting: heads down on the application while revenue, audience, and proof all wait for the slow clock to strike. It is the wrong move. You cannot compress a regulator, and waiting forfeits a window that moves at technology speed. The answer is a wedge product built on the fast clock.

THE PATTERN

What is the two-clock problem?

The two-clock problem is a speed mismatch inside one venture. Your main play runs on an approval-paced clock: regulators, licensing boards, certification bodies, an acquisition working toward close, an enterprise procurement committee. Your opportunity runs on a technology-paced clock, where the capability that makes the play valuable gets cheaper and more crowded every quarter. We named this pattern the Two-Clock Problem because the two clocks fail differently, and most founders plan for only one of them.

It shows up anywhere a gatekeeper sits between a venture and its market. A diagnostic waiting on clinical clearance. A lending product waiting on a state-by-state licensing run. A data platform waiting on a government security certification. A rollup thesis waiting on its first close. Different arenas, same shape: the thing that makes the venture big cannot ship until a slow external process finishes, and the thing that makes it timely will not wait for that process.

The Two-Clock Problem. A Vista framework for ventures whose main play is approval-paced while their opportunity is technology-paced. The slow clock cannot be compressed, and waiting on it forfeits the window. The resolution is a wedge product on the fast clock: near-term tooling or services that monetize the window and feed the endgame instead of competing with it.

THE STALLED DEFAULT

Why is waiting out the slow clock the wrong move?

Because waiting spends the clock you control on the clock you do not. The slow clock is genuinely incompressible. Review queues, licensing boards, and procurement committees run at their own pace, and pushing them rarely helps and often costs credibility you will want later. That half of the founder's diagnosis is correct. The mistake is the conclusion drawn from it: that since the main play cannot ship yet, the company should hold its breath.

While you hold your breath, three things keep moving. The capability behind your opportunity commoditizes, because technology-paced advantages always do. Adjacent players who need no approval occupy the ground floor of the market and set buyer expectations. And your runway converts into nothing but elapsed time: no revenue, no customer contact, no data, a team rehearsing a launch instead of learning from one.

The slow clock cannot be compressed. The fast clock will not wait for it.

In the engagements we run in approval-paced spaces, the waiting team is rarely idle. It is busy with the filing, busy with investors, busy polishing a launch plan. Busy is what makes this default so comfortable. But none of that motion compounds, because all of it is aimed at a date someone else controls.

THE REAL CONSTRAINT

Is the approval really what is stuck?

Usually not, and this is where the diagnosis earns its keep. Slow is not the same as stuck. Under the real-constraint lens, the question is never what hurts. It is what would have to change for the pain to stop. Run that question here and the approval falls away quickly: if the clearance, the license, or the signed contract landed tomorrow, would you be ready to win with it?

For most two-clocked ventures the honest answer is no. There is no audience to announce to. There is no revenue engine to pour the approval into, and no operating history that makes the newly permitted thing credible. The approval would land on an empty stage. That is the real constraint, and it has nothing to do with the queue: the venture has no fast-clock asset.

Three signs you have misnamed the constraint:

• Every plan starts the day the approval lands. Nothing in the company compounds before that date.
• The approval is the whole moat. Take it away and nothing about the venture would be hard to copy.
• Progress updates describe the queue. Reporting covers where the file sits, not what the business built.

Across the advisory work we do in these spaces, this rename is often the entire first conversation. A founder arrives blocked on a regulator and leaves owning a different problem: what to build while the regulator does its job. That version has the useful property of being solvable this quarter.

THE WEDGE

What should you build on the fast clock?

A wedge product: a near-term offer that sells now and builds exactly the assets the slow-clock endgame will need. Not a pivot, and not a side hustle. A deliberate first product whose job is to monetize the window and stock the shelves for the approved play.

The shape varies by arena. Tooling for the workflow your endgame will eventually own. A productized service built on the expertise the approval will later let you apply at scale. Readiness and preparation offers for others stuck behind the same slow clock. A lighter tier of the product that stays outside the regulated perimeter. The form matters less than the tests it must pass.

• It monetizes now. Real customers paying real money on a sales cycle measured in weeks, not on the approval's timeline. If it cannot produce revenue before the slow clock strikes, it is a second bet, not a wedge.
• It feeds the endgame. Every customer, proof point, and dataset the wedge produces should be one the approved play inherits. You are building the audience, credibility, and data the endgame needs, and getting paid to do it.
• It never trains the market against the endgame. If the wedge teaches buyers they do not need the approved product, or anchors your pricing so low the main play cannot recover, you are competing with your own future. Kill that wedge and pick another.

One boundary is non-negotiable: the wedge stays outside the regulated perimeter. You are monetizing the window around the approval, never the activity that requires it. Held to that line, the wedge also strengthens the eventual application, because the file now describes a real company with real customers rather than a bet in a holding pattern.

THE MAP

Which wedge fits your situation?

Match the wedge to the clock you are stuck behind. The table maps the common approval-paced situations to a wedge shape that fits and the asset it hands the endgame.

While the slow clock runs on	A wedge that fits	What it feeds the endgame
Regulatory clearance for a product	Tooling, education, or readiness services for the same buyer the cleared product will serve	A warm buyer list and trust in the exact channel the cleared product ships into
A license or charter	Operate as a vendor or partner to incumbents who already hold one	Operating history and relationships the license will multiply
A government or enterprise certification	Sell the uncertified tier to buyers the certification does not gate	Reference customers and usage the certified tier can cite
An acquisition or deal working toward close	Stand-alone services built from the capability the deal is meant to buy	Cash flow now and proof the combined entity inherits
A long enterprise procurement cycle	A self-serve or team tier that lands inside the account early	Internal champions and usage evidence procurement cannot ignore

Two notes on using the map honestly. First, a wedge earns real resourcing; run as an afterthought, it produces afterthought revenue and feeds nothing. Second, sometimes the wedge outgrows the endgame. That is not failure, it is information. A venture that discovers its fast-clock business is the better business has learned something the waiting version never would have.

THE DECISION RULE

How do you decide what to build while you wait?

Run one test and obey the result.

The two-clock decision rule. If the approval landed tomorrow and you would not be ready to win with it, the approval is not your constraint. Name the missing fast-clock asset, whether that is revenue, audience, credibility, or data, and build the wedge that produces it while feeding the endgame. If you would be ready, protect your focus and let the file sit.

Notice the rule cuts both ways. Some ventures should wait: the endgame is fully staged, the window is defensible, and any wedge would split a small team or drift toward the regulated line. Honest waiting is a position. Default waiting is a drift, and the difference is whether you ran the test.

The diagnosis is fastest with an outside read, because from inside the venture the approval looks load bearing by definition. The pattern we see across matchmaking conversations is that the founder already suspects the rename and mostly needs someone to say it out loud, then help pick the wedge. If that is where you are, a free intro call is the low-stakes way to test the rename. You can also tell us about your business and get matched with an operator advisor who has run a two-clocked venture, or see the full range of ways to work with us.

QUESTIONS

Frequently asked questions

What is the two-clock problem in business?

The two-clock problem is Vista's name for a venture whose main play is approval-paced, gated by regulators, licensing, certification, acquisitions, or procurement, while its opportunity is technology-paced. The slow clock cannot be compressed, and waiting on it forfeits the window. The resolution is a wedge product that monetizes the fast clock and feeds the endgame.

Is it ever right to simply wait for the approval?

Yes, in one narrow case: the endgame is fully staged, so the day the approval lands you can convert it, and the window is durable enough to still be there. If either half of that fails, waiting is drift. Run the tomorrow test honestly before you choose patience.

What makes a good wedge product while you wait on approval?

Three tests. It monetizes now, on a sales cycle measured in weeks rather than on the approval's timeline. It feeds the endgame by building the audience, credibility, or data the approved play will inherit. And it never trains the market against the endgame by teaching buyers they do not need it.

Will a wedge product distract us from the main play?

A bad one will. A good wedge is not a second company; it is the endgame's supply line, aimed at the same buyer and the same problem. If the wedge's customers, data, and proof do not transfer to the approved play, it is a distraction wearing a strategy's clothes.

How do I know if I have misnamed my constraint?

Ask what would have to change for the pain to stop. If the approval landed tomorrow and you would not be ready to win with it, the approval was never the constraint; the missing fast-clock asset is. Plans that all start on approval day are the clearest sign you are waiting on the wrong clock.

NEXT STEP

Stop watching the clock you cannot move

Two-clocked ventures fail politely. Nobody makes a dramatic mistake; they wait, and the window closes while the file is still in the queue. This week, run the tomorrow test with your team and name what you would be missing on approval day. Then pick the wedge that builds it. The slow clock will keep its own time either way. The real choice is what you are building when it finally strikes.