I Almost Built a Startup This Week. The Evidence Said No — In One Afternoon.

title: "I Almost Built a Startup This Week. The Evidence Said No — In One Afternoon."
published: true
description: "I found a hot market, a funded competitor, and a technical edge. Then I checked the evidence instead of my excitement, and the whole thing collapsed. Here's the checklist that saved me six months."

tags: discuss, startup, career, ai

I nearly threw the next six months of my nights and weekends at a startup idea I was genuinely excited about.

Hot market. A funded competitor proving people cared. A technical angle they didn't have. Every signal a builder waits for, all lit up at once.

I didn't build it. And the only reason is that I made myself answer four questions with evidence before I let myself open an editor. The idea died in about one afternoon — and that was the best possible outcome.

If you're sitting on an idea that feels obviously right, this is the checklist I wish I'd run years earlier.

The setup: everything looked green

I'd been deep in one problem for weeks and had built two small open-source things around it. Then I found a startup doing something adjacent — slick site, 1,000+ GitHub stars, a strong Product Hunt launch, clearly funded.

And my brain did what every builder's brain does:

"The market's validated. A competitor exists. I have an edge. This is my lane."

That exact feeling — validated market, real competitor, personal edge — is the one that separates you from six wasted months. So instead of building, I opened a list of questions and refused to write a line of code until I'd answered them honestly.

Question 1: Does the competitor actually make money?

This is the one everyone skips, because a funded, popular competitor feels like proof the business works.

It isn't.

I went looking for the competitor's revenue, paying customers, contracts — anything. What I actually found: the product is free forever for individuals, enterprise is "custom pricing," and the public evidence stopped at "early proofs of concept." Trials, not confirmed paying customers. Even the funding number I could only find self-reported.

That reframes everything:

Signal	What it actually proves
1,000+ GitHub stars	People are curious
Strong Product Hunt launch	People clicked once
"Early POCs"	Someone's trialing it for free
Revenue	...no public evidence

I had been about to treat a competitor's marketing traction as market validation. Those are different things, and confusing them is how people build businesses nobody pays for.

Question 2: Is my technical "edge" actually mine?

My angle felt novel. So I searched to see if it was.

It wasn't. Even a little.

There was an entire wave of 2026 research on exactly my idea — papers, open-source implementations under permissive licenses, a big lab's system, a paper whose title was basically my pitch.

"I've never seen a startup do X" is not the same as "X is novel." Startups are a lagging indicator of research.

By the time an idea feels like an obvious wedge to a solo engineer, a dozen labs have usually been on it for a year. My edge wasn't an edge. It was a well-known direction I'd rediscovered on a weekend.

Question 3: Does my thing even work?

Before deciding to sell my defense, I finally ran the honest experiment I'd been avoiding. Four setups, measuring two numbers that must always travel together: how many attacks it stopped, and how many legitimate actions still worked.

My tool caught attacks the alternatives missed. Great.

It also blocked 100% of the legitimate actions.

The reason was almost funny, and it doesn't matter that it's in my niche — the shape is universal: my clever filter couldn't tell a legitimate action from a malicious one, because they arrived looking identical. Useful signal, unusable product. I was one weekend of excitement away from shipping something that blocks every real thing a user tries to do. The experiment cost an afternoon. Finding this out from angry users would have cost six months.

Question 4: Is it crowded where I'm weak?

"Everything's crowded" is a lazy no. This was a specific one: the exact approach I'd bet on was being pursued by funded startups, big-lab research teams, and free open-source projects simultaneously — and the hard, defensible part was precisely where a solo engineer competes worst against funded teams with a head start.

Crowded isn't automatically a no. Crowded at the exact layer where you're weakest is a no with reasons.

What the evidence actually recommended

Add it up:

• Market real, but willingness to pay unproven — even for the funded incumbent.
• My "edge" is a known research direction, not a wedge.
• My prototype has real signal but a fatal flaw I can't yet fix.
• The competition is thickest exactly where I'm weakest.

So: don't build the startup. Not "never." Just "not on this evidence, not yet."

But the same afternoon clarified what was worth my time. The benchmark I'd built — the thing that measures how well anyone's defense works — isn't a competitor to anyone. It's the referee. That's an uncontested, useful role, it builds exactly the reputation that leads to paid work, and nobody's fighting me for it.

The part that generalizes (this is why I'm writing it)

You don't need to care about my niche to use this:

• A competitor's popularity is not proof of a business. Find the money, or admit you can't.
• "Nobody's doing this" is not proof of novelty. Check the research — it leads startups by years.
• Run the honest experiment before you fall in love. Measure the failure case, not the demo.
• "Crowded" only matters when it's crowded where you're weak.

None of this is anti-ambition. It's the opposite. The whole reason to check the evidence fast is so you spend your limited nights and weekends on the bet that survives the checking — not the one that merely survived your excitement.

My idea died in an afternoon. It was the most productive afternoon I've had in months.

---

Have you ever killed an idea early and been glad you did — or shipped one you should've killed? I want the war stories, both directions. 👇

I write about backend engineering, building things, and the honest math behind whether they're worth it. Follow me here if that's your kind of thing. 👋