About

DeliverySheet is built and supported by one person: Tan Gravam, in Amsterdam. When you email [email protected], the person who wrote the code answers.

Why it exists

The product comes out of close to two decades inside large delivery organisations, watching the same failure repeat at every size: teams commit to work before anyone has established that it is understood, owned, sized and unblocked. The missed date arrives months later, but the miss was decided at the commitment — in a meeting, a deck and a Slack thread that kept no record.

DeliverySheet holds that one layer: from a vague request to a clear delivery decision, with the evidence on the table and the promise recorded. The essays and the glossary are the thinking behind it, written while building it.

How it's run

Deliberately small: one builder, no growth team, opinionated scope. The product says no to time tracking, per-person velocity and configurable process on purpose — the reasoning is in the comparisons and in Allocation, not consumption. Pricing is one number on the pricing page, and the trial requires a card because honest constraints beat growth theatre.