You asked the agency to move a button and tweak the onboarding copy. A week later a change order lands in your inbox with a number on it. You are annoyed, because it feels like you are being nickel-and-dimed on your own product. Sometimes you are. Often you are not. The difference is whether the change order process is a fair mechanism or a revenue tap, and you can usually tell within the first two or three of them.
Why change orders exist at all
On a fixed-price contract, the price is fixed against a scope. That scope is the whole deal. The agency bid a number assuming a specific set of features, and the moment you ask for something outside that set, the economics they signed up for break. A change order is how they reprice the delta. That is legitimate. If change orders did not exist, agencies would either pad every fixed bid by 40 percent to absorb surprises, or they would eat scope creep until they cut corners somewhere you cannot see.
The catch is that changes on a fixed-price contract are expensive by design, often billed at three to five times the agency's normal blended rate. That premium is not pure greed. Re-planning, re-testing, and re-sequencing work mid-build genuinely costs more than doing it in the original plan. But that same premium is exactly what a less scrupulous shop leans on when it bids low to win the job and then makes its margin back on a river of change orders. Fixed-price MVPs routinely balloon 40 percent past the original quote through changes alone, and a chunk of that is avoidable.
How to tell a fair process from a revenue tap
A healthy change order process has four traits. First, it is written into the contract before you sign, with a defined rate and an approval step, not invented on the fly. Second, every change order is itemized: what changed, how many hours, at what rate, and why. Third, small clarifications that were obviously implied by the original scope do not trigger a charge. Fourth, you approve in writing before the work happens, so nothing is billed as a surprise.
A revenue tap looks different. Vague change orders with a lump-sum number and no hours behind it. Charges for things any reasonable reading of the scope already covered. A pattern where the low bid that won the job is now 30 percent underwater and every conversation ends in a new order. If you signed a suspiciously cheap fixed bid, this is often the back half of the fixed-bid trap arriving on schedule. The bid was never the price. The bid plus the change orders was always the price.
The tell is the ratio. A few change orders on a months-long build is normal life. A change order every week, each one itemized thinly, is a business model. Read the SOW red flags before you sign and you can spot the vague-scope setup that makes this possible in the first place.
How to keep change orders under control
Most change-order pain is scope pain wearing a different hat. The fixes are upstream of the invoice.
- Write a scope specific enough to argue with. If the SOW says "user management," every reasonable feature request will look like a change. If it lists the actual screens and states, most requests are obviously in or obviously out.
- Batch your changes. Ten one-line requests over ten days each carry re-planning overhead. One consolidated change list carries it once. You will pay less for the same changes simply by not interrupting the build ten times.
- Keep a running decision log. When you and the agency agree something is in scope, write it down. Half of all change-order disputes are really disagreements about what was said in a call three weeks ago.
- Ask for the hours, not just the price. A fair agency will show you the estimate behind the number. One that refuses is telling you the number is not really tied to work.
When you get a change order, do the same thing you would do with any agency bill: line-item it and sanity-check it. If you are not sure what fair looks like, learning to read an agency invoice critically carries straight over to reading a change order.
When the change order is actually your fault
Be honest with yourself, too. If you keep changing your mind about core flows, the change orders are the market pricing your indecision. That is not the agency being unfair. It is the cost of designing the product live, on a fixed-price contract that assumed you had already designed it. If you are still discovering what you want, a fixed-price build may be the wrong structure entirely, and a time-and-materials or retainer arrangement would stop turning every decision into a negotiation. The change order is a signal. Sometimes it points at the vendor. Sometimes it points at the plan.
FAQ
Are change order fees normal?
Yes. On fixed-price work they are the standard way to handle anything outside the agreed scope. What is not normal is charging for work already covered by the scope, or using change orders as the main way the agency makes its margin.
Why are change orders so much more expensive than the original rate?
Mid-build changes carry re-planning, re-testing, and disruption costs the original bid did not include, so a two-to-five-times premium is common. Beyond that, some shops price changes high on purpose because they bid the base low to win the job.
Can I refuse a change order?
Yes. A change order is a proposal, not a bill, and it should require your written approval before work starts. If you are being charged for changes you never approved, that is a contract problem worth raising immediately.
How do I stop the change orders from piling up?
Tighten the scope before signing, batch your requests, keep a written decision log, and always ask for the hours behind each number. If the volume still feels wrong, it may be time to book a call and get an outside read on whether the process is fair or a pattern.