Every studio has heard some version of: "can you just move this button over" or "can we just make the header a bit bigger." It sounds small because it's described in five words. The actual work behind those five words is rarely five minutes, and the gap between how a request sounds and what it touches is where most project budgets quietly bleed out.
Why "just move this" is never just one thing
A button isn't an isolated element. It's part of a spacing system, a responsive layout that has to hold up across five breakpoints, an interaction state that changes on hover and focus, and often a pattern repeated on a dozen other pages. Move it on one screen and you've either created an inconsistency or you've signed up to update every other instance of that pattern across the site.
Where the hidden cost actually hides
- Design system ripple: one component tweak often needs to be reflected everywhere that component appears, not just the page someone was looking at
- Copy and translation: text length changes shift layout in ways a single language preview won't catch, especially across multiple locales
- Responsive breakpoints: a change that looks fine on desktop can break tablet or mobile spacing in ways nobody tests until launch
- QA regression: any visual change needs to be re-checked across browsers and devices, not just eyeballed once on the screen it was requested on
- Deployment overhead: even a tiny change still goes through a build, a review, and a release, the same pipeline as a much bigger feature
How we scope revisions now
- Revision rounds are defined upfront in the proposal, so both sides know how many passes are included before anything is billed extra
- Every request gets bucketed as either cosmetic (contained to one element) or structural (touches the system), before any work starts
- We send a short written summary of what a request will actually touch before starting it, so "quick" surprises get caught in a sentence instead of an invoice
What this means for clients
None of this is about saying no to small requests. It's about being honest, before the work starts, about what "small" actually means in a connected design system. Clients who know the real shape of a request make better calls about which changes are worth making now and which can wait for the next batch. That honesty is what keeps a project's scope, and its budget, where everyone agreed it would be.