The idea
Marcus was a developer who had spent three years building software for a construction supply company. He noticed that small contractors (plumbers, electricians, two-truck painting crews) were often owed thousands of dollars in late invoices. His idea was an app that would automatically chase unpaid invoices with polite text reminders, then escalate to firmer messages, then offer the customer a one-click payment link. Price: $39 a month.
His reasoning, in his words: "Contractors lose money every month to late payers. They hate chasing people. This does it for them, and it pays for itself with one recovered invoice."
He had built about 70 percent of it on nights and weekends and had spent roughly $6,000 on design and a payments integration.
The scorecard
- Market — 6/10. There are hundreds of thousands of small contractors in the US, so the raw number is fine. The problem is that the market is crowded with accounting and invoicing tools that already include reminders. Marcus would be competing with features inside products contractors already pay for.
- Problem — 2/10. This is what killed it. When Marcus finally interviewed twelve contractors, ten said late payment was annoying but not a top-five worry. Most of their late payers were repeat clients who always paid eventually. Several said they deliberately did not chase hard because the relationship mattered more than a 30-day delay. The problem existed, but it was not painful enough to pay to remove.
- Money — 5/10. $39 a month is reasonable, and software margins are high. But with low urgency, customers would cancel the first month they did not have a late invoice, so the real lifetime value was a fraction of what his spreadsheet showed.
- Distribution — 3/10. Marcus had no audience among contractors and no plan beyond paid ads. Contractors are notoriously hard to reach with software ads. They are on job sites, not browsing app directories.
- Founder Fit — 5/10. Strong technical ability. Little understanding of how contractors actually think about money, clients, and time.
The verdict: DIES
Exactly why it died
Marcus built a painkiller for a headache nobody had. He had seen a real pattern (late invoices are common) and assumed the pattern was painful. Those are different things. A problem is only worth building for when the people who have it are already spending time, money, or attention trying to fix it.
The evidence was there before he wrote any code. If contractors were desperate to chase invoices, they would already be using the reminder features inside QuickBooks or Jobber, which most of them had and ignored. Nobody had turned those features on. That was the answer.
The second failure was order of operations. He built first, then interviewed. Twelve conversations, which took him eight days, would have saved him six months and $6,000.
What the test would have flagged
The pressure test would have marked the Problem category as the fatal flaw and asked one blunt question: what are contractors doing about this today? When the honest answer is "mostly nothing, and they are fine with that," the idea is in trouble no matter how good the software is.
What happened
He launched to a small paid-ad campaign, spent $2,400, got 41 trial signups, and kept 3 paying customers after 60 days. He shut it down in month five.
The lesson
A common problem is not the same as a painful problem. Before you build, find out what people are already doing to solve it. If the answer is nothing, they are telling you the problem is not worth their money.