Website Maintenance: What It Should Actually Cover
Most maintenance retainers are a backup plugin and an invoice. Here is what the line items should be.
Website Development
The honest answer is that it depends, which is useless. So here are the ranges we quote against and what moves a project between them.
Five to eight pages, existing content, a template-derived design, standard contact form. Fine for a local service business that needs a credible presence and a phone number.
Custom design, ten to twenty-five pages, a blog architecture, service pages structured for search, forms wired into a CRM. This is where most serious business sites sit.
E-commerce with real catalogue complexity, membership or booking systems, integrations with back-office software, or a custom application with a marketing site attached.
Content is the single biggest cause of delay and cost creep. Everyone assumes copy will appear. It does not. Either budget for someone to write it or accept that the project timeline is really the content timeline.
Integrations are second. “Just connect it to our CRM” is a sentence that can mean two hours or two weeks depending on whether the systems have decent APIs and whether anyone has decided which one owns each field.
A quote far below everyone else usually means one of three things: the scope is much smaller than you think, corners are being cut somewhere you will discover in month four, or there is a subscription attached that makes it expensive over time.
None of those are automatically disqualifying. But ask which one it is, and get the answer in writing.
Most maintenance retainers are a backup plugin and an invoice. Here is what the line items should be.
Ranked by effect against effort, based on what consistently works for businesses selling in a defined area.
Redesigns lose traffic for predictable, avoidable reasons. Here is the checklist that prevents it.
Reading is one thing, implementing is another. Tell us what you are trying to set up and we will scope it.