Why we ship in 14 days, not 90

I have run the 90-day project. As a founder buying it and as a founder selling it. The 90-day project has a secret, and the secret is that it is not 90 days of work. It is maybe 30 days of work wearing a 90-day coat.

The other 60 days are status meetings, scope drift, a two-week stretch where nobody is quite sure who owns the next decision, a re-plan after the first demo, and the slow realization that the thing being built stopped matching the thing that was needed somewhere around week six.

The deadline is a design tool

When you tell a team they have 90 days, they design for 90 days. The architecture gets ambitious. The abstractions get speculative. Someone builds a plugin system for a thing that will never have a second plugin.

When you tell a team they have 14 days, they design for 14 days. They build the feature, not the framework around the feature. They use the boring database table instead of the clever one. A short deadline is not pressure. It is a constraint that makes most of the bad decisions impossible.

Fourteen days is long enough to ship something real and short enough to make speculative architecture physically impossible.

Fourteen days fits in a founder’s head

You can hold a 14-day project in your head. You know what is being built, you saw the spec, you watched the commits. A 90-day project you cannot hold. You delegate it, and the moment you delegate it you lose the ability to catch the drift early, which is the only time catching drift is cheap.

So we do not sell 90 days. If your work is genuinely three months, we sell it as a sequence of sprints or an embedded engagement, each one small enough that you never lose the thread.

What 14 days forces us to be good at

A short window punishes vagueness. It forces us to write a real spec on day 1, scope hard, and refuse work that does not fit. That refusal is a feature. Every sprint we decline is a sprint we would have shipped late.

Ninety days hides all of that. You can be sloppy for sixty days and still feel productive. We would rather not have the option.