Why every project starts with two weeks you can judge

The problem with proposals

A proposal is a promise written before anyone has touched the hard part. The hard part is where projects fail: the buyer who doesn't behave the way the deck assumed, the integration that doesn't have the connection it was supposed to have, the scene that doesn't hold its frame rate on the phones customers own. A proposal can't know this. Two weeks of real work can.

What the two weeks are for

One real piece, through the hard part, that you can judge. For a go-to-market plan: the customer, the offer, the price and the channels, written down and agreed. For a configurator: one product with every option at full speed on the cheapest phone you care about. For an assistant: your real facts, one channel, one task. For a platform: the one feature the whole thing depends on, running on your real data. Rough edges everywhere else, on purpose.

What they are not for

Not a design exercise. Not a document for its own sake. Not a demo built to impress and thrown away: what is made in the two weeks is the first stage of the work, in your name, and if you stop you keep it.

Why it is scoped first

So the decision is easy to make and easy to walk away from. The two weeks are scoped with you on the first call, with the date written down. If we miss the date you don't pay for it. After the two weeks you have something real, a plan with stages and dates, and the choice.

When we skip it

A launch page or a simple company website doesn't need it; the work is known. Everything with an unknown in it does.