Skip to main content

Our Method

Find the door before we forge a key

A smaller product still leaves the lock. Keyteller names the door, names the lock, then forges one key system, or waits. Three questions first: what is true, what is better, and what to build first.

We still call this path MVP Factory. In Keyteller language it is how Discovery finds the door and chooses the first key.

The problem

Find the door. Forge one key.

MVP usually means shrinking the product you already decided to ship. That leaves the lock in place. The failure is not shipping too little. It is forging keys in front of a door you have not named.

Nothing gets forged until three questions have an answer a founder can argue with. What is true names the door. What is better names keys that already exist. What to build first chooses the first key system. The master key is the decision system that remains: constraint, evidence, ownership, and next move. Discovery is the engagement that holds this standard.

Read the four-part guide

The questions

Three questions before any build

01

What is true

Which door is actually locked in the live venture, not in the pitch? Until the lock is named, more product is activity, not progress.

02

What is better

Is there already a key? A vendor, a manual path, a narrower offer, or no work. Name it before the team forges a weaker one.

03

What to build first

Which key system opens that lock now? Forge only that first key, with a metric that matches the live direction, or park the rest honestly.

The path

Door in, first key out.

  1. Live direction

    Start from the venture as it actually operates, not the deck's version of it.

  2. Find the door

    Name the constraint worth opening. You can argue with it. You cannot skip it.

  3. Name the lock

    Write down why it still will not open, and which stronger keys already exist.

  4. Forge one key

    Authorize one key system. Everything else stays parked until the evidence changes.

Example

The clinic app that waited.

Synthetic case

Stated goal: a patient-facing mobile app for a clinic operator. After the three questions, the lock was the record write path plus the clinician task queue. That was the first key. The app was deferred.

Downloads are not completed clinical workflows on trustworthy data. The case is labeled synthetic so it teaches the sequence without pretending to be a client win.

Inspect

The tools are not the offer.

The same questions run as public tools if you want to see how the studio operates them. GitHub is for inspection. Discovery is the engagement.

  • Opportuner runs the first two questions. MIT on GitHub.
  • MapCmd ranks what to build first. MIT on GitHub.
  • CtrlC optional section packs for the first key. MIT on GitHub.

Bring a live direction. Then book the call.

You leave with the door named, the lock argued, the first key chosen or parked, and a master key the team can keep using. Discovery is how we run that.

Book a call