A useful website budget starts with the required outcome: what visitors need to do, who will publish content, and what the business must maintain. There is no single verified market price for a “small business website.” Location, scope, content, integrations and support change the quote.
Compare static and dynamic approaches against the same requirements, then compare their full cost over a defined period. The figures below are hypothetical planning inputs, not market averages, vendor prices or client results.
The Three Cost Profiles
DIY builder: You pay for a platform and supply some design, content and administration work yourself. Managed infrastructure can reduce tasks you need to perform, but subscriptions, feature tiers and export limitations matter.
Professionally built static site: You pay for design and implementation, then delivery, editing and integrations. A CMS can provide non-technical editing. Build dependencies and third-party services still need maintenance.
CMS or dynamic application: You pay for the implementation and operation of the runtime application and data. A simple managed CMS and a custom transactional application are different scopes and should not share a single cost range.
Hosting price alone does not establish reliability or security. A low-cost plan is not evidence of an inevitable incident, and expensive hosting does not guarantee a good result.
A Reproducible Three-Year Comparison
Assume three proposals for an informational website have already been checked against the same required pages, editing workflow and contact integration. These invented numbers demonstrate the method only. Currency is EUR, excluding VAT. Recurring prices are assumed constant for 36 months, with no introductory discounts, inflation or currency movement.
| Assumed input | DIY builder | Static professional | Managed CMS |
|---|---|---|---|
| Initial external payment | €200 | €2,500 | €4,000 |
| Platform/hosting per month | €25 | €5 | €25 |
| Domain renewal per year | €15 | €15 | €15 |
| External maintenance per year | €0 | €400 | €1,200 |
| Owner time initially | 40 hours | 4 hours | 6 hours |
| Owner time per year | 10 hours | 2 hours | 4 hours |
| Assumed value of owner time | €50/hour | €50/hour | €50/hour |
3-year external cash = initial payment + 36 × monthly charge
+ 3 × (annual domain + annual maintenance)
Owner time value = (initial hours + 3 × annual hours) × hourly value
Combined planning cost = external cash + owner time value
DIY cash = 200 + 36×25 + 3×(15+0) = €1,145
Static cash = 2500 + 36×5 + 3×(15+400) = €3,925
CMS cash = 4000 + 36×25 + 3×(15+1200) = €8,545
DIY owner time = (40 + 3×10) × 50 = €3,500
Static owner time = (4 + 3×2) × 50 = €500
CMS owner time = (6 + 3×4) × 50 = €900
Combined: DIY €4,645; static €4,425; CMS €9,445
Owner time is an allocation, not an additional supplier invoice. Its value is not automatically lost revenue. If you prefer cash-only budgeting, use the cash totals separately. Different inputs can reverse the result, and the example cannot establish that one architecture is generally cheaper.
Content writing, photography, translations, accessibility work, legal review, payment fees, new features and a future migration are excluded unless the real quote includes them. Add relevant items explicitly. Do not insert an “inevitable breach” charge or a percentage saving without evidence.
Check Real Vendor Prices at the Time of Purchase
Use dated vendor quotes and invoices rather than a copied plan-price table. Wix, Squarespace, Webflow, Netlify and Cloudflare Pages publish their own plan conditions.
Check currency, VAT, billing term, introductory versus renewal price, traffic or credit allowances, content limits, team seats, support and paid integrations. A site subscription may not include every workspace or export capability. For example, Webflow’s export documentation distinguishes code export from a complete portable copy of hosted functionality.
For hosting quotes with changing introductory rates, use the hosting cost comparison over the same horizon.
Hidden Costs to Put in the Scope
- Content and approvals: Who supplies text, images and sign-off, and how many revision rounds are included?
- Maintenance: Which updates, restores and compatibility fixes are covered, and which are billed separately?
- Integrations: Who pays for forms, email, payments, analytics and automation as usage changes?
- Business time: Who learns the editor, handles requests and coordinates suppliers?
- Exit work: What can be exported, under what rights, and what must be rebuilt?
- Incidents and changes: What coverage exists, how are urgent rates agreed, and which contingency costs are reasonable for this business?
Maintenance hours and incident costs need estimates tied to the scope. They are not fixed by whether a site uses WordPress or a static generator.
Compare Quotes Before Signing
Ask for deliverables, acceptance criteria, timeline assumptions, payment milestones, recurring charges and exit terms. Use the developer questions checklist to discuss operation and ownership transfer guide to clarify accounts and intellectual-property rights.
Separate essentials from optional work and compare a base case with higher usage, more editing or changed platform prices. Ask suppliers what would invalidate their estimate. A smaller launch may be appropriate, but neither business revenue nor headcount determines a mandatory website budget.
If you need help comparing proposals, request a review of the actual scope and assumptions. A credible recommendation should show the trade-offs and arithmetic rather than promise savings from the architecture label.
