Day one: the problem arrives
A logistics company submits a problem: their dispatch team keeps assigning the wrong vehicles to deliveries. It's costing them fuel, overtime, and customer patience. They expect a quote "in a few weeks, probably."
Day two: the conversation
We read the submission carefully, then ask four questions that change the scope: which data does the dispatch system trust? What happens when a vehicle is reassigned mid-route? Is the constraint solver allowed to reorder deliveries? Can we see a month of real history?
The answers come back the same day. The problem is smaller than it looked — and cheaper than they feared.
Day three: the proposal
A fixed price, a clear scope, and a delivery date. No hourly meter, no "discovery phase" upsell. The proposal explains what will be built, what won't, and what we'll do if the data surprises us.
Most studios sell time. We sell a result, priced in advance.
Why this works
- The client knows the cost before we start — no invoices that grow
- We invest in the questions — scope is where projects live or die
- Forty-eight hours is a promise — it forces us to read, not skim
By the end of the week, work begins. Most clients tell us the proposal alone was worth the submission.
