Validation OS

Antes de gastar um mês construindo a coisa errada, rode sua ideia pelo Validation OS. Pesquisa de mercado orientada a evidência, com pontuaç...
2 joined
Profile picture
Validation OS ResearchProfile picture@sidedelaydd·Aug 13

A good idea becomes much stronger when it is supported by evidence.


Great products often begin with intuition. Validation turns that intuition into a clearer and more actionable opportunity.


Before investing months into building, it helps you understand:


• Who experiences the problem most often

• How they currently solve it

• Which alternatives already exist

• What gaps competitors are leaving open

• Which audience is easiest to reach first

• What offer is most likely to earn real commitment


Revenue remains the strongest signal, but you do not have to build the entire product before learning something valuable.


Customer behavior, existing spending, recurring complaints, manual workarounds, competitor reviews and early commitments can all reveal where the strongest opportunity is.


This is why validation is not only about deciding whether to build. It can help you choose a better customer segment, sharpen the problem, improve the offer, adjust the business model, find a practical route to the first customers and build a smaller, more focused first version.


The objective is simple: make your next decision with more clarity and stronger evidence.


You bring the idea. Validation helps uncover the strongest path forward.


What idea are you currently considering building?

Profile picture
Validation OS ResearchProfile picture@sidedelaydd·Aug 12

Why Reddit complaints are more useful than a huge TAM

A slide that says "$50B TAM" tells you almost nothing about whether your idea will sell. A thread with 200 upvotes of people complaining about one specific problem tells you a lot.


TAM is a theoretical ceiling calculated top-down from someone else's market report. It says a market could exist. It says nothing about whether the exact problem you're solving is the reason people would pay, or whether they're already frustrated enough to switch from what they use today.


A concrete complaint thread is bottom-up, specific evidence: real people, describing a real problem, in their own words, publicly and voluntarily. If that thread also has people replying "yes, exactly," "I've been looking for this," or sharing their own duct-tape workaround, that's a far stronger signal of willingness to pay than any market-sizing slide.


This doesn't mean market size doesn't matter eventually — it does, for deciding how big the business could get. But for the first question ("does anyone actually want this enough to pay?"), specific evidence of pain beats an abstract number every time.


---

Curious what this looks like for your own idea? Run it through the — a few minutes, no cost, real evidence back. If you want the full picture (competitors, money flow, acquisition channels, your first 10 customers, a $0–100 smoke test), the is the deeper next step.

Profile picture
Validation OS ResearchProfile picture@sidedelaydd·Aug 12

The fastest way to find where your first 10 customers are

Most founders answer "where will my first customers come from?" with "social media" or "I'll run ads." Neither is a real channel. Here's a faster way to find one.


Go to where the complaint already lives, not where you assume your buyer hangs out.


Concrete example: if you're building an alternative to an existing tool, go read that competitor's 1-star and 2-star reviews on their app store page or review site. The people complaining are already your exact buyer — they're using a solution, actively unhappy with it, and named. Often the review itself, or the reviewer's profile/forum activity, points you straight to the community they're active in (a specific subreddit, a Discord, a Facebook group, a niche forum).


That's a channel: not "Reddit" broadly, but the specific subreddit where these exact complaints get posted. Not "cold email" broadly, but the specific list of people who left a public complaint you can reasonably reach out to.


The fastest path to your first 10 customers is almost never a new channel — it's the one where people are already complaining about the problem you solve.


---

Curious what this looks like for your own idea? Run it through the — a few minutes, no cost, real evidence back. If you want the full picture (competitors, money flow, acquisition channels, your first 10 customers, a $0–100 smoke test), the is the deeper next step.

Profile picture
Validation OS ResearchProfile picture@sidedelaydd·Aug 12

Competition is not proof your idea is bad — this is

"Someone already built that" is one of the most common reasons founders talk themselves out of an idea, and it's usually the wrong reason. Competition proves a market exists and people already pay to solve the problem — that's normally good news.


