Estimating a website project is not a matter of guessing how many weeks it will take and multiplying by your hourly rate. A useful estimate connects the promised outcome to the work required to produce it: decisions, design, development, content handling, reviews, testing and launch.
That connection matters commercially. If you miss a workstream, the team absorbs the cost or has to negotiate a change after the client expects it to be included. If you add a broad cushion without explaining what it covers, your fee may look arbitrary. A work-breakdown method gives you a better basis for both the number and the conversation around it.
The method below is designed for small and midsize agencies quoting a defined website project. The example is illustrative, not a benchmark: actual effort depends on the platform, content condition, integrations, decision-making and quality bar.
Start with a bounded project, not a page count
“A 10-page website” describes one dimension of the work, not the full scope. Ten pages built from one approved template and supplied copy may be simpler than five pages with custom interactions, a migration and complex approval requirements.
Before estimating, write down what the project is meant to deliver and what is known about its boundaries. For example: a marketing site for a professional-services firm, built on its existing CMS, with a defined set of page templates, a client-owned content team and one analytics integration.
Clarify the questions that can change effort materially:
- Is this a redesign on the current platform or a migration to a new one?
- How many distinct page templates are needed, and which pages are variations?
- Who supplies, edits and enters the content? How many existing pages need migration?
- Are there forms, booking flows, search, ecommerce or third-party integrations?
- Who approves the work, and how many review rounds are included?
- What does launch support include, and who is responsible for hosting and DNS?
If the answers are missing, mark them as assumptions, use ranges, or make further discovery a paid phase. A discovery conversation can surface budget, decision process and project constraints; this agency discovery-call checklist can help structure that discussion.
Build a work breakdown structure
A work breakdown structure (WBS) is a list of the deliverables and activities needed to complete the project. It makes invisible work visible. Start with phases, then break each phase into tasks that are specific enough to estimate.
1. Discovery and definition
Include kickoff, stakeholder interviews, reviewing existing materials, clarifying requirements, agreeing on success measures and documenting decisions. If the client already has a strong brief and approved sitemap, this may be light. If the agency must reconcile conflicting stakeholder requests, allow time for that work.
2. Information architecture and design
Estimate sitemap refinement, user flows, wireframes, visual concepts, design-system work and responsive states. Separate unique templates from pages that reuse an approved pattern. A homepage, service detail page and resource listing may need three distinct layouts; eight service pages built from one template do not necessarily require eight designs.
3. Development and configuration
Break out CMS setup, reusable components, page templates, front-end implementation, back-end configuration, forms, integrations and responsive behavior. Identify whether the work uses established components or requires custom functionality. “Build the site” is too broad to estimate reliably.
4. Content and migration
Specify who writes, edits, enters and checks content. Migration is not automatically a copy-and-paste task: old pages may have inconsistent formatting, image files may need preparation, and URLs may need mapping. Include redirect planning when URLs change and name the person responsible for supplying final copy.
5. Quality assurance and launch
Allow for functional testing, responsive checks, browser coverage, accessibility review, defect fixes, analytics verification and launch coordination. The precise testing scope should fit the project’s risk and requirements. For example, if accessibility conformance is part of the brief, state the intended standard and evaluation scope; the W3C Web Content Accessibility Guidelines (WCAG) 2.2 provide testable success criteria, rather than a vague promise that a site will be “fully accessible.”
6. Project management and client reviews
PM effort is real delivery effort. Include scheduling, status updates, internal handoffs, meeting preparation, decision tracking and consolidating client feedback. The more stakeholders and approval steps involved, the more coordination the project may require. Do not assume that a fixed-fee project makes this work disappear.
Estimate effort task by task
For each task, estimate the effort required from each role that will do it. Hours are useful even when you ultimately sell a fixed fee: they reveal whether the work fits the team’s capacity and whether the proposed price can support delivery.
Use three-point estimates when uncertainty is meaningful:
- Low: the work goes smoothly under the stated assumptions.
- Likely: the outcome you currently expect.
- High: a plausible difficult case, not a disaster scenario.
You can use the likely estimate for an initial plan, or calculate a weighted estimate such as (low + 4 × likely + high) ÷ 6. The formula is a planning aid, not a source of certainty. Keep the range visible if the inputs are still uncertain.
Here is an illustrative estimate for a small marketing site with a CMS, a handful of reusable templates, client-supplied copy and a standard contact form:
| Workstream | Illustrative hours | What is included |
|---|---|---|
| Discovery and requirements | 10 | Kickoff, review, requirements and decisions |
| Information architecture and wireframes | 15 | Sitemap refinement and key page structures |
| Visual design | 30 | Core templates, responsive design direction and revisions |
| Development and CMS setup | 50 | Reusable components, templates and standard form |
| Content entry and migration | 16 | Prepare and enter agreed content set |
| QA and fixes | 16 | Functional and responsive checks, defect correction |
| Project management and reviews | 15 | Coordination, updates and feedback rounds |
| Launch and handover | 8 | Launch checklist, deployment coordination and handover |
| Estimated delivery effort | 160 | Before project-specific risk allowance |
That total is not a promise that the calendar duration will be 160 hours divided by one person’s weekly capacity. Work has dependencies: design approval may need to happen before build, while client content may arrive late or in batches. Assign ownership and sequence tasks separately from estimating effort.
Turn effort into a price
Choose a pricing basis that fits how well the work is defined. For a stable scope, a fixed fee can give the client budget certainty, while the agency takes on the risk of delivering within its estimate. If requirements are likely to change or need investigation, time-and-materials or a paid discovery phase may be more appropriate. The trade-offs are explained in this guide to fixed-fee versus time-and-materials agency pricing.
For a fixed-fee estimate, calculate internal delivery effort first, then apply your agency’s pricing logic. For illustration, if the 160 hours above are priced at a blended delivery rate of $150 per hour, the baseline is $24,000. That rate is an example, not a recommended market rate. Your actual model should reflect labor costs, non-billable time, overhead, profit requirements and the mix of roles involved.
Next, consider the risk in the defined scope. Do not add an arbitrary percentage just because the number feels safer. Identify specific uncertainties—such as content readiness, an untested integration or unclear legacy redirects—and decide whether to reduce them through discovery, qualify them as assumptions, price a reasonable allowance, or exclude them pending a change request. If you build a reserve into a fixed fee, explain the scope and assumptions clearly; it need not appear as a separate “contingency” line.
Keep external costs distinct where useful: paid fonts, stock assets, hosting, licenses or specialist testing should be identified as client-paid expenses or included with a clear limit. Avoid silently absorbing costs that recur after launch.
Make uncertainty visible in the proposal
A good estimate is not just a number. It sets expectations about what the client is buying and what happens when the facts differ from the assumptions.
Document the following in the proposal or statement of work:
- Deliverables: page templates, functionality, integrations, content volume and handover items.
- Client responsibilities: content, access, approvals, legal review and a named decision-maker.
- Review limits: how many consolidated rounds are included at each stage and what counts as a revision.
- Exclusions: for example, copywriting, custom photography, ongoing SEO, hosting or post-launch support if not included.
- Change process: how new requests are assessed for fee and schedule impact before work begins.
- Acceptance and launch: what “complete” means, what the client must approve, and what must be ready before launch.
Technical requirements should be specific enough to test. If organic search setup is included, name the work—for example, configuring titles and descriptions, checking indexability and preparing redirects—rather than promising rankings. Google’s SEO Starter Guide explains foundational practices, but search outcomes depend on more than the implementation tasks in a website project.
When the client’s budget is below the estimate, change the scope or delivery approach rather than quietly compressing the same work into fewer hours. You might launch with fewer templates, defer a secondary integration, or make content migration a client responsibility. If the project is too small to support your delivery costs, a clear minimum can help; see how to set a minimum project fee.
Review the estimate before you send it
Have someone who did not build the first estimate review the work breakdown. Ask whether every promised deliverable has a corresponding task, whether the named team has the right skills and capacity, and whether client review and handoff time are represented. Compare the estimate with similar past work if you have reliable records, but adjust for differences instead of treating one previous project as a template.
Finally, check the economics after the project is delivered. Compare planned and actual effort by workstream, not only at total-project level. If design was on plan but migration took twice as long, you have a specific estimating lesson: perhaps content condition needs to be assessed earlier or the next proposal should define a migration limit. Over time, those notes make estimates more grounded without pretending every website is the same.
FAQ
How do I estimate a website project when the requirements are incomplete?
Separate known work from unknowns. Estimate the defined portion, list assumptions, and use a paid discovery phase or a time-and-materials arrangement for questions that could materially change scope. Avoid presenting a precise fixed fee for requirements you have not validated.
Should an agency estimate hours even when it charges a fixed fee?
Yes. Hours help you plan staffing, test whether the fee supports delivery and learn from project actuals. The client can buy a fixed outcome without seeing every internal hour, but the agency still needs an effort model.
How much contingency should I add to a website estimate?
There is no universal percentage. Allow for risks you can name, and reduce uncertainty where possible through discovery or explicit assumptions. A known integration risk is more useful to discuss than a generic buffer with no explanation.
What should be included in website QA?
Define QA against the project’s requirements. Common checks include forms and links, responsive layouts, agreed browser coverage, content presentation and launch-critical analytics. If accessibility or security requirements apply, specify the relevant scope and method rather than implying that a basic visual check covers them.
How should I handle extra requests after the estimate is approved?
Compare the request with the documented deliverables and assumptions. If it changes scope, explain the effect on fee, effort and schedule, then get approval before starting the additional work. If it is a correction to work that fails the agreed acceptance criteria, handle it under the original commitment.