The problem
Building a useless product—or a useful one for the wrong segment—is one of the quietest ways to burn runway. The problem is not only engineering spend: it is the full opportunity cost, morale drag, and credibility loss with early supporters. Teams confuse activity with validation: full sprints, green merges, applauded demos, yet no durable signal that anyone changes behavior or opens budget for the solution. The "useless" product can be technically impressive; it can even collect praise. It does not solve a pain that is strong enough, timely enough, for the right payer, or better than an alternative already in place. Hidden costs pile up: repositioning refactors, technical debt from pilot-specific features that fail to generalize, support for vague promises, and sales time on cycles that never close. Founders also underestimate the psychological cost of sunk investment: the more you spend, the harder it is to admit the direction was wrong, which delays the needed pivot. In B2B, useless products show up as endless POCs, pilot roadmaps that do not renew, and "interesting" without a budget line. In B2C, downloads without retention, or "neat" reviews without monetization, tell the same story. Partners and employees who backed the vision feel misled when the gap between narrative and usage widens, which compounds the cost in the next hiring round and in the next partnership conversation.
Why it fails
Naming the cost of a useless product lets you treat failure as a governable financial risk, not a personal flaw. While failure stays fuzzy ("the market was not ready"), you avoid crisp decisions. Once you quantify engineering time, cash burn, and opportunity cost (other hypotheses left untested), stopping or pivoting becomes more rational. For stakeholders, transparency on that cost kills toxic "almost" narratives: almost product-market fit does not pay payroll. In a Lumor-adjacent approach, you want early proof the product deserves to exist: behavior, payment, or repeated commitment under realistic constraints. Useless-product cost also includes brand dilution: promising a global solution too early when value is local burns trust for later iterations. Understanding the cost also right-sizes validation budgets: better to spend ten thousand euros to kill an idea in six weeks than one hundred thousand to keep it alive eighteen months without signal. Team culture wins too: documented learning is celebrated alongside shipping, which reduces shame about exploring a dead end. Boards and mentors can help only when the burn is legible; otherwise advice devolves into generic encouragement that preserves a slow leak.
A concrete method
Measure and prevent "no-market" product cost
1. Full cost sheet — Include salaries, contractors, cloud, tools, marketing, and especially founder time (value it at replacement cost).
2. Explicit opportunity cost — List two other hypotheses you did not test because of current focus; estimate plausible upside.
3. Early truth criteria — Before build, define which signals (payment, repeat use, referral) invalidate or validate the bet.
4. Runway cap per hypothesis — Allocate a time and money envelope; at depletion without signal, stop or pivot is mandatory.
5. Zero-vanity review — Ban metrics that rise without linkage to behavior or cash; require a logical chain to a purchase decision.
6. Paid or committed interviews — Small customer cost filters noise from free compliments.
7. Split build and learn — Ship the smallest artifact that tests value, not the smallest artifact that wows a demo.
8. Promise register — Every commercial or roadmap promise maps to evidence; otherwise it is future cost debt.
9. Blameless post-mortem — When you cut, document missed signals so you do not repeat the same hope curve.
10. Cost-per-proof table — Divide cumulative spend by the number of independent proofs obtained on pain, payer, and advantage versus alternatives.
11. External benchmark — Compare your spend pace to peers at a similar stage; unexplained gaps often hide scope creep or weak ICP focus.
These practices make waste visible before it becomes product identity.
Example
A B2B team spent fourteen months on an "talent optimization" platform with AI scoring, HR dashboards, and ATS integrations. Demos impress; two free pilots linger without converted budget. Direct cost exceeds eight hundred thousand euros; opportunity cost includes a vertical positioning never explored where three interviews would have surfaced sharper pain. When they map signals, they realize no monetary success criterion was set at the start. After stopping, a narrower MVP for one role and one HR metric cuts burn and secures deposits. Second case: a consumer workplace wellness app buys users with campaigns, but day-thirty retention is weak and no pricing model survives a real willingness-to-pay test. Useless cost includes content production, influencers, and UI refactors that masked the absence of a paid problem. Pivoting earlier to small-team B2B with a manager license would have cost less than twelve months of artificial growth. Third example: an internal tool built for one customer becomes a "product" without generalizing; custom support explodes. Real cost is three full-time people handling exceptions. The lesson: utility for one is not a market. A fourth vignette: a hardware-adjacent software team chases regulator-friendly checklists before any user pays for the core workflow; the "compliance-ready" label delays pricing conversations until the balance sheet cannot wait.
What to do now
On your current initiative, calculate total spend to date (time × rate, cash, tools) and divide by the number of independent proofs you hold on pain, payer, and advantage versus alternatives. If the ratio is high with few proofs, schedule a short window for a decisive signal (presale, paid pilot, constrained usage) or for a cut. Share the number with co-founders to break sunk-cost momentum. If Lumor or a blunt peer is available, simulate a skeptical buyer: what is missing to sign this week? Treat answers as a validation backlog, not a feature backlog. Set an audit date: without a budget line or repeated commitment, you return to strict exploration mode. Archive the spreadsheet to compare in thirty days: did you buy signal or comfort? Finally, align hiring and external comms: do not promise scale-up velocity if proofs are still lab-grade, or the cost of disillusionment will stack on top of the technical bill. Add a single slide to your internal weekly review: cumulative spend, proofs gained this week, and the next cheapest experiment that could falsify the thesis.
Related reading
Lumor puts your idea in front of 13 AI roles to stress-test assumptions, surface blind spots, and deliver a verdict, scores, and an execution plan.