Why the quotes are hard to compare
Support offers read alike: monitoring, fixes, updates. Yet two quotes can sit far apart. The difference is rarely greed. The same label covers different promises.
One vendor promises the site will stay up and that someone notices if it does not. Another promises every item in your queue is done within a week. A third promises the site will keep growing: new sections, speed work, integrations. Those are three services. The first sells attention; the other two sell hours of people's time.
What actually sets the price
Strip away the sales language and four things decide it.
Volume of work. How many changes you expect each month. A site touched once a quarter and a site with weekly campaigns need very different amounts of time.
Response time. "Within a day" and "within a week" cost different amounts, because the first needs someone free that particular day. A good contract also separates an urgent breakage from a planned task.
The state of the site on day one. A site with no documentation, scattered access and updates everyone is afraid to install costs more in the first months. The vendor clears the debt before anything can grow.
Platform and code. Someone else's custom code takes longer to understand than a familiar platform. That is why an honest vendor starts with an audit rather than a price list.
The usual formats
There are three, each with its own logic.
A monthly block of hours. A fixed volume you point at whatever you need: fixes, sections, speed. It suits a steady flow of tasks. Ours run from $1,500 a month for 30 hours to $3,700 for 90 hours; the full table is on the website support page.
A one-off task by estimate. A migration, a speed-up, a series of changes: one batch of work priced before it starts. Ours begin from $250. It fits an irregular flow.
Hourly. When the volume is unpredictable, work is billed as used, with a weekly report. Ours is from $45 an hour. Flexible, but you cannot know the month's bill in advance.
Prepaying three months earns a 5% discount with us, six months 7.5%.
What is in, what is out
Ask directly and get the answer in writing. Support usually covers uptime and error monitoring, backups, updates and spam protection on forms. Then a queue of changes to copy, banners and pages. Separately: new sections and integrations, and page speed.
What most often lands outside the scope: new functionality ("that is a project now"), design of new blocks, coordination with your other vendors, urgent work outside business hours. None of it is wrong. What hurts is finding out at the moment you need it.
Questions to ask before signing
- What counts as a breakage and what counts as a change request, and how fast do you respond to each?
- What happens to unused hours: do they expire, roll over, and by how much?
- Who holds the access and where is it stored? If the credentials live only with the vendor, that is dependence, not support.
- What does the report look like? Can you see where the hours went?
- What happens if we leave: how long does handover take, and do we receive code, documentation and backups?
- Do we need support at all? A good vendor will say "not yet" if your site does not change.
When you should not buy it
Plainly: if the site is touched twice a year, a monthly block is bad value for you. A one-off fix by estimate is cheaper and more honest. We say the same on our own page: a retainer at that volume is paying for availability you do not use.
The opposite also holds. If you run campaigns every month, add pages and connect services, one-off orders cost more in the end, because each one means finding someone, getting an estimate and waiting. For how the first months after launch look in a store, see our ecommerce cost breakdown; for what happens in the first weeks of a new site, what moves a website timeline.
If the site needs more design than code, look at design support and the retainer explainer. The hours are shared: they can go to either.

