Ask an agency for a quote and the first person you talk to is usually in sales, not engineering. That's not a knock on them — it's how the business is built. Their job is to match what you're describing to one of a handful of standard packages, because that's what makes a 30-person agency schedulable. The scope gets shaped to fit the offering before anyone technical has looked closely at the actual problem.
A sales team scoping a project has incentives that have nothing to do with your problem's actual size. They need the deal to be big enough to justify a kickoff call, a project manager, and a few weeks of onboarding — because those costs exist whether the job needs them or not. A two-day fix and a two-month build go through the same intake pipeline, so the two-day fix tends to get rounded up to look more like a project. That's not dishonesty; it's a business shaped around retainers and tiers having to fit everything through that shape.
When I scope something, I'm the one who's going to build it. There's no handoff between "the person who priced this" and "the person who understands what it actually takes" — that's the same conversation. If a request turns out to be smaller than it sounded, the quote reflects that, because there's no team size or package minimum to justify. If it turns out to be genuinely bigger, I can say so immediately instead of after a proposal cycle that already locked in a number.
That also means scope can move without a formal change-order process. If we're two days into a "quick fix" and it's clear the real issue is one layer deeper, we talk about it and adjust — not because a contract clause allows it, but because there's no layer of account management standing between the conversation and the decision.
None of this means every engagement stays small — some genuinely need to be big. It just means the size gets decided by what the work actually requires, not by which package it has to be sold as.