Partners Running an agency? Partner with us
The Graylemon Journal Build logs, teardowns and method, by email. Subscribe All resources
Follow the studio LinkedIn Instagram
Partner with usBook a call (opens in a new tab)
Service 01 · Not sure it's worth building

Venture Diagnosis

Find out whether it's worth building, for whom, and the smallest version that proves it, before you pay for the build. You get a written verdict: build, test first, or stop.

Photo · 21:9
A Venture Diagnosis working sessionComing soon
Your situation

You're about to spend real money on a guess.

You have an idea, a prototype or a product that has stalled. The numbers are flat and you can't tell whether the problem is the product, the positioning or the market.

Building got cheap. Knowing what to build didn't. Most products fail because nobody decided what they were for, and a Venture Diagnosis is where that decision gets made, on evidence.

What you get

A verdict you can act on, in writing.

The Venture Diagnosis, in writing6 deliverables
  1. A current-state map

    What exists, what's been tried, and what was learned.

  2. A Stuck-to-Scale stage diagnosis

    Which stage you're actually at, not the one you think you're at, with the evidence behind it.

  3. An assumption inventory

    The assumptions the venture rests on, and the three that sink it if they're wrong.

  4. A scope recommendation

    Build first, later, cut, don't build.

  5. A clear verdict

    Build, test first, or stop, with the reasoning.

  6. A fixed-scope quote

    For the build, if the verdict is build.

Image · 16:10
Sample Venture Diagnosis outputSample · coming soon
How it runs

Map, diagnose, decide.

  1. Map

    What exists

    • The product, prototype or idea as it stands
    • What's been tried, and what it taught you
    GateWe agree on the current state before judging it.
  2. Diagnose

    Where it's stuck

    • The Stuck-to-Scale stage, with its evidence
    • The assumptions that kill it if they're wrong
    GateEvery conclusion names the evidence behind it.
  3. Decide

    What happens next

    • Build first, later, cut, don't build
    • The verdict, and a fixed quote if it's build
    GateA verdict you can act on, in writing.
How it's priced

Fixed fee, credited against the build.

Fixed fee, set after scoping, in writing before work starts. If you go ahead with the build, the Venture Diagnosis fee is credited against it.

The free first step is a call, to check the fit before anyone spends anything.

What we need from you

Access, and someone who can decide.

  • Access to what exists

    The product or prototype, any data, and what you've already tried.

  • A decision-maker in the working sessions

    We force decisions in the room, not in a follow-up email.

  • Honesty about what hasn't worked

    That's usually where the answer is.

What this is not

Not a sales pitch for a build.

  • Not this: A sales pitch for a build.

    Instead: A written verdict: build, test first, or stop, with the reasoning.

  • Not this: A guaranteed yes.

    Instead: Sometimes the answer is "don't build it." That answer is part of what you're paying for.

A diagnosis that stops a bad build is worth more than a build that ships.

Questions

Before you start

All questions

How do I know if I'm ready?

You have a real problem or a working prototype, a budget set aside for it, and you can make decisions in days. If you're not sure the idea is worth building, that's exactly what a Venture Diagnosis is for, and the honest answer is sometimes "not yet."

How much does it cost?

Every engagement is a fixed fee, set after scoping, and you'll have the full number in writing before anything starts. If you go ahead with the build, the Venture Diagnosis fee is credited against it.

What if the idea is wrong?

Sometimes the honest outcome is that the thing shouldn't be built. We'll say so, with reasoning, and you keep everything that got us there.

We have a partial build, or a prototype made with AI tools. Does that change anything?

Usually it helps. We assess what exists before committing to extend it. Sometimes the right call is to build on it; sometimes the architecture blocks where you're trying to go, and restarting is cheaper. We'll tell you which, with the reasoning, and you decide.

Start a diagnosis

Tell us what you're trying to decide.

Three short steps. We reply the same business day with what happens next.

About you

The decision

Where is it now?
A few sentences is plenty. What you share stays private: we never publish or share it.

Budget, then send

Have you set aside budget for this?

What you share stays private: we never publish or share it. Privacy policy

We reply the same business day.

From the Journal

Is it worth building? How to decide before you pay for the build

Read the article
Next in the sequence

When the verdict is build: AI Product Build

AI Product Build

From the Lab: Cut It and Spot the Stall run the same judgement on a brief and on a stalled venture's numbers.

Search Graylemon

↑↓ Move↵ OpenEsc Close