Can we use the result with a different builder?

Yes. A document that only works with us is a snare.

How many of our people does it need?

Three to five, an hour or two each. If it needs more, you hear it at the start.

What if it turns out the thing is not worth doing?

That is a result too, and the cheapest way to reach it. We have said it before.

The people you spoke to. Whoever made the promise is whoever sits down to the work.

The way in

You do not yet know what to order.

One to two weeks at a fixed price, at the end of which you hold a scope, a prototype, a plan and a quote. They can be taken to another builder, and that is not a figure of speech.

The problem

Three sentences we hear constantly.

“We got three quotes and all three differ.” Each one guessed a different scope. You are comparing guesswork.
“I cannot know the cost before we start.” Nobody can. Somebody has to order the question first, and that work is paid for on its own. It is the whole of this sprint.
“If we get this wrong now, we pay for two years.” You will. Which is why this step exists before the large one rather than in its place.

What you receive

Four things, each with a name.

A scope. What is in, what is out and where the line runs, written so that somebody who is not technical can follow it.
A prototype. Clickable, not a picture. It goes in front of a user and shows where it stops being obvious.
A plan. The order of the work, the dependencies and where the risk sits, with an honest word about what can slip and what cannot.
A quote. A price against that scope, with the shape of the engagement and what happens if the scope changes.

All of it is yours on the day you receive it. If you decide to build with somebody else, or not to build at all, you take it wherever you like. We ask for nothing further.

The order

How the sprint goes.

The sprint runs on the method the consulting page sets out. This is its shortest form: one phase, a fixed price, and an ending with a document in your hand. The order below is drawn for two weeks, and a one-week sprint keeps it, compressed.

Day oneWe sit with the people who will use the thing and the people who pay for it. What has to be true for it to be worth doing gets written down while everyone is still in the room to argue with it.

Week oneThe scope is ordered and the prototype is assembled. You see it before it is finished and tell us where we have it wrong.

Week twoThe plan and the quote are written against the ordered scope. We hand them over and walk through them sentence by sentence.

The price

Fixed, and said before we begin.

The sprint is a fixed price for a fixed length. What that price is depends on the scope of the task and on how many people we need to hear. The band comes in writing when you ask, after half an hour of conversation.

If you go on to the first-version package, the sprint comes off its price. If you do not, nothing further is owed and the result is still yours.

The questions

What people ask before they book it.

Can we use the result with a different builder? Yes. A document that only works with us is a snare.
How many of our people does it need? Three to five, an hour or two each. If it needs more, you hear it at the start.
What if it turns out the thing is not worth doing? That is a result too, and the cheapest way to reach it. We have said it before.
Who does the work? The people you spoke to. Whoever made the promise is whoever sits down to the work.

The beginning

Start by ordering the question.

Write to us

A few sentences about the thing itself and about who has to use it. A person answers.