Once a project is done, new wishes come in: a special template, an extra landing page, new logic for an app. They seem small, because the store is already live and paid for. Even so, we bill every new piece of custom development as a separate job. That's not padding, it makes visible what's involved.
The situation
“It's just a small change” is the most common sentence after a launch. Sometimes it's true. But often, one sentence in a chat hides analysis, code, testing on every device and checking that nothing else breaks. And it isn't a fix to what was agreed, it's something new.
What goes into a “small change”
- Understanding: What exactly should happen, and in which cases should it not?
- Building: Writing code that fits the existing theme.
- Testing: Desktop, mobile, different browsers, all affected pages.
- Cross-checking: Does everything else still work? Especially with theme customizations, a change in one place can shift something elsewhere.
How we handle it
- We fix bugs, no discussion. If something doesn't work as agreed, that's on us.
- Anything new gets a short offer. With a description, fixed price and timeframe. You decide whether and when.
- Billing happens after delivery. Like any other job.
That way, the original fixed price stays fixed, and extra wishes are still possible at any time.
What you can take away
- Tell bugs and wishes apart. Both are legitimate, but only one is included in the fixed price.
- “Small” isn't an effort estimate. Better to get a quick price than a surprise afterward.
- A clear scope protects both sides. You only pay for what you order. The agency delivers what was agreed.
- Bundle your wishes. Several small changes at once are often cheaper than each one on its own.
Got an idea for your finished store? Describe it to us and you'll get a fixed price before anything happens.