Skip to content

How it works

You built it.
We work out what to do about it.

No questionnaire, no strategy workshop, no thirty-day plan. You give us a URL. We read your product properly, tell you what we think you’ve built, and then tell you the single most useful thing you could do next, and why.

01

We read your product

Paste a URL. We read the pages a good marketer would read. The homepage, the pricing, the docs, the changelog, and work out the problem you solve before anything else.

Problem first, deliberately. To find people who want your product we have to find people with the problem, and those are not the same search. Nobody types “golf society management software”. Plenty of people complain about running one from a spreadsheet.

Where we can’t find something, we say so rather than inventing it. Then you correct us, and your correction becomes the version we work from.

Here’s what I think you’ve built

Example
You solve
Golf society organisers losing entire evenings to registrations, handicaps and results spread across a spreadsheet and a WhatsApp group
By selling
A phone-first app that handles sign-ups, pairings and a live leaderboard for a society day
For
The one volunteer who ends up organising everything for a 40–120 member society
At
£4 per member per year, billed to the society
Instead of
A shared spreadsheet, a WhatsApp group, and one person doing the maths by hand on a Sunday night

Did I get that right?

Yes, that's itClose, let me fix somethingWay off

Corrections don’t overwrite what we guessed. They create a new version, so we can tell later what we got wrong and learn from it.

02

We work out what’s in the way

Most founders who think they have a traffic problem have a clarity problem, a conversion problem or a retention problem. Those have an order, and doing the fourth thing while the first is broken is wasted work.

So before we recommend anything, we decide which one you’ve actually got. That’s what makes it possible to say “don’t buy ads yet” and mean it.

The order things have to be true in

  1. 1Can anyone tell what it is?Clarity
  2. 2Can they become a customer?Conversion path
  3. 3Is anyone arriving?Traffic
  4. 4Do the arrivals do anything?Conversion rate
  5. 5Do they come back?Retention

The first “no” is your bottleneck. Everything below it is a distraction until it’s a yes.

03

We tell you one thing

Not a list. Not a plan. The single thing most worth doing, specific enough that you can start it now, with the reasoning and the evidence attached.

Six kinds of answer: fix something, go and do something, talk to people, stop doing something, wait, or double down on what’s already working. “Produce more content” is not automatically the answer, and often it’s the opposite of it.

Do this nextExample

Ask r/golf how societies actually handle scoring

Your buyers organise society days and the subreddit allows questions. Ask one rather than pitching: you want their words for the problem, and a question gets answers where a launch post gets removed.

The post, written for youYou post it. Nothing goes out in your name from here.

“How does everyone handle scoring for society days? Ours is a spreadsheet and a group chat and it falls apart by the ninth. Curious what actually works.”

Why we’re telling you this

  • Seen on your site: Your homepage names society organisers, and that is who is in there. The audience matches without you having to guess.
  • From your own results: You told us you launched on Product Hunt and posted twice on Reddit, with no reported outcome from either.
  • Why this rule exists: A question gets answers. A pitch gets removed, and a removal costs you the community for months.
  • You told us: You told us you have 30 minutes today. This takes fifteen of them.
What else did you consider?
  • Email three society organisersWorth doing, and harder: you would be guessing at the wording. Do this first and use what they say.
  • Post yesterday's product update on XYour last six posts there produced no measurable signups. Not today.
15 min of your dayPotential: High

Under the simple bit

What’s actually happening

You see three steps. This is the machinery behind them, and the reason you shouldn’t have to think about any of it.

  1. Understand

    We read your product like a marketer would, and tell you what we think it is. You correct us where we're wrong.

  2. Decide

    We work out what's actually blocking you, and pick the one thing worth your next twenty minutes. Sometimes that thing is “stop”.

  3. Act

    You do it. We draft the fiddly parts. The reply, the headline, the intro email. You're the one who posts.

  4. Measure

    We watch what it produced. Visits, signups, customers, or nothing, which is also worth knowing.

  5. Learn

    Results change our mind. A channel that produces nothing gets dropped, whatever the internet says about it.

  6. Do this next

    Then we do it again, knowing more than we did yesterday.

Where you do the work

One screen. One decision.

No feed to triage, no badge counts, no streak to break. If there’s nothing worth interrupting you for, it says so and you get on with your day.

Do This Next
Example

Good morning, Simon

Here’s the one thing worth doing.

Top priority

Ask r/golf how societies handle scoring

Your buyers are in there and the rules allow it. Ask the question rather than pitching. You want their words for the problem.

Your post, written for you

“How does everyone handle scoring for society days? Ours is a spreadsheet and a group chat and it falls apart by the ninth. Curious what actually works.”

Potential: HighTime: 15 min
Copy the postDone

Why this?

  • Your homepage names society organisers; that’s who is in there.
  • You’ve had no reported result from a launch post.
  • You said you had 30 minutes today. This takes fifteen.

What else did you consider?

Your product is live.
Let’s find
the next move.

Get a focused recommendation based on where your product is now, not a generic list of everything you could be doing.

worst case, you find out what you’re actually selling

Free diagnosis · No card required

Built by Simon.

Because I kept building products and then wondering how on earth to get anyone to use them.