Skip to content
WhittleOSWhittleOS
← All guidesValidation tools6 min read

From a complaint to a customer: where the two products diverge

A ranked complaint tells you somebody is annoyed. Whether they would pay, whether you can reach more of them, and whether one platform can end it are separate questions — and they are answerable before you build.

By Boris Binyaminov ·

Read on
2026-09-19
The concession
Our run did not read Reddit
The axis
What happens after the complaint

Start with the concession, because it is measured rather than polite: their product reads Reddit and ours, on the run we publish in full, read 3 hosts — and Reddit was not among them. If Reddit is where your buyers are, that settles it. What this page is about is the step after the complaint has been found and ranked, which is where the two products stop resembling each other.

The path from a complaint to a paying customer

Step

Their published features

Ours
Find the complaintScans of chosen subreddits, with evidence attached per pain pointA search across public sources, which on our published run were not Reddit
Rank itAI scoring and ranking by severity, published as a featureSeverity recorded per problem, then used as a gate rather than a ranking
Turn it into an ideaAI solution ideas per pain point, two or ten depending on the planCandidate ideas sourced, then most of them rejected
Decide whether to build itTheir page describes reports, not a verdict10 published checks, and an empty shortlist when none pass
Know what to do on MondayNot described on their pricing pageOne recommended first move with a condition for stopping

Their column is their own published feature list on 2026-09-19 and nothing else; where their page does not describe a step, the cell says so rather than claiming they cannot do it. We have not run their product.

The first three rows are the same job done differently, and reasonable people will prefer either. The last two are the ones worth choosing on, because a ranked list of complaints and a decision are different things to own on a Monday morning.

The specifics behind their column, with the page each was read from:

  • AI scoring and ranking of pain points (pricing page feature list)
  • Up to 10 pieces of evidence per pain point on Starter, 20-25 on Professional (pricing page comparison table)
  • AI solution ideas per pain point: 2 on Starter, 10 on Professional (pricing page comparison table)
  • Analysis timeframes of 7, 30 and 90 days (pricing page comparison table)

Recorded in our own competitor module with the page each came from, read on 2026-09-19. Facts they publish about their own product, not judgements about it.

A complaint tells you somebody is annoyed. It does not tell you whether they would pay, whether you can reach more of them repeatedly, whether the product that fixes it needs a human attached to every customer, or whether one platform can end it. Those are separate questions, they are answerable before you build, and on our side they are 10 published checks that can each fail outright.

What that costs in candidates

On the published run, the sweep collected 56 documented problems, of which 32 carry a link you can open. Those became 69 candidate ideas — and then 36 of them were rejected, leaving 5.

The best of what survived came back VALIDATE at 52, with the next move written out: ship a narrow landing page targeting the single-user pipeline wedge and test organic community response before writing code.

That rejection rate is the product, not a shortfall in it. A tool whose published feature is solution ideas per pain point is optimising for a full list; a gate is optimising for the hours you would otherwise spend on the 36 that did not work. Which one you want depends entirely on whether you are still looking or already deciding.

What to do with a complaint you already have

The gap between the two products is a procedure, and it is short enough to run by hand on any complaint either tool hands you.

  • Name the buyer, not the audience. "Freelancers" is an audience. "A freelancer on monthly retainers who bills three or more clients" is a buyer, and the difference is that you can go and find ten of the second kind this afternoon.
  • Check whether the problem comes back. Read the complaint for an end date. A migration, a launch, a filing — those are projects and they finish. A routine does not, and only a routine supports a monthly price.
  • Check that you can reach more of them the same way. One thread is one thread. Before anything else, find the second and third place the same buyer talks, and write down how you would get in front of them again next month without paying for it.
  • Make the smallest paid offer that would settle it. Not a waitlist. A price on a page, a pre-order, or a paid pilot with a stated scope — something where the answer is money or silence rather than encouragement.
  • Write the bar before you look. How many of the people you reach have to act for you to continue, and what you do if they do not. Decide it while you are still able to.

None of that needs either product. Both tools shorten the first step; the rest is the same work whichever one found the complaint, and it is where the decision actually gets made.

Their plans, as published

PlanPrice

What the page states

Starter$19/month20 scans a month, up to 2 subreddits per scan, 7-day free trial
Professional$49/month300 scans a month, up to 5 subreddits per scan, PDF idea reports

From

their pricing page

on 2026-09-19; they advertise 4,000+ founders. Theirs is a subscription and ours is a one-off pack from $19 for 2 credits, which is a different commitment rather than a different price.

The billing shapes follow the products. Monitoring a set of communities is an ongoing job and a subscription fits it. Settling whether one market is worth your next six months is not ongoing, and a monthly bill for it is a bill you forget to cancel.

When theirs is the better purchase

  • Reddit is specifically where your buyers are. Their product is built for it and our published run did not read Reddit at all.
  • You want to watch a set of subreddits over time rather than settle one question. Theirs is a subscription built for monitoring.
  • You want many candidate problems to browse. Ours is built to throw candidates away.
  • You are earlier than a decision — still looking for what to work on rather than checking something specific.

The first is the one to take seriously: our own published run is the evidence for it, and it is evidence against us.

The short version

  • Their product reads Reddit. Our published run read 3 hosts and Reddit was not one of them. If that is your market, stop here.
  • A ranked complaint is not a decision. Whether the buyer pays, is reachable, needs hand-holding, or depends on one platform are separate questions, and ours are published as checks that can fail.
  • On the published run, 36 of 69 candidates were rejected. That rate is the product rather than a shortfall in it.
  • Subscription fits monitoring; a one-off fits deciding. Pick the billing that matches the job you actually have.