Ten Business Days: The Shelf Life of an Opportunity in Modern American Business

Somewhere in your organization right now, a proposal is aging out. It was viable when it was written. The market condition it addressed was real, the competitor threat was live, the pricing window was open. By the time it clears its fourth sign-off, none of those things will still be true. Nobody will record the loss, because the opportunity never appeared on a ledger in the first place.

This is the structural contradiction at the heart of most American mid-market and enterprise companies: decision windows are compressing while approval chains are expanding. We built governance for an era when markets moved quarterly. We are running it in an era when they move weekly.

The Mismatch Nobody Budgets For

Consider the arithmetic. A typical capital or strategic proposal at a mid-sized US company passes through a requester, a manager, a director, a finance reviewer, a compliance check, and an executive committee that meets biweekly. Even a fast-moving organization consumes three to six weeks. Slower ones consume a quarter.

Now consider what's on the other side of that process. A regional retailer evaluating a curbside pickup partnership, a community bank weighing a fintech referral program, a manufacturer deciding whether to lock in a supplier contract before tariffs shift — none of these opportunities hold still for six weeks. Competitive advantage in most US industries now behaves like produce, not canned goods. It has a shelf life.

The cost of this mismatch is invisible by design. A declined proposal generates a paper trail. An expired one generates nothing — no rejection memo, no post-mortem, no line item. It is a loss recognized by no one, which means it is a loss learned from by no one.

Why Governance Grows But Windows Don't

Approval chains expand for comprehensible reasons. Each addition is usually a response to a specific past failure: the bad vendor contract, the compliance miss, the initiative that burned cash. Governance accretes like scar tissue — every scar is individually justified.

The problem is that these layers are calibrated to minimize downside risk without any mechanism weighing the upside cost of delay. Risk committees quantify what happens if a decision is wrong. Almost no committee quantifies what happens if a right decision is late. Until that asymmetry is corrected, the process will keep optimizing for safety at the expense of speed, and it will do so with a clean conscience.

The Two-Week Memo

The remedy we advocate is deliberately unglamorous: a lightweight internal document — the two-week memo — that binds the organization to a go/no-go call within ten business days of submission.

The memo is not a business case. It is closer to a flight plan. It fits on two pages and contains exactly five elements:

1. The decision. One sentence, phrased as a choice: Approve or reject X by [date].
2. The window. Why ten business days? What changes after that date? If nothing changes, this isn't a time-sensitive decision and belongs in the normal queue.
3. The downside. Maximum realistic loss if the decision proves wrong, stated in dollars or hours — not hedged into vagueness.
4. The reversal cost. What it takes to undo the decision if it fails. Cheap-to-reverse decisions deserve faster approval than expensive-to-reverse ones; most processes ignore this distinction entirely.
5. The named decider. One person. Not a committee, not a distribution list. A single accountable executive who must answer by day ten.

The deadline is the discipline. If the named decider takes no action by day ten, the memo defaults to a documented "no" — and the requester is free to escalate or drop it without stigma. Silence stops being a strategy.

What It Looks Like in Practice

This isn't theoretical. Variations of the mechanism have appeared in mid-market companies quietly wrestling with the same problem. A regional grocery chain in the Midwest adopted a version for vendor and partnership decisions after watching a delivery-app integration die in committee while a competitor launched one. A community bank in the Southeast applied it to product pilots, pairing it with a simple rule: pilots under $50,000 need one signature, not five.

The common thread is not recklessness. It is proportionality — matching the weight of the process to the reversibility and shelf life of the decision. Companies that adopt this framing often discover that a majority of their stalled proposals were, by their own criteria, cheap to reverse. They were being governed like mergers when they should have been governed like experiments.

The Objection, Answered

The predictable objection: doesn't a ten-day deadline produce hasty decisions?

It produces timely decisions, which is different. A forced deadline surfaces the real objection early — the stakeholder who would have quietly sat on the memo for a month must now voice their concern within the window, where it can be argued and resolved. Deadlines don't eliminate deliberation; they concentrate it. And for genuinely irreversible decisions, the memo's downside and reversal-cost sections make the case for routing them into the traditional, slower process. The two-week memo doesn't replace governance. It triages it.

Start With One

If you lead a team inside a larger organization, you don't need permission to fix your corner of the approval economy. Pick one category of recurring decision — vendor evaluations under a set threshold, partnership inquiries, internal tooling. Write the memo template. Name the decider. Start the clock.

The opportunities your company loses to delay will never send a farewell note. The two-week memo is how you at least make their expiration visible — and give the next one a fighting chance to arrive on time.