// discovery

Before the call

A discovery call goes one of two ways. Either the first half gets spent pulling basic facts out of you, or it starts on the actual build.

This is how it starts on the build. Seven questions about the work, then how to reach you. Ten minutes.

Answer what you know. A blank box is an answer too, and it shows us where the fog is.

// no budget question. price follows scope. what the problem is costing you is a different question, and a useful one.

// what does your business do

A line or two, in plain words. Everything below gets read against this.

// what's slipping

The thing that made you reach out. The real version, not the tidied-up one.

// what you're running on now

Tools, systems, spreadsheets, whatever the work currently lives in. This decides what gets connected to and what gets replaced.

// what does done look like

If this works, what is different? That is the thing we build toward, and the thing we check it against before it ships.

// what's it costing you

Time, money, customers, or just the drag of doing it by hand. Now picture it gone: you wake up tomorrow and it's handled. What's different, and what's that worth? A rough sense beats a number.

// what can't change

Non-negotiables. Systems that have to stay, rules you are bound by, dates that will not move. Cheapest field to skip, most expensive to find out about mid-build.

// who has to be on the call

Anyone who has to say yes. If it takes two people, we get both on the call or we move it. A decision relayed secondhand is a decision that stalls.

// timeline

For sequencing, not pressure.

// how to reach you

So the brief has somebody attached to it.

// name

// email

// best way to reach you

// by submitting, you agree to our /privacy