Capital

What does money buy, and what does it cost?

1. 01Reference onlyEvidence quality: medium

   Speed versus efficiency: when deliberately inefficient growth is rational

   We name the work that informed the idea and hold none of its content.

   Extracted pattern

   • Prioritising speed over efficiency is only rational when a market is genuinely winner-take-most and the window is closing.
   • The strategy is a bet on market structure, not a growth technique.
   • Most companies are not in that market, and copying its behaviour destroys them.

   Decision pattern

   • Situation. A competitor is growing faster and the founder feels pressure to match.
     Move. Test whether the market rewards being first at scale — network effects, high switching costs, exclusive supply. Only then accept inefficiency.
     Trade-off. Speed burns capital and quality; if the market is not winner-take-most, both are lost.
     Breaks when. Customers can switch easily, supply is abundant, or the company has no access to the capital the strategy requires.

   Practical implication

   Before matching a competitor's speed, establish whether this market actually pays a premium for being first at scale. If it does not, efficiency is the winning move and their spending is your opportunity.

   Counter-pattern / contradiction

   • Bootstrapped and service businesses win by margin and durability; speed at any cost is straightforwardly wrong for them.

   Failure modes

   • Adopting scaling behaviour on bootstrapped cash.
   • Reading a competitor's spending as evidence of a real land-grab.

   What was measured

   market share velocity · retention by cohort · capital available versus burn required

   Stage relevance

   Traction · Scaling

   Source

   Aurygine · 2018-01-01
2. 02SourcedEvidence quality: high

   Default alive: knowing whether the company survives without new money

   Summarised in Aurygine's words from a publicly readable source, linked below.

   Extracted pattern

   • Every founder should be able to answer, without a spreadsheet session, whether the company reaches profitability on current cash and current growth.
   • Not knowing the answer is itself the finding.
   • Once the answer is no, the choices narrow to: grow faster, cut cost, or raise — and delay removes options.

   Decision pattern

   • Situation. Spending exceeds revenue and the founder is unsure how serious it is.
     Move. Compute months of runway at current burn, then ask whether current growth closes the gap before the cash runs out.
     Trade-off. Forces an uncomfortable conversation earlier than the founder would choose.
     Breaks when. Revenue is highly seasonal or lumpy, where a single month's burn misreads the year.

   Practical implication

   Keep the runway number visible and honest. The decision that matters is not 'are we doing well' but 'does the company survive on the cash it already has'.

   Counter-pattern / contradiction

   • Deep-tech and infrastructure companies are structurally default-dead for years by design; the measure there is milestone risk, not runway alone.

   Failure modes

   • Treating a funding conversation as a plan.
   • Cutting cost so late that the cut has to be twice as deep.

   What was measured

   months of runway · monthly burn · growth rate · gross margin

   Stage relevance

   First customers · Traction · Scaling · Turnaround

   Source

   Paul Graham · 2015-10-01 original
3. 03Aurygine synthesisEvidence quality: high

   Customer-funded growth: making the buyer your investor

   Aurygine's own synthesis across observed practice. No single work is reproduced.

   Extracted pattern

   • A customer who pays before the thing exists has told you more than any survey could.
   • Deposits, pilots and prepaid pilots are financing instruments, not just revenue.
   • If nobody will pay in advance, the problem is usually urgency, not price.

   Decision pattern

   • Situation. Founder needs money to build, has no capital and no track record.
     Move. Sell a paid pilot to three buyers with a fixed scope and a delivery date, and build only what the pilot requires.
     Trade-off. The first version bends towards three specific buyers and may not generalise.
     Breaks when. The product needs heavy upfront infrastructure before any value exists, or the buyer cannot legally prepay.

   Practical implication

   Before raising or spending, test whether the problem is urgent enough to be prepaid. Prepayment is the cheapest validation instrument available to a founder and it funds the build at the same time.

   Counter-pattern / contradiction

   • Capital-intensive and deep-tech companies routinely cannot be customer-funded early; milestone financing fits better.

   Failure modes

   • Building for six months on savings, then discovering the urgency was imagined.
   • Discounting the pilot so heavily it proves willingness to try, not willingness to pay.

   What was measured

   prepaid pilots signed · cash collected before build · pilot-to-contract conversion

   Stage relevance

   Idea · Pre-revenue · First customers

   Source

   Aurygine · 2026-01-12
4. 04Aurygine synthesisEvidence quality: high

   Utilisation and price: the two levers a service business actually has

   Aurygine's own synthesis across observed practice. No single work is reproduced.

   Extracted pattern

   • A service business grows through sold hours and price per hour. Everything else is downstream of those two.
   • Raising price on new customers only is the lowest-risk experiment available.
   • Unsold capacity is a cost that never appears on an invoice.

   Decision pattern

   • Situation. Revenue is flat and the founder is already working full weeks.
     Move. Measure utilisation honestly, then raise price for new work by 10–15% and hold it for one quarter.
     Trade-off. Some prospects are lost; the ones lost were usually the least profitable.
     Breaks when. Utilisation is low because demand is weak — then the problem is acquisition, and a price rise makes it worse.

   Practical implication

   Check utilisation before you check marketing. High utilisation and flat revenue is a pricing problem; low utilisation is a demand problem. They need opposite moves.

   Counter-pattern / contradiction

   • Software businesses have near-zero marginal delivery cost, so utilisation thinking misleads them.

   Failure modes

   • Adding staff before price has been tested.
   • Counting booked hours instead of paid hours.

   What was measured

   utilisation % · average price per engagement · repeat rate · days to payment

   Stage relevance

   First customers · Traction · Mature

   Source

   Aurygine · 2026-03-05
5. 05Aurygine synthesisEvidence quality: high

   The first hire: buying back the constraint, not the discomfort

   Aurygine's own synthesis across observed practice. No single work is reproduced.

   Extracted pattern

   • Hire against the constraint that is provably costing revenue, not against the task you enjoy least.
   • A hire is a recurring cost with a notice period — price it as twelve months, not one.
   • If the work has never been written down, it cannot be delegated yet.

   Decision pattern

   • Situation. The founder is overloaded and considering a first hire.
     Move. Log two weeks of work, identify the activity blocking revenue, document it, then hire narrowly against that.
     Trade-off. Two weeks of delay while the constraint is proven.
     Breaks when. Demand is collapsing — then the answer is not a hire at any speed.

   Practical implication

   Prove the constraint before you pay for it. Write the role from two weeks of real logged work, and check the company still has cover if the hire takes three months to pay back.

   Counter-pattern / contradiction

   • Venture-funded teams hiring ahead of demand is a deliberate, funded bet — not a template for a bootstrapped company.

   Failure modes

   • Hiring a generalist to absorb undefined work.
   • Committing to salary from a single large contract that has not been renewed.

   What was measured

   revenue per founder hour · work turned down · cash cover in months after the hire

   Stage relevance

   First customers · Traction

   Source

   Aurygine · 2026-03-20