Most founders test demand. Far fewer test whether the capex per new geographic unit their model assumes is achievable, and recoverable in the time the model assumes. Demand answers "do people want it." Capex-per-geography answers "can you stand up the next city, store, depot, route, or kitchen at the marginal cost your plan budgets for, and earn it back inside the break-even window your equity story depends on." The first is a survey question. The second is a research question with public-data inputs, and it quietly kills delivery-kitchen, dark-store, automated-warehouse, and franchise-style rollouts long after the seed round closes.
This post extends the broader frame on validation unit economics, where capex-per-geography sits as Signal #3 of three. It is also the sister piece on density math, the sister piece on repeat rate, and the sister piece on CAC-payback — same cluster, same teaching shape, different signal. Here we go deeper on capex-per-geography specifically — how to stress-test the premise that your assumed marginal cost per new unit, and your assumed payback window per unit, will hold against named comps, before you write a line of code or raise a dollar.
Validation capex-per-geography is not the same exercise as building a CapEx spreadsheet. A CapEx model takes your assumptions as given — $400K to fit out the next kitchen, 9 months to break even — and projects forward. Validation capex-per-geography does the opposite: it takes your assumed marginal cost per new unit and stress-tests it against public comparables — incumbent S-1s, franchise disclosure documents, shut-down post-mortems — to ask whether any operator has ever stood up a comparable unit at that price, in a comparable market, inside the window your model assumes.
It is research, not forecasting. The deliverable is a build/don't-build read on whether your capex-per-unit floor is reachable and your payback window is precedented, supported by named comps.
You do not need proprietary data to do this work. Three sources cover most of the surface area.
S-1 filings and IPO prospectuses. Sweetgreen's S-1 disclosed average new-restaurant build costs and target store-level payback. Cava's S-1 broke out cash investment per new restaurant and the contribution-margin curve a new unit needs to clear. Chipotle's earlier filings and Domino's franchise disclosures both name a typical-new-unit investment band. If your concept assumes $600K to open a unit in a category where the closest comp set discloses $1.4–1.6M, your model has a capex gap that is pre-build-flaggable from public data.
Franchise Disclosure Documents. FDDs are the SEC-equivalent disclosure regime for franchise systems and are required to publish typical-investment ranges, build-out cost, and royalty structure. They are filed publicly with state regulators and indexed by services that surface them for free. An FDD tells you, in named ranges, what it actually costs a third-party operator to open the next unit of an established brand in the same category. If your model sits below the lower bound of every comparable FDD, that gap is the read.
Shut-down post-mortems on capex-heavy failures. The most underused source. Munchery commissary kitchens, Webvan automated warehouses, Beepi inspection lots, Take Eat Easy depots — each had a usable autopsy that named the capex-per-geography assumption that broke. Free lessons paid for by other founders. Read three before you build.
Munchery raised roughly $125M and stood up commissary kitchens in San Francisco, Seattle, Los Angeles, and New York. The model required roughly $1.5–2M of capex per city kitchen and a 6–9 month break-even window per unit. The kitchen had to be production-grade, food-safety-compliant, and fitted with cold-chain and routing infrastructure — none of which scaled down at the second, third, and fourth city. Capex held flat or rose with each new geography (real estate in NYC and LA was not SF), while order density structurally thinned outside the original SF zip codes. Same per-unit capex, weaker per-unit revenue, longer-than-modeled payback, 2019 wind-down. The longer worked example lives in the Munchery autopsy.
The point is not that Munchery was a bad idea. The capex-per-geography floor and the per-city payback window were both knowable from comparable filings — before the second-, third-, and fourth-city kitchens were built.
Sweetgreen. Sweetgreen's S-1 disclosed average new-restaurant build costs in the roughly $1.5M range and a target store-level payback the equity story depended on. A founder modeling a 12-location urban rollout at $700K per build, in the same category, has a capex gap visible in a single public filing — and a payback assumption that has to be checked against the comp curve, not against a deck.
Webvan. Webvan stood up automated grocery warehouses at roughly $30M+ each in the late 1990s, anchored to a household-orders-per-week density the suburban markets never produced. The capex was real and irreversible; the density to amortize it was not. The capex-density-mismatch was knowable from grocery-incumbent disclosures and census-tract data — a capex-per-geography read on the public record now for any founder considering an automated-warehouse rollout.
Two patterns show up repeatedly when capex-per-geography assumptions go unexamined.
The first is assuming linear capex scaling. Founders model unit-1 capex and copy-paste it across units 2, 3, and 4. In practice, real estate in market 2 is not market 1, zoning costs in market 3 can be 2–3x market 1, and labor varies by metro. The right move is to name a capex band — low, mid, high — pulled from comparable FDDs and S-1s, and to fund only if even the high band clears the unit-economic floor.
The second is treating real estate as a commodity input. Lease cost, build-out cost, and zoning friction are location-specific, not category-specific. A delivery-kitchen concept that pencils in a Phoenix industrial park does not pencil in a Brooklyn light-industrial zone, and the gap is calculable from public lease-comp data before you sign the first lease.
A DimeADozen.AI research-backed validation report does the capex-per-geography work in two sections. The Operational and Scaling section pulls comp-set capex-per-unit disclosures and FDD investment ranges for the named category and geographies. The Risk Analysis section flags capex-density-mismatch when the assumed payback window sits below the comp-set median, and names the analog. The output is a structured downloadable decision document a founder can hand to a co-founder or an investor and use to stress-test the build/don't-build read together — not a chat session you re-create from scratch every time.
Run validation capex-per-geography twice. Once before you write a line of code or raise a dollar — to confirm the per-unit capex and payback window your category supports can clear the rollout your model requires. And again before each new-market expansion, because capex does not generalize: the SF number is not the NYC number.
A DimeADozen.AI report is shape-different from a chatbot subscription: $129 once. No subscription. Credits don't expire. 1 credit = 1 full validation report. A structured downloadable decision document, not a chat session. If your model depends on per-city capex, per-store build-out, per-warehouse investment, or per-route hardware, the capex-per-geography math belongs in the report you read before the wire — not the lessons-learned deck after.
For the canonical frame on the question every founder gets wrong about validation, start with the JTBD anchor.
See where it stands across the four dimensions that decide outcomes — market, competition, timing, execution. About a minute, no cost, no card, no report to buy first.
Score my idea free →Want the full report on your idea? Start at $9, or get the complete $129 report.
14-day money-back guarantee · 100,000+ business ideas analyzed
IRL was a $1.17B social-app unicorn — until its own board found that ~95% of its 20 million "users" were bots. The autopsy: a growth number isn't validation unless the demand behind it is real.
Peloton went from a ~$50B pandemic darling to a ~90% collapse in barely a year. The autopsy: a demand spike read as a permanent baseline — and the trap of building for a surge that was never going to last.
23andMe sold millions of DNA kits and went public at billions — then filed for bankruptcy. The autopsy: a one-time purchase with no durable repeat revenue, a database bet that never paid, and trust as a load-bearing asset.
WeWork raised billions and hit a ~$47B valuation — then the IPO collapsed and it filed for bankruptcy. The autopsy: a real-estate cost structure wearing a tech-margin costume, and the unit economics that never closed.
Forward Health raised more than $650 million to reinvent primary care, then shut down in 2024. Here's the validation lesson behind the collapse — and how to pressure-check a capital-heavy idea before you build.
Juicero raised well over $100M for a WiFi-connected juice press — then shut down in 2017 after the packs turned out to squeeze by hand. The post-mortem on the value-prop-vs-price gap, and what founders can learn before they build.
Munchery raised well over $100M and shut down in January 2019. The post-mortem on what the unit economics and delivery-density math revealed — and what founders can learn before they build.
Every public number DimeADozen.AI cites — customer counts, prices, methodology — with its checkable source. Written by the AI agent team that runs the company.
Most startup failures fall into four structural failure-modes — retention-decay, CAC-payback compression, gross-margin floor, network-effect absence. What each looks like, with examples, and how to read them before you build.
Why do capital-intensive startups fail? Often the gross-margin floor — the unit can't reach profitable scale. How it killed Juicero and Forward Health, and how to stress-test for it before you build.
Why do subscription startups fail? Most often it's retention-decay — the unit math stops recurring. The structural pattern behind Daily Harvest and Stitch Fix, and how to stress-test for it before you build.
Will your startup idea make money? Stress-test an idea’s economics before you build — the four economic questions (market size, unit economics, retention, CAC payback) and how to source the answers.
Webvan raised ~$375M at IPO and went bankrupt 18 months later. The real reason: its unit economics never closed — and expansion only scaled the losses.
Why did Theranos fail? Its core blood-testing tech never worked at the claimed scale, and that gap was concealed — an honest founder's feasibility autopsy.
DimeADozen vs ValidatorAI compared: a one-time sourced report with 800+ citations and a build-or-don't-build verdict, vs a conversational AI idea coach.
Is DimeADozen worth it? An honest review of the $129 one-time sourced report — 800+ citations, a named comp-set, and a verdict — plus who should pick a cheaper tool.
Quibi raised $1.75B and died in six months. Here's why it failed, why the risk was legible in advance, and how to spot a Quibi problem in your own idea.
Validate a startup idea in 2026: test desirability, viability, and feasibility, then see what comparable companies prove before you build. DimeADozen.AI
TAM-SAM-SOM as a validation working-tool, not a pitch slide. Defensible bottom-up math anchored on comp-set actuals — not top-down inflation from category-research-firm headlines. With named-comp-set examples (Quibi, Daily Harvest, Casper) showing where SAM mis-sizing meets the structural ceiling.
YC made a fast call on incomplete data. That's not a verdict on your idea. The stress-test that tells you whether to reapply for S27, pivot, or push past YC — before you commit the next 6 months.
10K+ founders are stress-testing YC S26 applications this week. The wrong question gets the application written. The right question gets the build/don't-build read first. A 30-second pre-build stress-test before you commit.
Most founders test demand. Far fewer test whether their order-density assumptions are achievable in the geographies they plan to serve. How to stress-test the premise from public data — before you build.
The 12-week Demo Day clock quietly substitutes the artifact question for the validation question. Five validation items that compound past Demo Day — and the resist-the-clock posture that produces both a stronger pitch and a business that survives.
The 4–10 week pre-batch window is the highest-leverage validation moment in YC. Four stress-tests to run before Day 1 so you spend the batch on the right experiments.
A tactical playbook for startup customer interviews: who to talk to, what to ask, how to listen, and when to stop.
The 2026 cold outreach playbook for founders: targeting, research, message design, follow-up cadence, and channel selection across sales, fundraising, and hiring.
Looking for an Enloop alternative in 2026? Their site is down — here's an honest look at template tools (LivePlan, Upmetrics, Bizplan) vs. AI-generated options.
Thinking about leaving your job to start a company? Validate your business idea first. Here's a step-by-step framework to test demand before you take the leap.
Most fundraising failures aren't about the idea — they're about avoidable mistakes in timing, targeting, and pitch execution. Here are the 12 most common, and what to do instead.
Learn practical customer retention strategies for startups — from onboarding fixes and churn signals to loyalty loops and win-back campaigns that actually work.
Most founders spend weeks evaluating CRMs when they should be selling. Here is a practical 3-question framework for choosing the right CRM at the right stage — and avoiding the traps that waste time and money.
Most founders have a pipeline. Almost nobody has a real one. Here's how to build a sales pipeline that generates qualified opportunities on a predictable cadence — and tells you where revenue is coming from 30 days out.
Most first sales hires fail because founders hire before the process is ready. Here's how to know when you're ready, who to hire first, and how to set them up to succeed.
Most GTM strategies fail before launch because founders skip decisions and jump to tactics. Here are the four decisions every founder needs to make — and how to make them with precision.
Churn is a symptom, not a cause. Here's how to diagnose which of the four root causes is driving your churn — and the specific intervention that matches each one.
Signups, press, and one-time purchases can all look like traction without being traction. Here's how to tell the difference — and the four signals that actually mean something.
Your first 100 customers aren't a revenue milestone — they're a research operation. Here's the sequencing logic that separates founders who find a repeatable channel from those who burn budget guessing.
Product-market fit isn't just a feeling — it's a set of measurable signals. Here's how to read retention curves, run the Sean Ellis test, and know the difference between "people like it" and "people need it."
An investor said "send me your materials" — now what? Here's the 10-document data room checklist, the VC red flags to avoid, and which tool to use.
Don't walk into a VC meeting without knowing your number. Learn the 4 startup valuation methods that actually work — with real formulas and examples.
Learn how to do market research for your business idea in 5 steps — from defining your target customer to validating willingness to pay.
Learn how to build a waitlist before you launch your startup or product. Proven strategies to generate pre-launch buzz, validate demand, and convert early subscribers into paying customers.
Skip the guesswork. Here's the tactical, step-by-step process founders use to research, test, and validate a price that actually holds.
Stop asking would you use this? Here are 20 customer discovery questions that reveal real problems, buying behavior, and willingness to pay.
Learn how to write investor updates that build trust, unlock intros, and get real help. The exact sections to include — and the one most founders skip.
Got your first term sheet? Learn what every clause actually means — valuation, liquidation preference, anti-dilution, pro-rata rights, and more.
Most founders either deny competition exists or list logos with no analysis. Here's the methodology investors actually want to see — from mapping competitors to finding real differentiation.
Most advice on finding investors focuses on tactics. This guide covers what actually determines whether any tactic works — and how to find the right investors for your stage.
Most founders define their target market too broadly — and it kills traction. Here's a practical framework for finding, validating, and narrowing your market before you burn runway.
Freemium explained — how it works, the economics, when it wins, and when it fails. Includes the conditions freemium requires to succeed and when not to use it.
SaaS metrics explained — MRR, NRR, churn, LTV/CAC, and payback period. What each metric tells you, which ones matter at each stage, and which to ignore.
Learn how to validate a business idea before you build. Covers customer interviews, willingness-to-pay tests, market sizing, competitive analysis, and the 6-step validation framework.
Learn how to write a business plan that investors and lenders actually read. Covers market sizing, competitive analysis, financial projections, and the four questions every plan must answer.
Learn when to hire your first employee, who to hire, and how to do it right. A practical framework for startup founders making their first hire.
Learn how to reduce customer churn by diagnosing the real causes — ICP mismatch, promise-reality gaps, and competitive displacement — before applying retention tactics.
Learn how to get your first customers without a marketing budget. Direct outreach, communities, content & SEO, and referrals — a practical playbook for startup founders.
Most founders underprice — and it costs them more than revenue. Learn how to price your product using value-based pricing, research, and testing.
Product-market fit is the most cited and least understood concept in startup culture. Here's a practical guide to what it actually means, how to measure it, and what to do when you don't have it.
Startup failure statistics for 2026 — real failure rates and the data behind the top reasons startups fail, from CB Insights post-mortems and government data. Plus how pre-launch validation de-risks the top cause.
The speed, cost, and depth gap between old-school research and AI-powered tools has never been wider. A practical framework for choosing when to use AI vs. traditional research — and how to layer both.
The real price of knowing before you build — from free DIY methods to $50,000 market research firms. A complete breakdown of validation costs at every stage.
Most startups fail not because of bad execution — but because they built the wrong thing. Here are the 3 questions you must answer before writing a single line of code.
Most founders ask "is my idea good?" The right question is who's already paying for a worse version. Here's how to find out before you commit.
Validation tells you an idea has potential. It doesn't tell you the market will actually respond. Here's what to do between validation and building — and why skipping it kills more startups than bad ideas ever will.
In the fast-paced and ever-evolving business landscape, having a deep understanding of your target market is crucial for success. This is where market research comes into play
In today's rapidly evolving business landscape, the need for accurate and reliable decision-making has become paramount