Why the range is so wide
Ask ten agencies what a contractor website costs and you'll get ten different numbers, because the question is incomplete. A single-truck electrician with one service area and a phone number needs a different build than a five-location HVAC company running ServiceTitan, a call tracking platform, and financing integrations. Both are "custom contractor websites." The price is not the same, and it shouldn't be.
What actually drives cost on a hand-coded build: page count (a 12-page site is not the same job as a 90-page silo with service-area pages for eleven counties), the number of systems the site has to connect to, whether content already exists or has to be written from scratch, and how much of the old site's data (reviews, photos, job history) needs to migrate over. Design complexity matters less than most owners think. Wiring and content volume drive the real number.
The other variable, rarely discussed upfront, is what you're actually buying. A cheap WordPress theme install and a hand-coded static site both get called a "custom website" in sales copy. They are not comparable products. One is a rented storefront on a plugin platform, paying a monthly toll to keep the lights on. The other is code you own outright, hosted on infrastructure you control, with no plugin surface for someone to hack. That difference belongs to a separate comparison (see the WordPress vs. custom-coded breakdown linked below), but it explains why two "custom" quotes can be five figures apart for what looks like the same page count on paper.
There's also a labor-market reality worth naming plainly. Hand-coding a page takes longer than dragging blocks in a page builder, and that labor shows up in the quote. Contractors sometimes balk at this until they price out what a slow, plugin-choked WordPress site costs them in lost calls over a year. A site that loads in four seconds instead of two loses visitors before they ever see the phone number. The build cost and the cost of a bad build both belong on the same balance sheet, even though only one shows up on the invoice.
- Page count and service-area coverage (single city vs. multi-county vs. multi-location)
- Number of integrations: booking software, CRM, phone tracking, payments, review widgets
- Whether content is written from scratch or migrated from an existing site
- Migration complexity if you're moving off WordPress or a franchise platform
- Timeline pressure (rush builds cost more, always)
Typical price bands for a custom-coded build
These are ranges, not quotes. Every contractor's tool stack and page count is different, and the only honest number comes from a strategy call where we look at what you actually run the business on. That said, here's the shape of the market for a hand-coded, no-WordPress build:
| Build type | What's included | Typical range |
|---|---|---|
| Single-trade, single-location | Home, services, about, contact, one service-area page, lead form, basic schema | Low thousands |
| Single-trade, multi-area | Above plus service-area pages per city/county, expanded FAQ, review display | Mid four figures to low five figures |
| Multi-trade or multi-location | Separate silo pages per trade or per branch, deeper schema, more forms, more integrations | Mid to high five figures |
| WordPress-to-static migration | Full rebuild plus content/data migration, redirect mapping, integration re-wiring | Varies by page count and integration count, usually comparable to a fresh build plus migration time |
Integrations are usually quoted separately from the base build because the labor is different work: connecting a form to your CRM's API, wiring call tracking numbers to your ad campaigns, or hooking a booking widget into ServiceTitan or Jobber isn't page design, it's software integration. A contractor with three tools to wire in pays less for that piece than one with eight.
Where a lot of contractors get surprised is service-area page count. A roofer working one city needs one or two location pages. A roofer working eleven counties across a metro region needs eleven or more, each with genuinely different content (not the same page with the city name swapped, which search engines see through immediately and rank poorly). That's not padding. That's the actual work of ranking in each of those places, and it moves the page count, and therefore the price, more than almost anything else on this list.
Content writing is the other line item people underestimate. A site with real service descriptions, honest FAQ answers, and location-specific detail written from how the business actually operates costs more to produce than filler copy, but it's also the content that shows up when someone asks an AI assistant to recommend a contractor in their area. Thin, templated copy doesn't get cited. That's a build-cost driver worth paying for, not a place to cut corners.
What drives the number up (and what doesn't)
Some things are worth paying for. Some are agency padding dressed up as value. Here's how to tell the difference.
Worth paying for: real integrations that save you double-entry (a lead form that writes straight into your CRM instead of you copy-pasting emails), call tracking wired to specific campaigns so you know which ad or page actually produced the phone call, and enough service-area pages to actually rank in the counties you work, not just the one where your shop sits. These cost labor hours because they're real engineering, not templates.
Not worth paying extra for: a page builder license disguised as "custom design," stock photo packages, or a CMS subscription you'll pay monthly forever on top of the build. If a quote includes a recurring platform fee beyond hosting, ask what that fee is actually buying you. A hand-coded static site has no CMS license to renew because there's no CMS.
- Page count and unique service-area content: up
- Integration count (CRM, booking, phone, payments): up
- Content written from your job history and specifics, not filler: up (but pays back in AI-search and organic visibility)
- Stock templates rebranded with your logo: should bring the price down, not up
- Recurring page-builder or CMS licensing fees: a red flag, not a value-add
Rush timelines push the number up too, and that's a legitimate cost, not padding. Compressing a build that would normally take several weeks into a couple weeks means paying for concentrated labor, sometimes evenings and weekends, to hit the date. If you're not in a rush, saying so upfront can bring the quote down, because it gives room to sequence the work around other clients instead of clearing the calendar for you.
The honest version: a contractor who needs six pages and a contact form pays less than a five-location company wiring ServiceTitan, a payment processor, and call tracking into every page. That's not upselling. That's two different jobs, and pricing them the same would mean overcharging the small job to subsidize the big one, or underpricing the big job until the integrations get rushed and something breaks after launch.
Custom-coded vs. WordPress: the cost picture nobody shows you
A WordPress theme install often quotes cheaper upfront. What that quote leaves out: plugin licensing renewals, hosting that scales in cost as traffic grows, security patching (or a hack that costs a redesign to fix), and page-builder bloat that slows the site down until Core Web Vitals tank your rankings. None of that shows up in the initial number. All of it shows up on the invoice eighteen months later, or in the ranking drop nobody can explain.
A hand-coded site has a higher relative build cost per page in some cases, because there's no theme doing the work for you, every page is built to spec. But there's no plugin attack surface, no monthly page-builder fee, and no mystery slowdown from a dozen plugins fighting each other. Hosting on Cloudflare's own infrastructure keeps load times under two seconds anywhere in the US, and that speed is a build outcome, not a plugin you bought.
The real comparison isn't sticker price. It's total cost of ownership over three to five years, plus who owns the code and domain when the relationship ends. On a hand-coded build, you get the full codebase and domain, no lock-in, no held-hostage renewal calls. That distinction gets a full breakdown in the linked comparison guide below. This section exists to flag it as a cost factor, not re-teach the whole argument.
There's a specific pattern worth naming because it comes up often enough to have a name: the "hostage site." An owner signs with an agency that builds on a proprietary or heavily-customized WordPress install, and when the relationship sours or the agency goes quiet, the owner can't get the login, can't move the domain cleanly, or discovers the site was never really theirs to take. That risk doesn't exist on a hand-coded build where you hold the code and the domain from day one. If you've been burned by that once, it's the single biggest reason to price ownership into the decision, not just the build.
- WordPress: lower sticker price, ongoing plugin/hosting/security costs, platform lock-in risk
- Custom-coded: higher relative build cost, no recurring plugin fees, no plugin hack surface, you own the code
- Migration: moving from WordPress to custom-coded is a real project cost, but it's a one-time cost, not a recurring one
What integrations typically add to the number
This is the piece most contractor website quotes skip entirely, and it's usually where the real cost lives for an established business. If you're running ServiceTitan, Jobber, or Housecall Pro, wiring your site's booking form or scheduling widget into that system is a distinct line item from building the page it sits on. Same for a CRM: a lead form that fires a webhook into your CRM instead of landing in an inbox someone has to manually re-key is worth the integration cost, because it's the difference between a lead getting worked in minutes versus sitting in an inbox until Monday.
Phone and call tracking is another one. If you run paid ads, radio, or truck wraps alongside the website, wiring dynamic number insertion so you can see which channel actually drove the call is standard practice for an established contractor, and it's a build-time integration, not an afterthought bolted on later. Payment integrations (deposits, invoicing links) and review widgets that pull live from Google instead of a static testimonials page round out the common list.
None of these are exotic. All of them take real wiring time: API keys, webhook testing, and confirming the data actually lands where it's supposed to before the site goes live. A quote that doesn't mention any of your existing tools by name probably hasn't priced them in, which means the real number shows up later as a change order.
A practical note for owners running an older, homegrown system: not every piece of software has a clean, documented API. Some booking and CRM platforms are easier to wire into than others, and that affects the labor estimate on the integration piece specifically, separate from the base build. If your current software is unusual or dated, say so upfront. It changes the integration quote, not the base page-building quote, and finding that out mid-build costs more than finding it out on the strategy call.
- CRM webhook wiring (lead form to CRM, no manual re-entry)
- Booking/scheduling integration (ServiceTitan, Jobber, Housecall Pro, or similar)
- Call tracking with dynamic number insertion by channel
- Payment/deposit links and invoicing integration
- Live review pull (Google) instead of a static testimonials page
What happens after launch: ongoing costs to expect
The build price isn't the last number you'll see, and any quote that pretends otherwise is incomplete. What comes after launch on a hand-coded site is usually short and predictable: hosting (typically low, since static sites hosted on Cloudflare's network don't need the server horsepower a database-driven WordPress site does), a domain renewal you already pay regardless of who built the site, and time for updates when you want to add a page, a new service area, or refresh pricing.
Compare that to the ongoing cost list on a heavily-plugged WordPress build: premium plugin licenses that renew annually per plugin, a hosting plan that has to scale up as the plugin stack gets heavier, and periodic security patching that either costs money directly or costs money indirectly when a plugin vulnerability takes the site down and it has to get rebuilt. None of that is hypothetical. It's the normal maintenance load of a plugin-based platform, and it's why total cost of ownership tells a different story than the build invoice alone.
There's a middle-ground question worth asking any agency before you sign: what happens to updates after launch. On a hand-coded site, adding a page or a service area is a scoped, occasional cost, not a recurring subscription. Ask specifically how that's billed, whether it's hourly, a flat per-page rate, or bundled into a maintenance retainer, before you're mid-relationship trying to figure out why a one-page addition costs what it costs.
- Hosting: typically lower and more predictable on a static, hand-coded build
- Domain renewal: a cost you carry regardless of who built the site
- Plugin licensing: a recurring cost specific to WordPress-style builds, not custom-coded ones
- Security patching: budget for it on WordPress; largely a non-issue on a hand-coded static site
- Post-launch updates: ask upfront how additions (new pages, new service areas) get billed
How to get an accurate number for your business
The only way to get a real number, not a teaser, is to walk through what you actually run the business on. That means naming your booking software, your CRM if you have one, whether you track calls by channel today, how many service areas you work, and whether you're rebuilding from scratch or migrating off an existing site with reviews and job history to carry over.
Bring those specifics to a strategy call and you'll get a scoped number, not a range pulled from a rate card. A contractor who already knows their tool stack and page count gets a fast, accurate quote. A contractor who just wants "a website" gets a discovery conversation first, because building the wrong scope costs more to fix later than it does to scope correctly up front.
One more thing worth saying plainly: if a quote comes back suspiciously low and doesn't ask a single question about your CRM, booking software, or service areas, that's not a good deal. That's a template with your logo on it, and the real cost shows up later in plugin fees, security patches, or a rebuild in eighteen months.
- Know your booking/CRM/phone tools before the call, name them specifically
- Know your service areas (cities/counties you actually want to rank in)
- Decide upfront: fresh build or migration off an existing site
- Treat a no-questions-asked low quote as a warning sign, not a win