A useful estimate begins with a clear scope.
Two proposals can describe a “business website” while including very different work. One may cover a small set of pages using an existing template. Another may include content planning, custom design, migration, integrations and ongoing support.
Compare the work before you compare the total. This guide explains the decisions that change the budget. It does not publish a Krazio price list or a universal market rate.
The main cost drivers
1. Pages, layouts and content
Page count matters, but unique layouts and the readiness of your content matter too. Reusing a well-designed service template is different from designing every page separately. Confirm whether writing, image selection and content entry are included.
2. Design and review scope
A custom design needs discovery and review time. The proposal should explain which screens you will review, how feedback is handled and what happens when the agreed scope changes.
3. Features and integrations
Forms, booking tools, CRM connections, user accounts and payment workflows add work beyond presentation. Existing API documentation can make scoping easier; unclear or unavailable interfaces can create extra work.
4. Migration and search continuity
For a redesign, include content transfer, redirect mapping, important tracking checks and testing of existing enquiry paths. Simply replacing the homepage leaves those jobs unresolved.
5. Ownership after launch
Hosting, domain renewals, premium plugins, maintenance and third-party subscriptions should be visible in the proposal. Check which costs recur and which are paid directly to a provider.
Make proposals easier to compare.
| Ask the supplier | Look for |
|---|---|
| Which pages and features are included? | An itemised scope with exclusions |
| Who provides content and images? | Clear responsibilities and review stages |
| What connects to our CRM? | Named fields, integration boundaries and error handling |
| What will we own? | Accounts, source files, licences and handover details |
| What are the ongoing costs? | Hosting, subscriptions and maintenance shown separately |
| How are taxes and changes presented? | A clear total, applicable tax treatment and change process |
Set a budget preference without guessing a specification.
It is fine to share a budget range before you know the final solution. A useful discussion separates essential requirements from improvements that can wait, then assesses what can be delivered within that scope.
For example, start with the key service pages and a reliable enquiry flow, then add a customer portal when there is a clear need. Phasing only helps if the first release can stand on its own.
Before you approve: ask for the scope, milestones, dependencies, ongoing costs and acceptance criteria in writing. A lower headline price is not necessarily a lower total cost.
Ready to make the brief concrete? Tell us what your website needs to achieve.