Cilantrobyte.

Consultation · 1–2 weeks

Idea Verification

A short, disciplined sprint to find the weakest part of your idea before the budget commits to defending it.

Duration

1–2 weeks

Engagement

Idea Verification

Starts with

A written brief

Status

Taking bookings

(01) Our take

Most early-stage products don’t die from bad execution. They die from a sound idea in adjacent territory — close enough to feel right, far enough from the real demand that no amount of polish will bridge the gap. Idea Verification is the engagement we built for the moment before that commitment, when the pitch still feels sharp but nobody’s actually tried to break it yet.

We start with the artefacts you already have — the deck, the doc, the napkin sketch, the half-built Figma file — and we write down the bets each one is making. Then we go looking for evidence. We talk to five to ten people who look like your target user, we map competitors and adjacencies honestly, and we run a quiet teardown of the business model to see which parts rely on assumptions nobody’s tested.

We won’t run a focus group and we won’t hand you a 60-slide deck. What you get back is a written point of view: here are the three assumptions your idea rests on, here’s what we learned about each, here’s what we’d change, and here’s the shape of the next engagement if you want to keep going. If the evidence pushes the other way — we’ll tell you that too, and we’ll argue with you about why.

The engagement is deliberately short. One to two weeks keeps the team’s attention on yours, keeps the cost bounded, and keeps us honest: if we can’t form a defensible opinion in ten days, the problem isn’t your idea, it’s the scope of what you’re trying to verify — and we’ll say so plainly.

(02) Is this for you

When to pick this

  • You’re about to commit budget or headcount to a build and you want a second set of eyes before you sign.
  • You’ve got founder conviction but no external signal yet, and you want it tested by people who aren’t on your cap table.
  • You’re choosing between two directions and want the trade-offs written down honestly.
  • You need something to show a board or investor that isn’t a pitch — a written recommendation carries differently.

When not to pick this

  • You already know the idea works and you need to start building. Go build.
  • You want validation, not verification. We won’t tell you what you want to hear, and paying us to do so is a waste of money.
  • The question is “how do we ship it” rather than “should we ship it.” That’s Project Management or a build engagement, not this.

(03) Process

Week by week

  1. Week 1

    Kick-off, assumption map, 5–10 user conversations, competitor teardown.

  2. Week 2

    Synthesis, optional clickable prototype, written recommendation delivered.

(04) What you get

Deliverables

The headline artefact

A written recommendation — 10–20 pages — with a phased proposal for what comes next.

Alongside it

  • User & competitor research
  • Risk and assumption map
  • Written recommendation
  • Optional clickable prototype

Book a Idea Verification engagement.