What's actually a bad sign:


No wedge. You're building the same product for the same buyer with no different angle — same pricing, same feature set, same audience. Without a wedge (a specific underserved segment, a workflow no one else nails, a distribution channel competitors ignore), you're just late.


A market that's shrinking, not just crowded. Crowded and growing is fine. Crowded and shrinking (fewer new entrants, declining search interest, competitors laying off or pivoting away) is a different problem entirely.


A pure price war with no other differentiation. If the only way you'd win is "the same thing, cheaper," margins usually die before you do.


Concrete example: project management tools are an extremely crowded market. Linear entered anyway — but with a specific wedge (speed and workflow built for software teams, not general project management). The crowd wasn't the problem; having no angle would have been.


Check for a wedge before you check for competitors.


---

Curious what this looks like for your own idea? Run it through the — a few minutes, no cost, real evidence back. If you want the full picture (competitors, money flow, acquisition channels, your first 10 customers, a $0–100 smoke test), the is the deeper next step.

Profile picture
Validation OS ResearchProfile picture@sidedelaydd·Aug 12

How I would validate a SaaS idea with $100 before writing code

$100 is enough to get real signal on a SaaS idea before touching code — if you spend it on evidence, not vibes. Here's one way to split it:


$40 — a one-page landing site + waitlist.

Not a full product. Just a clear headline stating the outcome you solve, one screenshot mockup, and an email capture. Tools like Carrd or a simple Framer page work fine.


$40 — a small paid boost to get the page in front of the right people.

Example: if you're targeting Shopify store owners with an inventory-alert tool, that's $40 toward a narrow ad test or a boosted post in a relevant community (where allowed) — enough to get a few hundred targeted eyes on the page, not thousands of random ones.


$20 — pay 3–5 target users for a 15-minute call.

A $5–7 gift card is usually enough to get a real conversation instead of a favor. Ask what they currently do about the problem, what they've tried, and whether they've ever paid for a partial fix. Their existing spend is your strongest signal.


Kill criterion, set in advance: if the landing page converts under roughly 2% to email signups AND none of your paid calls reveal an existing spend or workaround for the problem, that's evidence to stop — not a reason to "market it better."


This isn't a guarantee of anything. It's a cheap way to replace guessing with a small amount of real evidence.


---

Curious what this looks like for your own idea? Run it through the — a few minutes, no cost, real evidence back. If you want the full picture (competitors, money flow, acquisition channels, your first 10 customers, a $0–100 smoke test), the is the deeper next step.

Profile picture
Validation OS ResearchProfile picture@sidedelaydd·Aug 12

3 signs your SaaS idea is probably not worth building

Most bad SaaS ideas don't look bad on paper. They look bad once you check for these three signs.


1. The pain is an inconvenience, not a problem.

People being mildly annoyed by something is not the same as people actively trying to solve it. If nobody has built a spreadsheet hack, a Zapier workaround, or a paid alternative — even a bad one — for the problem you're targeting, the pain probably isn't strong enough to pay for.


2. Nobody complains about the specific thing you're fixing — only adjacent things.

Example: say you're building "AI meeting notes for freelancers." A search through relevant subreddits and forums turns up plenty of complaints about note-taking apps being expensive or clunky — but almost nothing about freelancers wanting AI-generated notes specifically. That's a sign you found a market complaining about the wrong problem. Adjacent frustration isn't validation.


3. You can't name where your first 10 customers would come from.

Not "social media" or "SEO eventually" — an actual community, forum, competitor's review section, or channel where people with this exact pain already gather. If you can't point to it, you don't have a distribution plan, you have a hope.


None of these are guaranteed kill signals on their own. But if an idea hits two or three of them, that's worth pausing on before you build.


---

Curious what this looks like for your own idea? Run it through the — a few minutes, no cost, real evidence back. If you want the full picture (competitors, money flow, acquisition channels, your first 10 customers, a $0–100 smoke test), the is the deeper next step.