Before you buy software, understand the problem. This walks you from the symptom, through the friction, down to the real root cause — then points you at the tools that fix that, not the thing you first assumed. Diagnose the disease before you prescribe the medicine.
The most expensive mistake a founder, leader or maker makes is buying software for a problem they don't fully understand. People describe problems as symptoms ("our launch isn't getting traction"), almost never as root causes ("visitors don't trust us yet, so they don't convert"). A wrong tool doesn't fix operational chaos — it scales it faster. And it has to be crystal clear not just to you but to your whole team: if ten people are solving ten different problems, you'll buy ten tools and fix none. So this tool forces the depth first — symptom, then friction, then root cause — and only then names the software.
Watch how tool-buying usually happens: something hurts, someone Googles "best CRM" or "best project management tool", a comparison page anoints a winner, a subscription begins. Three months later the pain is intact and the tool is shelfware — not because the tool was bad, but because the category was wrong. "We need a CRM" turns out to mean "sales doesn't follow up", which turns out to mean "nobody owns follow-up" — an ownership problem no software fixes. The diagnosis wizard above exists to interrupt exactly that chain: it refuses to recommend anything until you've walked from what hurts to why it hurts, because the second question changes the answer more often than not.
The wizard's three steps mirror how operational problems actually nest. The symptom is what you'd complain about to a friend: revenue is flat, everything feels chaotic, customers leave. The friction is where the symptom shows up in daily work: leads go cold, handoffs drop, the same questions get answered forever. The root cause is the mechanism producing the friction: there's no single place where work lives, nobody sees the pipeline, knowledge exists only in one person's head. Tools operate at the root-cause level — that's why the same symptom ("we're drowning") routes to completely different software depending on the two answers underneath it.
Thirty-six paths cannot hold the full messiness of a real company, and pretending otherwise would break the point of the exercise. The wizard covers the root causes that account for most small-business operational pain — visibility, ownership, repetition, trust, follow-up, knowledge — but some problems live outside software entirely: a co-founder conflict, a product nobody wants, a price that's simply wrong. If your honest answers don't feel like they fit any path, that misfit is itself a diagnosis: your bottleneck may not be an operations problem, and the most valuable output of ten minutes here might be crossing "buy a tool" off the list before it costs you a year of subscriptions.
Two habits make the diagnosis dramatically more accurate. First, answer from evidence, not aspiration: pick the symptom that's actually costing money this quarter, not the one that's fashionable to worry about. Second, run it as a team exercise: have each person who touches the problem walk the wizard independently, then compare paths. Agreement means you've found it. Divergence is gold — it means the team is fighting different fires, which explains every stalled tooling discussion you've had. The conversation that follows ("wait, you think the problem is follow-up?") is routinely worth more than the recommendation itself, because alignment is the prerequisite for any tool working.
A correct diagnosis plus a correct tool still fails on adoption — the graveyard of SaaS is full of right answers nobody used. The pattern that works: one owner (a name, not a committee), one workflow moved completely into the new tool (not a pilot limping alongside the old spreadsheet), a two-week checkpoint against the original root cause ("are handoffs still dropping?"), and only then expansion. Resist the urge to configure everything on day one; tools earn complexity gradually or die from it immediately. And keep the diagnosis: written down, it's the success criterion that tells you in a month whether the tool actually treated the cause or merely reorganised the symptom.
Diagnoses expire. The bottleneck that defined your company at five people is usually solved — and replaced — by fifteen; the tool that fixed visibility at one stage becomes the silo of the next. Re-run the wizard whenever the ground shifts: headcount doubles, a new channel starts working, a key person leaves, growth stalls without obvious cause. Ten minutes per quarter is enough. Constraints move through a company the way water finds new low points, and the teams that stay fast aren't the ones that never develop bottlenecks — they're the ones that notice each new one while it's still small enough to fix with a Tuesday afternoon and the right tool.
Run enough diagnoses and a humbling pattern appears: a meaningful share of root causes dissolve with a decision rather than a subscription. "Nobody owns follow-up" is fixed by a name on a whiteboard before any CRM helps. "The same questions get asked forever" is fixed by one afternoon writing the answers down — the wiki tool comes later, if ever. "Handoffs drop" is often a missing agreement about who hands what to whom, which no project board can invent. The wizard will still point you at software when software is the answer — but hold every recommendation against the question "could we fix this with a rule this week?" first. Tools amplify decisions; they don't make them.
The wizard ends with a diagnosis and a recommendation; the natural next step is choosing between the two or three honest candidates in that category. That's what our Tool Finder does: a twenty-second wizard that matches your size, budget and working style against the tools we've actually reviewed — no pay-to-play rankings, real pricing, and honest trade-offs per pick. Diagnose here first, then let the Finder narrow the category to a shortlist; between the two, you'll have done more rigorous tool selection than most companies manage with a consultant — for exactly zero euros.
In three steps it moves from the symptom you feel, to where the process breaks (the friction), to why it breaks (the root cause) — then recommends the tool category that actually addresses the root cause, not the surface symptom.
No — it's a structured decision tree that runs entirely in your browser. Nothing is sent, stored or processed on a server, and there's no cost or account.
Because most tool purchases fail: people buy for the symptom, not the cause. Naming the real bottleneck first means the tool you pick actually solves your problem instead of scaling the chaos.
The paths cover the most common operational bottlenecks. If none fit precisely, use the Tool Finder to browse by category, or the honest reviews to compare options directly.
Blogger, teacher or toolmaker? Put this calculator on your own page — free forever, no strings. Copy the snippet below (the credit link is appreciated and keeps the tool free):
This tool is free and runs entirely in your browser. The link above is an affiliate link: we may earn a commission if you sign up, at no extra cost to you, and it never changes our honest take.
New dossiers, cost-traps we found, and tools that earned a keep — no hype, no sponsored-disguised-as-advice. Unsubscribe anytime.