Website Development Cost Estimate Template for 2026 (Free, With Calculator)
The short answer
These are 2026 US-market ranges, and they match our website development cost guide, which explains the tiers and drivers in depth. If you only need a quick number, the website development cost calculator is faster. This page is about the document itself: what a website estimate should contain, a template you can copy, and how to tell a solid estimate from a number written to win the deal.
Why bother with a template at all? Because most website budgets that go wrong were never wrong in total. They were wrong in structure. One quote leaves out QA, another assumes you write all the copy, a third has no contingency and turns every surprise into a change request. Put them in the same ten lines and the differences become obvious.
The ten line items of a website estimate
Every serious estimate we see, from a US agency or an offshore team, can be mapped to these lines. Seven make up the build. Contingency sits on top of it. Hosting and maintenance are yearly, and they are the ones most often missing.
| Line item | What it should cover | Typical share | Red flag in an estimate |
|---|---|---|---|
| 1. Discovery | Goals, sitemap, content inventory, key-page wireframes, tech choice | 5–12% of build | Missing entirely on a custom site, or a vague "strategy" fee with no output listed |
| 2. UX/UI design | Style guide, layouts per template, desktop and mobile, revision rounds | 15–30% | Priced per page, with no template count and no revision limit |
| 3. Template build | Responsive front end of each unique template and its components | 20–35% | One lump "development" line with no hours |
| 4. CMS + content | Content types, roles, page loading, languages, redirects, training | 8–15% | Silent on who loads content and how many URLs are migrated |
| 5. Integrations | CRM, email, analytics, booking, search, payments, each named | 0–20% | "Integrations included" without a list |
| 6. QA | Browsers and devices, accessibility, performance, forms | 15–20% of dev hours | "Testing included" with no device list, or no QA at all |
| 7. Project management | Planning, demos, reporting, launch | 10–15% | Zero PM, which means you are the project manager |
| 8. Contingency | Buffer for unknowns, approved in writing | 10–20% on top | Hidden inside line items, or absent on a vague scope |
| 9. Hosting + tools | Hosting, CMS plan, CDN, backups, paid plugins | $300–7,000 a year | Not mentioned, or hosting in the vendor's name |
| 10. Maintenance | Updates, security, monitoring, small changes | 15–20% of build a year | No post-launch offer, or "free support" with no hours |
Estimate calculator: fill the template with your numbers
Set the inputs to your project. The calculator turns them into hours per line item, the way vendors do it internally, then applies the rate of the team you are considering. Everything it produces flows into the copyable template in the next section. The hour models are based on what we see in website estimates for US clients, ours and competitors' that clients share with us. Treat the result as a planning number with a realistic spread, not a quote.
Website estimate builder
| Line item | Hours | Cost |
|---|---|---|
| Discovery | ||
| Design | ||
| Template build | ||
| CMS + content | ||
| Integrations | ||
| QA | ||
| Project management | ||
| Build subtotal | ||
| Contingency | ||
| Hosting + tools, per year | ||
| Maintenance, per year |
The range is skewed upward on purpose: scope grows more often than it shrinks. A US freelancer usually needs fewer PM hours but more of your time, and rarely includes QA.
Two things to notice when you move the sliders. First, templates drive the price far more than pages: going from 7 to 12 templates adds more than going from 25 to 100 pages. Second, the region select changes only the rate, not the hours. The same site needs the same work wherever it is built.
The website estimate template (copy it)
Five blocks: the cover sheet, the line items, assumptions and exclusions, running costs, and a comparison sheet for vendor quotes. Each has a copy button. Table blocks copy as tab-separated rows, so they paste into Google Sheets or Excel as proper columns. Text blocks paste cleanly into a doc or an email.
WEBSITE DEVELOPMENT COST ESTIMATE Client: ____ Vendor: ____ Estimate no.: ____ Date: ____ Valid until: ____ (30–60 days is normal) PROJECT Website type: ____ (marketing site / corporate site / content site / redesign) Platform: ____ Design approach: ____ Unique page templates: ____ Pages to build and fill: ____ Languages: ____ Integrations: ____ (list each one in the line items) PRICE Pricing model: ____ (fixed price / time and materials with cap / hourly) Blended rate: ____ per hour Build estimate (all line items): ____ for ____ hours Contingency (____%, spent only with written approval): ____ Total project budget: ____ Likely final range: ____ to ____ AFTER LAUNCH (per year) Hosting, CMS plan and paid tools: ____ Maintenance and support (____% of build): ____ PAYMENT SCHEDULE ____% on signing / ____% on design approval / ____% on launch TIMELINE Discovery ____ weeks / Design ____ weeks / Build and QA ____ weeks / Launch ____
| Line item | What is included | Hours | Rate | Cost |
|---|---|---|---|---|
| Discovery | Stakeholder interviews, goals and KPIs, sitemap, content inventory, wireframes of key pages, technical approach. Level: ____. | ____ | ____ | ____ |
| UX/UI design | Style guide or design system, ____ template layouts for desktop and mobile, 2 revision rounds. Approach: ____. | ____ | ____ | ____ |
| Template build (front end) | ____ responsive templates and reusable components, coded to the approved design on ____. | ____ | ____ | ____ |
| CMS setup and content | Content types, editor roles, ____ pages loaded, ____ language(s), redirect map from old URLs, editor training. | ____ | ____ | ____ |
| Integrations | ____ integration(s): ____ (CRM, email marketing, analytics, booking, search, payments). Forms tested end to end. | ____ | ____ | ____ |
| QA and accessibility | Browsers and devices: ____. WCAG 2.1 AA checks, Core Web Vitals, forms, links, staging sign-off. | ____ | ____ | ____ |
| Project management | Plan, weekly demo and report, risk log, launch checklist, handover of all accounts and code. | ____ | ____ | ____ |
| Build subtotal | All line items above | ____ | ____ | |
| Contingency | ____% of build. Spent only with written approval, reported separately. | ____ | ||
| Total project budget | Build plus contingency | ____ | ||
| Hosting and tools (per year) | See running costs | ____ | ||
| Maintenance (per year) | ____% of build per year | ____ |
ASSUMPTIONS 1. Client supplies final copy and images by ____. Copywriting is ____ (included / excluded / priced separately). 2. The estimate covers ____ unique templates. A new layout counts as a new template. 3. Platform: ____. Paid themes, plugins and fonts are billed at cost: ____. 4. ____ integration(s) with documented APIs. Accounts and API keys are provided by the client. 5. Two rounds of design revisions per template. Further rounds at ____/hour. 6. Content migration: ____ pages, ____ language(s). Old URL count for redirects: ____. 7. Supported browsers: latest two versions of Chrome, Safari, Edge and Firefox; iOS and Android phones. 8. Accessibility target: WCAG 2.1 AA for templates and components. 9. Client feedback within ____ business days. Delays move the timeline, not the scope. EXCLUDED (priced on request) - Copywriting, photography, video, illustration - Translation (unless listed above) - Paid ads, SEO campaigns, ongoing content production - Third-party license fees and hosting (see running costs) - Features not listed in the line items CHANGE REQUESTS Changes outside this scope are estimated in writing before work starts and billed at ____/hour or from the contingency with approval. OWNERSHIP Client owns the domain, hosting account, CMS, analytics and all code and design files from day one.
| Item | Typical 2026 cost / notes | Per year |
|---|---|---|
| Hosting, CMS plan, CDN, backups | Managed WordPress from about $30/month; Webflow CMS about $23–29/month; headless CMS plus hosting often $100–400/month | ____ |
| Domain and DNS | Usually $15–60 per year per domain | ____ |
| Paid plugins, themes, fonts, forms | Many renew yearly; ask the vendor for a list | ____ |
| Third-party services | Email marketing, CRM seats, search, cookie consent, booking | ____ |
| Maintenance and support | Updates, security patches, uptime monitoring, small changes. ____% of build per year | ____ |
| Content and SEO upkeep | Your team or an agency, not part of the build | ____ |
| Line item | Your baseline | Vendor A | Vendor B | Vendor C | Notes |
|---|---|---|---|---|---|
| Discovery | ____ | ||||
| UX/UI design | ____ | ||||
| Template build (front end) | ____ | ||||
| CMS setup and content | ____ | ||||
| Integrations | ____ | ||||
| QA and accessibility | ____ | ||||
| Project management | ____ | ||||
| Contingency | ____ | Included? Separate? | |||
| Total as quoted | ____ | ||||
| Missing items added at your baseline | QA, PM, content, redirects… | ||||
| Comparable total | ____ | ||||
| Templates assumed | ____ | ||||
| Who writes and loads content | |||||
| Running cost per year | ____ + ____ | ||||
| Overlap hours with your team |
How to use it with vendors: send them the line items and assumptions tabs with your RFP and ask them to answer in this format. Vendors who estimate properly will fill it in a day. The ones who can only give a total will tell you something by struggling. If you are preparing a formal request, our RFP guide covers the rest of the document.
Built by Gilzor
Results we’ve shipped
Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.
How to read a vendor's website estimate
An estimate is a set of assumptions with a price attached. Read the assumptions first and the price last. This is the order we use when a client asks us to look at a competing quote.
- Count the templates, not the pagesFind the number of unique layouts the vendor priced. "A 20-page website" can mean 4 templates or 15. If the estimate doesn't say, ask; it is the single biggest driver of design and build hours.
- Find the content lineWho writes copy, who loads it, how many old URLs get redirects? A low quote that assumes you deliver every word and image ready to paste is cheap for a reason. Content delays are also the most common reason website timelines slip.
- Check QA, PM and contingency are visibleIf they are absent, they are either hidden inside other lines (fine, if the vendor can show it) or not happening (not fine). QA of 15–20% of development hours is normal on a professional build.
- Read the integrations by name"CRM integration" can mean a form that emails your sales team or a two-way sync with HubSpot including lead scoring. Each named integration should carry its own hours. Our API integration cost guide explains the spread.
- Look at the pricing model and change rulesA fixed price on a vague scope will include a risk buffer, and every surprise becomes a change request at full rate. Time and materials needs a cap and weekly reporting. See fixed-cost software development for how vendors price risk.
- Ask for the running costs in writingHosting, CMS plan, paid plugins and a maintenance offer. Also check that the domain, hosting and code accounts will be in your name from day one.
The size of the gap between estimates surprises people every time. The Standish Group's CHAOS research has long reported that only about a third of software projects finish on time, on budget and with the planned scope, and unclear requirements sit near the top of the reasons. Research by McKinsey and the University of Oxford on more than 5,400 large IT projects found they ran 45% over budget on average. A website is far smaller and safer than those projects, but the mechanism is the same: the estimate was a guess about scope that nobody wrote down.
A worked comparison: three quotes, one brief
A typical case from first calls: a B2B company sends the same brief (about 8 templates, 30 pages, HubSpot and analytics) to three vendors. On totals, the decision looks easy. After normalizing in the comparison sheet, it isn't.
| Line item | Vendor A: US agency | Vendor B: offshore agency | Vendor C: freelancer |
|---|---|---|---|
| Discovery | $6,000 | $2,000 | Not included |
| Design | $15,000 | $6,000 | $2,500 (theme customization) |
| Template build | $14,000 | $5,600 | $3,500 |
| CMS + content | $5,000 | $2,000 | Client loads content |
| Integrations | $4,000 | $1,600 | $500 (form plugin to HubSpot) |
| QA | $4,500 | $1,700 | Not included |
| Project management | $5,500 | $2,300 | Not included |
| Contingency | Inside the fixed price | $3,200 (15%) | None |
| Total as quoted | $54,000 | $24,400 | $6,500 |
| Comparable total (gaps filled) | $54,000 | $24,400 | $14,000–17,000 plus your time |
The freelancer's quote was never $6,500. It was $6,500 for a narrower site, plus the work you'd do or buy separately. That can still be the right choice for a simple site with a marketing lead who has time. Vendors A and B quote the same scope; the difference is the hourly rate and the overlap window. Vendor B's 15% contingency looks like padding until you notice that Vendor A built the same buffer into its fixed price without showing it.
The same estimate in different regions
The hours above don't change by country. The rate does. Here is the calculator's default site (about 386 hours with contingency at 15%) priced with typical 2026 blended rates for a US client.
The rate gap reflects labor markets. The Bureau of Labor Statistics put the median US web developer wage at $92,650 in May 2025, before benefits, payroll taxes and the agency's overhead and margin. Latin American and Central European agencies price similarly; the difference for a US buyer is the clock. Latin American teams share most of the US workday. We are a Polish and Cypriot company, which is offshore for the US: two to four shared hours with the East Coast on a shifted schedule, and little with California. For a website with weekly reviews and written feedback that works fine. If your marketing lead wants live working sessions every afternoon Pacific time, it doesn't. The trade-off is laid out in our nearshore software development rates guide.
Quiz: which kind of estimate should you ask for?
Not every project is ready for a fixed bid. Asking for the wrong kind of estimate gets you either a padded number or a cheap number that grows. Five questions:
What estimate fits your website project?
Hidden costs that estimates leave out
These are the lines we most often find missing when clients show us a quote they already signed.
- Content. Copywriting, photography, and the hours of loading and formatting pages. Often 10–25% of the total project effort when somebody finally does it.
- Migration and redirects. An existing site with hundreds of indexed URLs needs a redirect map, or you trade a new design for lost search traffic.
- Accessibility. UsableNet counted more than 5,000 digital accessibility lawsuits in US federal and key state courts in 2025. Building to WCAG 2.1 AA from the start adds a few percent to design and QA; retrofitting later costs far more.
- Paid plugins, fonts and SaaS. Licenses that renew every year, plus CRM seats or email plans the integrations depend on.
- Hosting and the CMS plan. Managed WordPress starts around $30 a month, a Webflow CMS site plan around $23–29 a month before workspace seats, and headless setups often run $100–400 a month across CMS, hosting and monitoring.
- Maintenance. Budget 15–20% of the build per year. Over three years that's roughly half the build cost again. Our website development and maintenance cost article breaks it down.
- Your own team's time. Reviews, feedback rounds, approvals. Someone on your side should plan for several hours a week.
How to reduce the estimate without breaking the site
- Merge templates. Most sites can drop two or three layouts by using flexible sections. In the calculator, going from 10 templates to 7 saves around 20% of the build.
- Finish the copy before design. It removes a revision round and the most common cause of delay.
- Use a platform your marketers can run. WordPress powers about 42% of all websites according to W3Techs, and builders cover many marketing sites. Headless is worth it for large, multi-channel sites, not for 25 pages.
- Phase the scope. Launch with the pages that sell. The resource hub, the second language and the calculator widget can wait for phase two.
- Pay for discovery on a vague brief. It feels like an extra cost and usually lowers the total, because vendors stop pricing uncertainty.
- Change the rate, keep the process. A Latin American or Central European team builds the same site for roughly 40–45% of US agency pricing, provided reviews and QA stay strict.
- Don't cut QA or redirects. Those savings come back as bugs on launch day or lost search traffic.
For broader tactics across software projects, see how to reduce software development cost.
What we see in estimates and first calls
We have launched 70+ projects over seven-plus years, mostly for startups and SMBs, and these patterns repeat:
- The brief says pages, the vendor prices templates. Half the "why are these quotes so different" questions end when both vendors list their template counts.
- Integrations are underestimated on both sides. A HubSpot form is a few hours. A two-way sync with custom fields and lead routing is days. The estimate has to say which.
- Contingency gets cut first in negotiations. It then reappears as change requests, usually at a higher effective price because there's no room left.
- Nobody owns content. Projects where copy is ready before design starts are the ones that ship on schedule. It's a big part of how we keep 98% of projects on time.
- Running costs surprise people in month 13. Plugin renewals, hosting upgrades, a security patch that breaks a form. A maintenance line in the original estimate avoids the awkward conversation.
If a site is part of a bigger product, the scope often belongs in a web application estimate instead, with different line items and a much wider range. And if the estimate needs a proper requirements phase first, our business analysis team does that as a standalone service.
FAQ
What should a website development cost estimate include?
How much does a website cost in 2026?
How much contingency should a website estimate include?
Is a fixed-price website estimate better than hourly?
How do I compare website estimates from different vendors?
How much does website maintenance cost per year?
Where Gilzor fits
We build marketing, corporate and content sites as part of our web development service, with design, QA and project management on the team rather than outsourced. We send estimates in this ten-line format, with the assumptions written out, and we are happy to look at one you already have. For a three-page brochure site with ready copy, a builder is the better buy, and we will tell you that.
No sales pitch
Get a straight answer for your project
Tell us what you’re building. We’ll reply with options, a rough cost and timeline. If we’re not the right fit, we’ll say so.
Co-Founder of Gilzor. Works with founders and product companies on how to staff and run engineering: team extension, dedicated teams, and getting stalled projects moving again.
Gilzor · Web Development partner
Need a team for your web product?
Services
Web DevelopmentCustom websites and web apps — front-end, back-end, launch and support.→By company type
Selected projects
The team behind them
