Skip to main content
Memo

Free tool

Don't fund a buildyou can't explain.

I'll ask you three things about what you're building. After each answer I'll tell you what's solid, what's fuzzy, and what's missing. Takes a few minutes.

Want to talk instead? Book a Revenue Strategy Call.

Why I made this

You've seen this movie. Feature ships. Nobody knows if it mattered.

The ticket looked fine in planning. A few months later, no one can say which number moved or who was supposed to own it.

So before you spend another sprint, I'll ask you:

  1. What are you building?

    Just say it plainly. Skip the pitch language.

  2. What problem does it fix?

    Who's hurting, and what makes you sure it's worth fixing now?

  3. Where does the work get stuck?

    Usually it's a missing owner, a messy handoff, or a number nobody watches.

You'll get notes after each answer, then a short wrap-up at the end.

Example

Here's the kind of feedback you'll see

This one's made up. Yours will be based on what you type.

What I heardLet customers set themselves up

You don't want new customers waiting on your setup team every time.

What's workingYou named a real process

That's better than "improve onboarding," which could mean anything.

Where it falls shortNo target yet

You said what you'll build, but not how money, cost, or speed should change.

What's missingHow bad is it today?

How long does setup take now? Where do people give up?

A clearer frameShorten time to first use

Put one person on that clock. Only build what makes it shorter.

Next moveMeasure it, own it, check it weekly

Then pick the smallest change that's worth shipping first.

How I work

I built this the same way I work with companies.

Start small on whatever's actually stuck. Attach a number to it. Only grow the thing once that number moves.

Build smallFix the stuck point. Leave the deck for later.
Track itOne number, one owner, a weekly look.
Grow laterScale after you've got proof, not before.
More on how I use AI as an operator →

If you want more

These are the frameworks I use in the feedback

Read one, or bring your summary to a call. Either works.

  • Metrics

    KPI Tree

    How a goal connects to the numbers and the people watching them.

    Read →
  • Revenue

    Shipped Revenue

    Why "we shipped it" isn't the same as revenue moving.

    Read →
  • Rhythm

    Operating cadence

    What to look at each week and each month so you don't drift.

    Read →
  • Call

    Revenue Strategy Call

    Half an hour on whatever you're stuck on right now.

    Book →

FAQ

Quick answers

If you're skimming, start here.

Still stuck?

Bring the live problem. We'll sort it in 30 minutes.

A Revenue Strategy Call is a working session, not a pitch. We'll name the gap, who owns it, and what to do next week.

Book a Revenue Strategy Call

Not ready to meet? Request a Private Revenue Memo