The screen budget is real.

Cost & Funding · 5 min read

Every design package comes with a number. That number is screens. And it's the single most important constraint in the entire project.

Most clients don't think about screens until they run out of them. They think about features, ideas, user journeys. All important. But every one of those things eventually has to live on a screen. And screens cost money to design, annotate, and build.

When a client has thirty screens in their budget and fifty features on their list, something has to give. And that conversation, the one where you decide what stays and what waits, is where the real product gets defined.

Not all features cost the same number of screens

A simple list view takes one screen. A settings page with a few toggles takes one screen. But a multi-step onboarding flow might take four or five. A creative tool with different modes and states could take six or seven. The complexity of the feature determines how many screens it consumes.

This is something clients often don't realise until we start mapping it out. A feature that sounds simple in conversation can be expensive in screens. And a feature that sounds complex can sometimes be surprisingly lean. You don't know until you break it down.

That's why the screen count isn't just a design metric. It's a cost metric. More screens mean more design hours, more development hours, and a longer timeline. The screen budget is directly tied to the project budget.

Constraints force better products

I know constraints sound limiting. But they're actually the thing that makes a product good. When you can't build everything, you have to choose the things that matter most. That forces prioritisation. And prioritisation is where clarity comes from.

McKinsey and Oxford found that large IT projects run 45% over budget on average, with scope management as the primary driver. The projects that blow out are the ones where nobody said "that's enough for version one." The screen budget is the mechanism that prevents that.

I've watched clients make their best decisions under screen pressure. When the budget forces a choice between two features, the one that survives is almost always the right one. The constraint doesn't limit the product. It sharpens it.

The screen count protects you

Without a screen limit, scope creep happens by default. Every meeting adds a feature. Every feature adds screens. Every screen adds cost. Before long, the project is twice the size and twice the price, and nobody made a conscious decision for that to happen.

The screen budget is the guardrail. It makes the cost of every feature visible. When a client says "can we add a dashboard?" I can tell them exactly how many screens that dashboard will cost and what it means for the remaining budget. That transparency is what keeps projects on track.

So when you look at your screen count and feel like it's not enough, remember this. That number isn't holding you back. It's the thing that's going to keep your project from spiralling into something you can't afford to finish.

Sources
Delivering Large-Scale IT Projects On Time (McKinsey & Oxford, 2012) - Large IT projects run 45% over budget and 7% over time, with scope management as the primary driver.

Related blog posts:

Scope creep starts with "while we're at it" →

Fewer screens forced better thinking →

The difference between a feature and a solution →