Short answer
Most small changes take hours to build and weeks to arrange: a quote, an approval, then a wait for a slot in the agency’s schedule. A flat monthly fee removes the quoting, so changes go straight into a queue you control and most ship within a few working days.
Where the three weeks go
Ask your supplier for the history of a recent small change and lay it out. It usually looks something like this:
| Step | Typical wait |
|---|---|
| Request sent and acknowledged | A day or two |
| Scoped and quoted | Several days |
| Quote approved on your side | Several days, longer if it needs a purchase order |
| Scheduled into the agency’s diary | A week or more |
| Built | Often a few hours |
| Tested by you, fixed, released | A few days |
The build is the shortest step. Almost all of the delay is paperwork and waiting.
Why the quote model is slow by design
When every change is priced separately, every change is a small sale. The agency has to estimate it carefully to protect its margin, you have to approve it to protect your budget, and then it has to fit between the bigger projects that pay the agency’s bills. Nobody is being difficult. The model simply makes small work expensive to arrange.
When the deadline isn’t yours
Platforms that run a business answer to dates set by someone else: a funding rule change, a new inspection framework, the opening day of the season, a customer’s go-live. If changes take three weeks to start, a two-week deadline is already lost. What you need is a queue you can reorder the day the rules change, with the deadline item at the top and work starting straight away.
Testing shouldn’t be your second job
If you’re the product owner, the tester and the help desk, you’ll know the cost of work that comes back half right. Each round of fixes adds days. Work that has already had a senior review before it reaches you turns your testing into genuine sign-off. How to keep reviews moving.
What to ask your current supplier
- What’s the average time from a request to it being live?
- Can we reorder the work ourselves, without a new quote?
- Who reviews the work before it reaches us?
- Who owns the code and the hosting accounts?
- What happens to the code and the accounts if we move supplier?
The flat-fee alternative
On a subscription there are no quotes. You add a change to the queue, put it in the order you want, and it gets worked on. Most tasks ship within a few working days, a senior developer reviews every release, and everything we build lives in your repositories and belongs to you. For the board, it’s one known monthly cost on a 12-month term rather than a headcount request. How we work with platform owners.
Questions
Can you take over a platform another agency built?
Yes. Most of our subscription clients already have software running when they come to us. We review the codebase first so we understand it before we change anything.
Who owns the code?
You do. Everything we build lives in your repositories and belongs to you.
What if a rule change means we need something urgently?
You move it to the top of the queue the day it changes. If something is broken in production, it jumps the queue on every plan.