Step 1 of 5

What are you
building?

Two quick questions: the kind of product, and whether there's already something running today.

Type of projectPick the closest fit — we'll go deeper in the brief.

Is there something already?This changes the approach far more than the technology does.

Step 2 of 5

Who uses it,
and what must it do?

This is the part that actually shapes the build — and the architecture we propose on the right.

Who is it for?

How many people will use it?Roughly, around launch — not a five-year projection.

What does it need to do?Choose everything that applies. Not sure about one? Leave it — we'll cover it on the call.

Step 3 of 5

An honest range here saves everyone a round of guessing. Nothing is binding.

When should it be live?

Working to a fixed date? (optional)

An event, a season, a compliance deadline — anything the launch has to land before.

Budget range

Step 4 of 5

In your own words. No need for a specification — we'll write that together.

What do you call it? (optional)

What problem should it solve? *

30 more characters to go

Anything we can look at? (optional)

Anything already decided? (optional)

If you have no view on the technology, that's the normal answer — our proposal is on the right.

Step 5 of 5

We reply within one working day, usually with a couple of questions and a rough shape.