Skip to main content Scroll Top

Website Design & Development


Most small business websites are built in about two days here, once content is ready. The two-to-four weeks the industry quotes is mostly queue time and approval loops, not build time. This page covers what gets built, what it costs, and what never gets skipped for speed.

Updated September 2026 · Written and maintained by the Progression Agency strategy team

We build websites that produce inquiries, and we publish the standard we build them to so you can hold us to it. Nine stages, fourteen technical commitments, a redirect map before development starts, an open CMS you can take anywhere, and a scope document that says what is excluded as well as what is included. Prices are below. So is the honest advice about when you should repair rather than rebuild — which is more often than agencies admit.

What a website has to do

What we build, and what it has to do
Four numbers we hold every build to. If a site misses any of them it is not finished, however good it looks in a portfolio.

Strip away everything else and a business website does four jobs. It has to be found. It has to be understood by a stranger in about four seconds. It has to be usable on a phone, on a bad connection, by somebody in a hurry. And it has to make contacting you effortless. A site that does all four while looking ordinary outperforms a beautiful one that does three.

That is the standard we design to, and every number above is measurable rather than asserted. If a build misses any of them it is not finished, however good it looks in a portfolio.

Our process

Our build process, stage by stage
Stage two decides whether the site can ever rank, and stage eight decides whether you keep the rankings you already have. Both are invisible in a portfolio.

Nine stages. The first and the eighth are the ones most agencies skip, and they are the two that determine whether the site can rank at all and whether you keep the rankings you already have.

Stage one: discovery

Before anybody opens a design tool we need your revenue by service line, your margin, your close rate on inbound inquiries, your capacity and your seasonality. Without those the site gets optimized toward whatever is easiest to generate rather than toward what is worth having, and every subsequent decision is a guess dressed as a preference.

Discovery — Stage one. Your unit economics before anybody opens a design tool.

Stage two: architecture

The sitemap, derived from what people actually search rather than from how your business is organized internally. One page per intent, mapped before anything is designed. This is the stage that decides whether the site can ever rank, and it is invisible in every portfolio you will ever look at.

Architecture — Stage two. The sitemap decides whether the site can ever rank.

Stage three: the content plan

What each page must contain, who writes it, who approves it, and by when. The single largest cause of website projects running late lives here, and it is almost always client-side — a draft waiting for a review nobody has time for. We agree the dates up front and we chase them.

Content plan — Stage three. Who writes it, who approves it, by when.

Stage four: design

Unique templates rather than unique pages. A type scale, a color system, spacing rules, component states, and responsive behavior tested at four breakpoints. When you compare quotes, count templates rather than pages — a twelve-page site built from three templates is a completely different job from one needing nine.

Design — Stage four. Unique templates, a type scale, component states.

Stage five: build

Semantic HTML with a logical heading order. An open-source CMS you can host anywhere. Structured data implemented per template rather than bolted onto the homepage. A performance budget agreed at the start and enforced, rather than a performance audit at the end.

Build — Stage five. Semantic HTML, open CMS, performance budgeted from the start.

Stage six: content production

Written, edited and photographed. The pages that rank contain something the pages already ranking do not — a number you measured, a process you actually follow, a constraint only somebody in your business would know. That requires interviewing your people, so we book that time in advance.

Production — Stage six. Real information, real photography, real editing.

Stage seven: QA

Accessibility against WCAG 2.2 AA. Performance measured on a throttled mobile connection rather than on office fibre. Every form submitted from a real phone with the email confirmed received. Structured data validated per template. Browser and device matrix checked.

QA — Stage seven. Accessibility, performance, forms, structured data.

Stage eight: redirect mapping

Every existing indexed URL mapped to a specific new URL, implemented as a 301 and tested on staging before launch day. This document is produced before development starts, not before launch, because producing it early forces somebody to look at which pages actually earn traffic before deciding to delete them.

Redirects — Stage eight. Every indexed URL mapped and tested on staging.

Stage nine: launch and verification

Within the hour of going live: sitemap submitted, Search Console verified, the site crawled for 404s and redirect chains, forms tested again, the staging noindex tag confirmed removed, and the top fifty URLs checked by hand. Then again the next morning.

Launch — Stage nine. Verified within the hour, then again the next morning.

What you get

What you get, itemized
Every row is in the scope document, not in a sales conversation. Compare this against any other proposal you have received – the differences will be instructive.

Every row above appears in the scope document rather than in a sales conversation. Take the list to any other proposal you have received and compare — the differences are usually more informative than the prices.

No lock-in — Ever. Open CMS, your hosting, your domain, your files.

What it costs

What we charge, by build type
The last row is the one we recommend most often and sell least. If your site converts, is indexed and merely looks dated, restyling it costs a fraction and risks nothing that already works.
Fixed-scope pricing
Build typePrice fromTypical timelineWhat it includes
Restyle in place$4,8003–5 weeksNew type, color and imagery on your existing structure. No ranking risk.
Single landing page$1,4001–2 weeksOne template, copy, form, tracking
Brochure site, 5–8 pages$9,5006–8 weeks2–3 templates, content plan, structured data, redirect map
Business site, 10–16 pages$18,0008–13 weeks4–6 templates, service pages, full technical standard
Site plus content program$36,00014–20 weeks30–60 pages, internal linking, keyword-led architecture
Bilingual site, 12–20 pages$26,00012–18 weeksTwo languages written natively, correct hreflang
Ecommerce, under 200 SKUs$34,00012–18 weeksCatalog, checkout, product schema, analytics
Ecommerce with integrations$78,00020–32 weeksERP, PIM or fulfillment integration, data migration
Accessibility remediation$4,0003–6 weeksExisting site brought to WCAG 2.2 AA

Hosting and maintenance are separate and optional — you are welcome to host anywhere, and we will help you set it up either way. The full market context is on how much does a website cost and our wider rates are on marketing agency pricing.

Where the budget goes on a $18,000 build
Buyers over-value design and under-value discovery, content and QA. The gap on the first and fourth bars is where most disappointing website projects are actually decided.

Where the money actually goes

Buyers consistently expect design to be nearly half the budget. On a build that performs it is closer to a fifth, with discovery, content and QA taking a third between them. That gap is where most disappointing website projects are decided, and it is worth understanding before you compare two quotes on price alone.

Where buyers think the money goes
The rest is discovery, content and QA

When you should not rebuild

Rebuild, restyle or repair?
Green means rebuild is probably right; red means repair or diagnose first. We publish this knowing it costs us projects, because rebuilding a site that already converts is the most expensive mistake in this category.

We publish this knowing it costs us projects. Rebuilding a site that already converts is the most expensive mistake in this category — it costs several times what a restyle costs and it risks rankings that a restyle does not touch. If your site is fast, indexed, converting and merely dated, we will tell you to restyle it.

Restyle versus rebuild
And a rebuild risks rankings a restyle does not

Restyle in place

New typography, new color system, new imagery, updated components — applied to your existing structure and URLs. Three to five weeks, a fraction of the cost, and nothing that currently works is at risk. This is the right answer more often than the industry admits.

Repair rather than replace

If the problems are a broken form, missing service pages, no internal links and slow images, those are fixable in a fortnight on the site you have. We will quote that instead, and we will tell you what it will and will not solve.

Instrument before you decide

If there is no analytics and no Search Console, nobody — including us — can tell you whether the site is your constraint. Install measurement, wait a month, and decide with data. That advice costs you nothing and it is the correct first step surprisingly often.

Conversion: the part that decides whether any of it was worth it

Conversion work, ranked by measured lift
Nine of these ten can be done on the site you already have. We will tell you when that is the right answer, and it frequently is.

Traffic is a multiplier applied to a conversion rate. A site converting at 0.8% against a 3% benchmark discards three quarters of everything every channel delivers, and fixing that is cheaper and faster than tripling traffic. Nine of the ten fixes above can be done on the site you already have.

Brochure versus asset at 18 months
Same traffic, same budget, different sitemap

The four-second test

Show your homepage to somebody who has never seen it, for four seconds, then take it away and ask what the business does, where it operates and what they should do next. If they cannot answer all three, no amount of traffic will help. It costs nothing and it is the most useful user research most businesses will ever do.

Forms

Every additional field costs completions. Name, phone and one free-text box outperforms a nine-field qualification form for first contact — you can qualify on the call. Fields large enough to tap accurately, no CAPTCHA that fails on a slow connection, and the whole thing tested from a real phone before launch and monthly afterwards.

1 in 6 — Sites with a broken form. No complaints, no leads, invisible until tested.

Trust signals

License number, insurance, years in business, review count with a real rating, association memberships, and photographs of actual work. Stock photography of a smiling model actively reduces credibility with buyers who have seen every image in the catalog.

Price transparency

‘Starting at’ outperforms ‘call for pricing’ on every metric we measure, and it pre-qualifies inquiries so you spend less time on people who were never going to buy. If you genuinely cannot publish a number, publish the variables that move it.

Response-time promises

A stated commitment you can actually keep — ‘we answer every call within sixty seconds during business hours’ — is a differentiator worth more than a redesign. Responding to an inquiry within five minutes rather than an hour roughly doubles the contact rate in our own client data.

The technical standard

The technical standard every build meets
Fourteen items, all measurable, all in the scope. Ask any other agency which of these they commit to in writing.

Fourteen items, all measurable, all written into the scope. Ask any other agency which of these they will commit to in writing — the answer separates a build from a template application faster than any portfolio review.

Performance

A performance budget agreed at the start and enforced through the build, rather than an audit at the end that produces a list of regrets. Images as WebP or AVIF at the dimensions actually displayed, explicit width and height on everything, third-party scripts audited before launch, and the LCP element never lazy-loaded.

Accessibility

WCAG 2.2 level AA: meaningful alternative text, 4.5:1 contrast on body text, everything keyboard operable, visible focus states, real form labels, errors announced to assistive technology, logical heading order, and usability at 200% zoom. In the United States this is increasingly a legal exposure rather than a nicety, and it is dramatically cheaper built in than retrofitted.

WCAG 2.2 AA — Accessibility standard. Increasingly a legal exposure, cheaper built in.

Structured data

Implemented per template rather than pasted onto the homepage: Organization and LocalBusiness sitewide, Service on service pages, BreadcrumbList everywhere, FAQPage where there are genuine questions, Article on editorial content, Person on author pages. Validated per template before launch.

Security and maintenance

HTTPS enforced with no mixed content, the CMS and plugins current, backups running with a restore actually tested, and Search Console alerts configured. A hacked site loses rankings and takes weeks to recover, and it is entirely preventable.

Migration: keeping the traffic you already have

The redirect map: the deliverable that decides whether you keep your traffic
The most common way a business loses a year of search visibility is a redesign launched without this document existing. Two to six weeks of volatility is normal even when it is done properly.

If your current site has any search visibility, the redirect map is the most important deliverable in the entire project and it is the one most frequently absent. Losing a year of accumulated ranking on launch day is entirely preventable and it happens constantly, because the damage appears over four to eight weeks — long after anybody associates it with the launch.

301 — The only redirect. 302s do not consolidate signal on a permanent move.

What we export

  • Every URL in the Search Console Pages report, indexed and excluded
  • Every URL in the current XML sitemap
  • Every URL a full crawl of the live site discovers
  • Every landing page from twelve months of analytics, ranked by sessions
  • Every URL with an external backlink pointing at it

What we do not do

  • Redirect everything to the homepage — Google treats that as a soft 404 and the signal is lost
  • Change URLs without a reason
  • Redesign the substance of pages that are already ranking
  • Launch on a Friday
  • Delete the old site before the new one is verified

What happens afterwards

Two to six weeks of ranking volatility is normal even on a clean migration. We watch the Search Console Pages report daily for the first month, because rising 404s and new ‘Duplicate’ statuses are the earliest warning. A dip that has not recovered by week eight is a problem rather than patience, and we treat it as one.

Platforms we build on

Three-year cost of ownership by platform
We build on WordPress or headless, and never on anything you cannot take with you. The last row is not a monthly fee – it is a future rebuild payable to whoever you move to.

WordPress

Our default for most business sites. Fully portable, extensible, and you can host it anywhere. It requires maintenance — core and plugin updates, security monitoring, backups — which is a real ongoing cost and the reason we quote it separately rather than hiding it.

Headless (Next.js with a content API)

For performance-critical sites, complex content models, or businesses with a development capability. Fastest and most flexible, and it needs somebody technical available. We recommend it when it is right and say so when it is not.

Shopify

For ecommerce, unless there is a specific reason not to. Well-supported, well-understood, and the transaction infrastructure is somebody else’s problem — which is worth a great deal.

Squarespace and Webflow

Both perfectly capable for smaller sites, and we will build on either if it fits. Squarespace is the right answer for a business that wants twelve pages it maintains itself with predictable costs. Webflow when design control matters more than extensibility.

What we will not build on

Any proprietary platform the agency owns. If leaving requires a rebuild, that is not a website — it is a subscription with a design attached, and the eventual cost is payable to whoever you move to.

Open CMS — Never proprietary. If you cannot take it with you, do not build on it.
Measured — Not asserted. LCP, CLS, INP, contrast ratios, conversion rate.

How long it takes

How long it takes
Six to ten weeks if content is ready. Twelve to twenty if it has to be written. Add three to five weeks for a second language. Overruns are almost always content and approvals, not development.

Six to ten weeks for a brochure site where content is ready. Twelve to twenty if it has to be written. Add three to five weeks for a second language done properly. Overruns are almost always caused by content and approvals rather than by development, which is why we agree content dates in stage three and chase them.

Week 3-5 — Where projects stall. Content and approvals, not development.

What you can do to make it faster

  1. Name one decision-maker with the authority to approve without a committee.
  2. Gather your content, or agree at the start that we write it.
  3. Book the photography in week one — it takes weeks to arrange and it is worth more than most design premiums.
  4. Provide access on day one: registrar, DNS, hosting, current CMS, analytics, Search Console.
  5. Block four to eight hours a month for approvals, interviews and decisions.
  6. Tell us what you will not do, before somebody plans around it.

What is in the contract

Every term, stated
ItemOur termsWhy it matters
ScopeItemized deliverables plus explicit exclusionsVagueness always resolves in the agency’s favor
Definition of doneWritten, agreed before we startEnds the argument about the final invoice
RevisionsFixed count per stage, statedPrevents both scope creep and corner-cutting
TemplatesCounted and namedA ten-page site with nine templates is a different job
ContentWho writes it and who approves it, with datesThe leading cause of overrun
Redirect mapProduced before development startsDecides whether you keep your rankings
CMSOpen-source and self-hostableYou can leave whenever you want
Domain, hosting, DNSIn your nameNo hostage situations
Source filesTransfer on final paymentYou paid for them
AccessibilityWCAG 2.2 AAStated as a standard, not as an aspiration
PerformanceNumeric targets: LCP, CLS, INP‘Fast’ is not a specification
Browser supportNamed matrixSo nobody argues about it later
Post-launch30 days includedLaunch week is when things surface
TrainingRecordedSurvives the person who attended leaving
PaymentMilestones tied to deliverablesNot to calendar dates
OffboardingWritten process with a timelineAgreed before you need it
Yours — Domain and hosting. Registered in your name, logins in your possession.
Handover — In writing. Accounts, files, credentials and an offboarding process.

What we build for different businesses

Local service businesses

A page per service, a page per area you genuinely serve, problem-diagnosis content, a price list or service list as indexed HTML, and a conversion path that assumes the visitor is on a phone in a driveway. Trust signals above the fold, license numbers visible, and a form that works.

Professional services

Practice-area pages with genuine depth, individual professional pages with verifiable credentials — which rank strongly for name searches and convert far above average — and procedural content answering the questions nobody else answers. Compliance review where the profession requires it.

Healthcare and dental

Procedure pages written to answer patient anxiety rather than to describe technique, insurance acceptance pages, provider bios, and a tracking configuration that respects HIPAA constraints on pages containing protected health information.

Restaurants and hospitality

The menu as real indexed HTML rather than a PDF — this alone unlocks search demand for specific dishes combined with a neighborhood name — plus hours that are actually correct, a phone number that dials in one tap, real photographs of the actual food, and a deliberate decision about third-party ordering.

Ecommerce

Category pages as the money pages with real buying guidance below the grid, unique product descriptions rather than manufacturer copy, faceted navigation handled deliberately so it does not generate forty thousand crawlable variants, and product schema kept in sync.

B2B and industrial

Capability pages with genuine specification detail, certifications, tolerances, materials and lead times. B2B buyers search extremely specific technical language that consumer-oriented sites never use, and the competition for those terms is frequently negligible.

Nonprofits

Program and eligibility pages, application processes, event listings with proper structured data, and content in every language the community actually speaks. Also help claiming Google Ad Grants, which provides substantial free search advertising and is widely unclaimed.

Responsive design, tested properly

Not ‘it works on mobile’ — tested at four breakpoints on real devices, on a throttled connection, with the things people actually do. Tap targets large enough to hit accurately. No horizontal scrolling anywhere. Tables that scroll inside their own container rather than pushing the page sideways. Text readable without pinching. An address that opens the map app in one tap.

Information architecture

The sitemap is a commercial document, not an organizational chart. It is derived from what people search and what they need to decide, which is frequently not how the business thinks about itself. One page per intent, three clicks maximum from the homepage to any commercial page, and breadcrumbs with markup on every page.

Copywriting

Written by somebody who interviewed you, not assembled from the pages already ranking. The pages that win contain information nobody else has: what a job actually involves, what it costs, what goes wrong, what you do differently and why. That requires access to your people, which is why we book it in advance rather than hoping for it.

Photography and imagery

Real photographs of your work, your premises and your people. We art-direct and we can arrange the shoot. Budget $1,200 to $4,000 for a day plus retouching and usage rights, and expect it to outperform an equivalent spend on design. Shoot vertically as well as horizontally, because most of your audience is holding a phone.

Forms and lead capture

Three fields, real labels, errors announced to assistive technology, spam handled without a CAPTCHA that fails on a slow connection, and delivery confirmed by email and stored in a database so a mail failure does not silently lose inquiries. Tested from a real phone before launch and monthly afterwards.

Analytics and conversion tracking

Google Analytics 4 configured with conversion events that correspond to real business events rather than page views. Call tracking with a duration threshold. Deduplication so one person who calls and submits does not count twice. Search Console verified. Where a CRM exists, connected, so reporting can show revenue rather than leads.

Structured data and AI visibility

Schema per template, question-shaped headings with the answer within sixty words underneath, comparative information in real HTML tables, specific committed numbers rather than ‘competitive pricing’, a visible last-updated date in the body, an llms.txt file at the root, and AI crawlers deliberately allowed in robots.txt unless you decide otherwise. Covered further in GEO vs SEO.

Multilingual builds

Separate URLs per language with correct hreflang annotations, native-quality writing across the whole conversion path rather than a translated homepage leading to English service pages, and somebody who can answer the phone in that language. Roughly a fifty per cent premium over a single-language build, and in the right market it is the highest-return line item in the quote.

Ecommerce specifics

Category pages treated as the primary landing pages, faceted navigation canonicalised or blocked before it generates tens of thousands of crawlable variants, unique product content rather than manufacturer copy, product schema with accurate price and availability, and out-of-stock handling that keeps the URL and offers alternatives rather than 404ing a page with links and rankings.

Booking and scheduling

If your business books appointments, integrated booking removes the largest single point of friction between interest and commitment. We prefer an integration you control over a third party that owns the customer relationship, and we test it on a phone before launch because that is where it will be used.

Integrations

CRM, payment, booking, inventory, membership, ERP. Each is a project inside the project and each is where fixed-price quotes go wrong, because integrations behave differently from their documentation. We name them individually in the scope with an allowance against each rather than absorbing them into a single number.

Hosting

In your name, at a provider you can log into. We will recommend one and set it up, and you can move whenever you like. Server response time floors every other performance metric, so this is not the place to economize — the $300 a year saved on cheap shared hosting is spent several times over on developer callouts and lost inquiries.

Maintenance

Core and plugin updates, security monitoring, backups with a restore actually tested, uptime monitoring, and a small allowance of content edits. $50 to $250 a month for a small site. Optional, and you can do it yourself or use anybody — we will document what needs doing either way. More detail on website maintenance.

Training and handover

Recorded, so it survives the person who attended leaving. Written documentation of where everything lives, which accounts control what, and how to do the six things you will actually need to do. Plus a written offboarding process agreed at the start, in case you ever want to work with somebody else.

Ownership

You own the domain, the hosting, the CMS, the content, the design files and the source. All of it transfers on final payment and none of it is contingent on continuing to work with us. This is the clause that traps more businesses than any other and it is free to get right at the start.

What we will tell you not to do

  1. Rebuild a site that already converts and merely looks dated.
  2. Publish your menu, price list or service list as a PDF.
  3. Build on a platform you cannot take with you.
  4. Launch without a redirect map.
  5. Spend on design before fixing a form that does not work.
  6. Add a chat widget that costs you a second of load time for a handful of conversations.
  7. Buy stock photography when your own work photographs better.
  8. Build forty pages before validating that four of them index.
  9. Pay for a rebuild when instrumenting the current site would answer the question for free.

How we quote

After a conversation about what the site must produce, never before. We will ask for your close rate, your average customer value and your capacity, because without those we cannot tell whether the project makes sense for you — and if it does not, we would rather say so in the first meeting than in month four.

How we work with your existing agency

Frequently and without friction. If you have an SEO or paid media agency you are happy with, we build to their specification and hand over cleanly. We will ask them for the keyword map, the redirect requirements and the tracking spec before we design anything, which is the sequence that avoids the usual argument three weeks after launch.

What happens after launch

Thirty days of support included, because launch week is when things surface. Indexing confirmed, Core Web Vitals measured from field data rather than a lab score, forms re-tested, the Pages report watched daily for the first month, and a check-in at week eight to confirm any migration volatility has resolved.

Who we work with

Businesses that want a site that produces inquiries rather than one that wins awards, and that are prepared to give four to eight hours a month to approvals and interviews during the build. We are a poor fit for organizations that need design by committee, and we will say so early rather than discovering it in month three.

Who we are not right for

  1. If you want the cheapest possible site, a template you set up yourself will genuinely serve you better.
  2. If you need a rebuild in three weeks, we cannot do it properly in three weeks and we will not pretend to.
  3. If approval requires six people to agree, the project will cost more and take longer than either of us wants.
  4. If you are not prepared to be interviewed, the content will be generic and it will not rank.
  5. If your constraint is capacity rather than demand, more inquiries are not a benefit and you should spend the money elsewhere.
4 sec — Comprehension window. What you do, where, and what to do next.
2.5s — Mobile LCP target. Measured on field data, not a Lighthouse score.
3 fields — Form length. Name, phone and one free-text box beats nine fields.
Templates — Not pages. Count templates when comparing quotes.

Frequently misunderstood things about web design

A redesign does not improve rankings by itself

Unless search was designed into it. The same thin content, the same missing internal links and no keyword-led architecture will rank the same or worse, and a launch without a redirect map will rank substantially worse. Design is close to neutral; structure and content are not.

Word count is not the goal, coverage is

Longer pages correlate with better rankings because thorough pages answer more of what a searcher needs. Adding words without adding coverage produces a longer page that ranks the same. List the questions a visitor has, answer them all, and count the words afterwards as a diagnostic.

Templates are not bad for SEO

Templates are neutral. What harms performance is the absence of a keyword-led architecture, thin service pages, no internal linking and a broken migration — all of which happen just as easily on a custom build.

Nobody reads your homepage

Most visitors arrive on an interior page from a search result. The homepage matters for brand searches and for orientation; the pages that produce inquiries are almost always service and location pages. Budget accordingly.

Fast is a specification, not an adjective

‘Optimized for speed’ means nothing. Mobile LCP under 2.5 seconds on field data means something, and it can be measured by anybody, which is why we put it in the contract.

Browser and device support matrix

Named in the contract, so nobody argues about it after launch. We test against the current and previous major version of each, on real devices rather than in an emulator.

What we test, and to what standard
EnvironmentSupport levelNotes
Chrome, current and previousFullDesktop and Android
Safari, current and previousFullmacOS and iOS. iOS Safari behaves differently and is tested separately
Firefox, current and previousFullDesktop
Edge, current and previousFullChromium-based
Samsung Internet, currentFullSignificant share on Android in several markets
iPhone SE through Pro MaxFullSmallest and largest current viewports
Android, 360px to 430px wideFullWhere most local search actually happens
Tablet, portrait and landscapeFullBoth orientations
Screen readers: VoiceOver and NVDAFullKeyboard navigation and announced errors
Internet ExplorerNoneDiscontinued. Supporting it costs more than the traffic is worth
Throttled Slow 4GPerformance testedThe condition your visitors are actually in
200% browser zoomFullA WCAG 2.2 AA requirement, and commonly broken

What is included at each price point

The differences between tiers are structural rather than cosmetic — every tier gets the same technical standard, the same ownership terms and the same accessibility commitment. What changes is scope.

Tier comparison
IncludedRestyle $4,800Brochure $9,500Business $18,000Content program $36,000
Discovery and unit economicsLightYesYesYes
Search-led sitemapNo — existing keptYesYesYes
Unique templatesRestyle of existing2–34–66–9
PagesExisting5–810–1630–60
CopywritingExisting keptYesYesYes
Photography directionOptionalOptionalYesYes
Structured data per templateYesYesYesYes
Redirect mapNot neededYesYesYes
WCAG 2.2 AAYesYesYesYes
Numeric performance targetsYesYesYesYes
Analytics and conversion trackingYesYesYesYes
Internal linking programNoLightYesYes
Second languageNoAdd $9,000Add $11,000Add $14,000
Recorded trainingYesYesYesYes
Post-launch support14 days30 days30 days60 days
Source files on final paymentYesYesYesYes

Note the rows that are identical across every tier. The technical standard, the accessibility commitment, the performance targets and the ownership terms do not vary with price, because they are not features — they are the minimum conditions for the thing to work.

$4,800 — Restyle in place. When the site works and merely looks dated.
30 days — Post-launch support. Included, because launch week is when things surface.
Support — Thirty days. Because launch week is when things surface.
Training — Recorded. So it survives the person who attended leaving.
Photography — Real. Stock actively reduces trust with buyers who have seen it all.
Cheap build over three years
The cheap one needs replacing

Three from Google Search Central that bear directly on the material above.

Do you still need a website in 2026? — Google Search Central. Worth settling before commissioning a build.
Are websites getting fat? Page weight and Googlebot limits — Google Search Central. A real constraint on modern builds.
How browsers really parse HTML and what that means for SEO — Google Search Central. Why build quality affects visibility.

Want an honest opinion before you spend anything?

Send us your URL. We will test your contact form from a real phone, check how many of your pages are indexed, measure your mobile performance on a throttled connection, look at whether your structure can rank at all, and tell you whether you need a rebuild, a restyle, or four fixes. Free, written up, no obligation — and if the answer is four fixes, we will say so and quote for those instead.

Get a free website review

Every guide we publish, grouped by what you are trying to do.

The nine stages, as cards

Answer first: the sequence below is the order the work has to happen in, because each stage consumes the output of the one before it. Skipping ahead to design is the single most common cause of a project that overruns and then underperforms.

1 — Discovery before design. Unit economics, close rate, capacity and seasonality first..
2 — Sitemap from search demand. One page per intent, agreed before anybody designs..
3 — Content plan with dates. Who writes each page, who approves it, by when..
4 — Templates, not pages. Count templates when comparing quotes..
5 — Redirect map before development. Every indexed URL mapped and tested on staging..
6 — A numeric build standard. LCP, CLS, WCAG level, structured data per template..

The launch-day checks that actually catch problems

Answer first: six checks, run within the hour of launch, catch nearly every launch failure we have seen. The fourth — removing the staging noindex — is the one that most often goes unnoticed for weeks and costs the most.

A — Forms tested from a phone. Before launch and monthly afterwards..
B — Analytics verified live. Not assumed to be working because it was installed..
C — Search Console connected. Sitemap submitted, coverage watched for a fortnight..
D — noindex removed. The single most common launch-day failure..
E — 404 crawl run. Before anybody announces the launch..
F — Top fifty URLs checked by hand. Automated checks miss visual breakage..

What you should own at the end

Answer first: everything. Domain, hosting, CMS admin, analytics, design files and code, all in your business’s name with the agency holding access rather than ownership. This costs nothing to arrange at the start and is expensive to unwind later.

The domain — Own. Registered in your business name, always..
The hosting account — Own. In your name, with the agency as a user..
The CMS admin — Own. An owner account you control..
The analytics property — Own. Yours, not the agency's..
The design files — Own. Handed over at the end, in an open format..
The code — Own. In a repository you can access after the engagement..
Ownership: what to confirm before signing
AssetShould be registered toWhat goes wrong otherwise
Domain nameYour businessYou cannot move host or agency without permission
Hosting accountYour businessYou cannot take a backup or migrate
CMS administrator accountA named person at your businessYou cannot grant or revoke access
Analytics propertyYour businessYour historical data leaves with the agency
Design filesDelivered to you in an open formatFuture work restarts from screenshots
Code repositoryAccessible to youNobody else can maintain the site
Third-party licensesYour businessRenewals lapse silently

Every row in the right-hand column is something we have seen happen. None of it is malicious in most cases; it is what results from nobody asking the question at the start.

What we cut from most briefs

Answer first: the six items below appear in a majority of briefs, cost real load time, and produce close to nothing. Removing them is usually the cheapest performance improvement available on a redesign.

Carousels nobody scrolls — Cut. They cost load time and produce almost no clicks..
Stock photography of people — Cut. It reads as a placeholder that stayed..
Splash animations — Cut. They delay the first useful frame..
Pop-ups on first paint — Cut. They are penalized and they annoy..
Auto-playing video with sound — Cut. Nobody has ever wanted this..
Twelve-field contact forms — Cut. Every field costs completed inquiries..

Repair or rebuild?

Answer first: repair when the site is indexed, ranking and structurally sound but looks dated. Rebuild when the URL structure, the CMS or the editability is the problem. A restyle costs a fraction of a rebuild and carries none of the ranking risk.

Repair — The site is indexed and ranking. A restyle carries no ranking risk..
Repair — The structure works. Only the styling has aged..
Repair — The CMS is current. No security or upgrade pressure..
Rebuild — URLs are unsalvageable. Structure prevents ranking at all..
Rebuild — The CMS is unsupported. Security is the deciding factor..
Rebuild — The site cannot be edited. Ongoing cost outweighs the build..
Repair or rebuild: the deciding factors
SymptomRepairRebuildWhy
Looks dated, ranks wellYesNoStyling is separable from structure
Slow on mobileUsuallySometimesOften images and scripts rather than the build
Cannot be edited without a developerNoYesThe ongoing cost outweighs the build
URL structure prevents rankingNoYesStructure is not restylable
CMS no longer supportedNoYesSecurity decides it
Fails accessibilitySometimesSometimesDepends whether it is markup or structure
Needs new functionalitySometimesSometimesDepends whether the platform supports it

Read the middle two columns together: only three of the seven rows point unambiguously at a rebuild, and two of those are about maintenance rather than appearance. We would rather quote a restyle for the right work than a rebuild for the wrong work.

Questions to ask any web design supplier

Answer first: six questions, and the one that reveals most is what the scope excludes. Any supplier can list what is included; only one with a real process can tell you what is not.

How many templates? — Ask. Not how many pages..
Who writes the content? — Ask. And is it priced?.
What is excluded? — Ask. The most revealing question in any scope..
What is the redirect plan? — Ask. It should exist before development..
What standard do you build to? — Ask. Numbers, not adjectives..
What happens after launch? — Ask. Support terms, in the same document..

Web design for general contractors

Construction and trades sites fail in a consistent and fixable way, which is worth setting out separately because the buyer behaves differently from a typical service client.

What general contractor web design has to get right

A general contractor web design has three jobs: prove the work with real project photography, make the service area unambiguous, and put the phone number where a thumb finds it. Homeowners comparing contractors decide on evidence and reachability, and most trade sites lead with a stock photo and bury the number in a footer.

Why the standard template underperforms

Web design for general contractors is frequently sold as a template with a gallery bolted on. The gallery is the site — before-and-after sequences from jobs you actually did, with the town named — and treating it as a subpage rather than the main event is the single most common structural error in the category.

License, insurance and service area

These are not fine print for this buyer. Stating the license number, the insurance position and the exact towns served removes the three questions that otherwise become a phone call, and their absence reads as evasion whether or not it is.

Frequently asked questions

How much does a website cost?
Our fixed-scope pricing starts at $1,400 for a landing page, $9,500 for a five to eight page brochure site, $18,000 for a ten to sixteen page business site, and $34,000 for ecommerce under 200 SKUs. A restyle in place, when your site works and merely looks dated, is $4,800. Full market context is on how much does a website cost.
How long does a website take to build?
Six to ten weeks for a brochure site where content is ready, twelve to twenty weeks if content must be written, and twenty to thirty-two for ecommerce with integrations. Add three to five weeks for a second language. Overruns are almost always caused by content and approvals rather than by development.
Do I need a new website, or can the current one be fixed?
Frequently it can be fixed. If your site converts acceptably, is fast, indexed and ranking, and merely looks dated, a restyle in place costs a fraction and risks nothing. Rebuild when the CMS is unsupported, when you need to grow from twelve pages to fifty, or when you are on a platform you cannot leave.
Will a new website improve my Google rankings?
Only if search was designed into it. A redesign with the same thin content, the same missing internal links and no keyword-led architecture will rank the same or worse, and one launched without a redirect map will rank substantially worse. See what is SEO.
What is a redirect map and why does it matter?
A document mapping every existing indexed URL to a specific new URL, implemented as 301 redirects and tested on staging before launch. Without it, old URLs 404, backlinks stop passing value, and rankings for pages that were working disappear over four to eight weeks. We produce it before development starts.
Which platform do you build on?
WordPress by default, because it is fully portable and extensible. Headless with Next.js for performance-critical or complex builds. Shopify for ecommerce. Squarespace or Webflow where they genuinely fit. Never a proprietary platform you cannot take with you. See Squarespace vs WordPress.
Who owns the website when it is finished?
You. The domain, the hosting, the CMS, the content, the design files and the source, all transferring on final payment and none of it contingent on continuing to work with us. This is the clause that traps more businesses than any other and it is free to get right at the start.
Do you write the content?
We can, and we usually should. Writing twelve pages properly is thirty to sixty hours, and ‘client supplies content’ in a quote does not make the content free — it moves the cost into your diary and it is the leading cause of website projects launching late. Either way we need to interview your people.
What about accessibility?
Every build meets WCAG 2.2 level AA: meaningful alternative text, 4.5:1 contrast on body text, full keyboard operability, visible focus states, real form labels, errors announced to assistive technology, and usability at 200% zoom. In the US this is increasingly a legal exposure, and it is far cheaper built in than retrofitted.
How fast will the site be?
We commit to numbers rather than adjectives: mobile Largest Contentful Paint under 2.5 seconds measured on field data, Cumulative Layout Shift under 0.1, and Interaction to Next Paint under 200 milliseconds. Performance is budgeted from the start rather than audited at the end.
Do you do ecommerce?
Yes — Shopify or WooCommerce, from $34,000 for under 200 SKUs and from $78,000 with ERP, PIM or fulfillment integrations. Category pages are treated as the primary landing pages, faceted navigation is handled deliberately, and product data is the real cost driver rather than design. See ecommerce website design.
Can you build the site in more than one language?
Yes. Separate URLs per language with correct hreflang, native-quality writing across the whole conversion path rather than a translated homepage, and a language switcher that works on every page. Roughly a fifty per cent premium over a single-language build, and in the right market it is the highest-return item in the quote.
Do you host the site?
We will set up hosting in your name at a provider you can log into, and you can move it whenever you like. We do not lock hosting to the engagement. Server response time floors every other performance metric, so we will steer you away from the cheapest shared plans.
What happens after launch?
Thirty days of support included. Indexing confirmed, Core Web Vitals measured from field data, forms re-tested, the Search Console Pages report watched daily for the first month, and a check-in at week eight to confirm that any migration volatility has resolved.
Do I need ongoing maintenance?
On WordPress and anything self-hosted, yes: updates, security monitoring, backups with a tested restore, uptime monitoring. $50–$250 a month for a small site. It is optional with us and you can use anybody — we will document what needs doing either way. See website maintenance.
How many pages should my site have?
One per service you want inquiries for, one per genuine sub-service, one per location you can write distinctly about, plus cost guides, problem-diagnosis pages and an about page with real people. For a typical service business that is twenty-five to eighty pages built over a year.
Can you work with our existing SEO or marketing agency?
Frequently and without friction. We ask them for the keyword map, the redirect requirements and the tracking specification before we design anything, which is the sequence that avoids the usual argument three weeks after launch.
What is in the contract?
Itemized deliverables and explicit exclusions, a written definition of done, a fixed revision count, templates counted and named, who writes and approves content with dates, the redirect map, the CMS, ownership of domain and hosting, source file transfer, the accessibility standard, numeric performance targets, a browser matrix, thirty days of support, recorded training, milestone payments and a written offboarding process.
Why do you tell people not to rebuild?
Because rebuilding a site that already converts is the most expensive mistake in this category. It costs several times what a restyle costs and it risks rankings a restyle does not touch. We would rather quote you $4,800 for the right work than $18,000 for the wrong work and lose the relationship in month six.
How do I get started?
Send us your URL. We will review it properly and free — the form, the indexing, the mobile performance, whether the structure can rank — and tell you what we think you actually need. If that is not a website project, we will say so. Contact us.
How long does a website project take?
A template configuration runs two to four weeks; a designed build on a flexible framework runs six to twelve; a custom build with integrations runs three months and up. The variable that moves the date most is content, not design.
Who writes the content?
Whoever is named in the contract. Projects stall on content more than on any other cause, and the assumption that the client will supply it is where most timelines break.
What does a website cost?
The drivers are the number of unique page templates, whether content is written or supplied, whether the site integrates with anything, and how much of the work is original design rather than configuration.
Do we own the site at the end?
You should. The domain, the hosting account, the code and the content should all sit in accounts you control, and that belongs in the contract rather than in an assumption.
What happens after launch?
Updates, backups, monitoring, security and small changes. A build without a maintenance arrangement is a site that degrades from the day it ships.
Will the new site keep our rankings?
Only if every URL that has a ranking or an inbound link is mapped to its closest equivalent with a permanent redirect. That map is the single most important artefact in any redesign.
WordPress, Shopify or Squarespace?
Shopify if selling products is the primary activity. Squarespace if the site is small and will be self-managed. WordPress if the content model is complex or the site needs to do something the others cannot.
How many revision rounds are included?
Two is standard. What matters more is that a round is defined — consolidated feedback from one decision maker, not a stream of individual comments.
Do we need a designer and a developer?
On anything custom, yes, and the handoff between them is where quality is lost. A single supplier covering both removes that risk and narrows the field.
What is a staging environment?
A copy of the site where changes are made and tested before going live. Any arrangement that edits the live site directly will eventually break it in public.
How do we handle accessibility?
Decide the conformance target at the start, because retrofitting is far more expensive than building to it. WCAG is the standard courts and settlements reference.
What about hosting?
Buy it in your own name. Bundled hosting is convenient and is the most common form of supplier lock-in.
How is the project managed?
A named point of contact, a written scope, a change process, and a schedule with dependencies rather than a list of activities.
What if we need changes after launch?
Either a monthly allowance in a retainer or an hourly rate agreed in advance. Discovering the rate when you need the change is the worst time to negotiate it.
Do you build in a page builder?
Ask, because it decides who can edit the site afterwards and how heavy the pages are. Builders trade editing convenience for performance and portability.
How do we measure whether it worked?
Agree the definitions before launch — what counts as a lead, which pages matter, what the baseline is. A site launched without a baseline cannot be judged.
What content management training is included?
Enough that someone internal can make routine changes without calling. A handover without training produces a site that is never updated.
How long should a website last?
Five to seven years for the design, indefinitely for the content and structure if maintained. Sites are usually replaced because they were neglected rather than because they aged.

Web design questions, answered straight

How fast can you actually build my website?

Two days for most small business sites, once we have your content and you are responsive to questions. The two-to-four-week timeline the industry quotes is mostly queue time and slow approval loops, not build time. The genuine constraint is usually how quickly you can supply copy, images and feedback — if that side moves fast, so do we.

What gets cut if a site is built in 48 hours?

Nothing that matters, and it is a fair question to ask. What is skipped is the waiting: the discovery theatre, the sequential approval rounds, the internal handoffs. What is not skipped is responsive layout, page speed, on-page SEO structure, tracking, forms that work, and accessible markup. If a fast build ever meant skipping those, it would not be worth the speed.

Can I do the website myself with Squarespace or Wix?

Yes, and for a simple brochure site with a small budget that is often the sensible answer. The DIY builders fall down when you need custom functionality, serious page speed, complex SEO structure, or integrations. The honest test: if your site is five pages and a contact form, build it yourself. If it is meant to generate leads at volume, the difference starts to pay.

WordPress or Squarespace — which should I choose?

Squarespace for simplicity and low maintenance, WordPress for flexibility, SEO control and anything you might want to extend later. WordPress asks more of you in upkeep, which is why maintenance plans exist. Neither is universally better; the deciding factor is whether you will need the site to do things you have not thought of yet.

Do you handle SEO after the site launches?

Yes, and building the site with that in mind is most of the value — correct heading structure, fast loading, clean URLs, and schema built in from day one rather than retrofitted. A beautiful site with no search foundation is a very expensive brochure.

Who owns the website when it is done?

You do — the domain, the hosting account, the files, all of it. We build on infrastructure registered to you. Sites held hostage on an agency's hosting is a common and genuinely awful practice, and the way to avoid it is to insist on ownership before the build starts.

What does a small business website cost?

It spans an enormous range depending on page count, custom functionality and whether content is written for you. We publish a guide to what the market actually charges, and we quote your specific scope in writing the same business day rather than making pricing a mystery you have to book a call to solve.

Will my site work properly on phones?

Yes, and it is not optional — most small business traffic is mobile, and Google evaluates the mobile version. Every build is checked on real phone widths, not just a desktop browser resized.

Do I need to redesign or just fix what I have?

If the structure is sound and it is dated, styling and speed work is far cheaper than a rebuild. If the site is slow at its foundations, built on an abandoned theme, or structured in a way search engines cannot read, patching is throwing money at a problem that returns. An honest audit answers this in an afternoon.

What do you need from me to start?

Your service list, any existing copy and images, access to the domain, and a decision-maker who can answer questions quickly. That last one is genuinely the biggest variable in how fast a site ships.

Do you write the content, or do I?

Either. Sites move fastest when you supply the raw substance — what you do, who for, what makes you different — and we shape it. Fully written-for-you content is available and adds time, mostly for interviewing you properly.

What happens after launch — do I need a maintenance plan?

WordPress sites need updates, backups and security monitoring, or they eventually break or get compromised. You can do it yourself if you are technical and disciplined. If you are not, a maintenance plan is cheap insurance against the version of this problem where the site is down and nobody has a backup.

The short answerWeb design and development covers two different jobs that are usually sold together: deciding what the site should be and how it should look, and building it so it works and can be maintained. Most project failures happen at the seam between them, not inside either one.

What is the difference between web design and web development?

Design decides what exists and how it looks and behaves. Development builds it. The seam between them is where projects go wrong — designs that cannot be built as drawn, and builds that quietly simplify the design without telling anyone.

The practical consequence is that you should care whether the two are done by people who talk to each other. A design handed over a wall to a developer produces either an expensive argument or a silent compromise, and you find out which at launch.

What should a web design and development project include?

Discovery, information architecture, template design, build, content, testing and handover. Content and handover are the two that get cut, and they are the two that determine whether the site is still good in two years.

Discovery

What the site is for and what it must do. Short, but skipping it is the most expensive saving available.

Information architecture

What pages exist and how they relate. Usually the highest-value workstream and the least visible.

Template design

Design templates, not pages. A site designed page-by-page cannot be extended by anyone but its designer.

Build

Including a staging environment. Without one, your customers do the testing.

Content

The usual critical path. Budget for writing, not just for placing.

Testing

Real devices, real connections, and the forms actually submitting to the right inbox.

Handover

Documentation, access, and a named person. Get it in the contract.

How do you choose between a page builder, a CMS and a custom build?

Match the tool to who will maintain it. If your team will edit the site weekly, choose something they can edit. If the site is mostly static and the requirements are unusual, a custom build is cheaper to run than it looks.

The common mistake is choosing the most capable tool rather than the most appropriate one. A heavily customised builder site that only its agency can change is worse for most businesses than a simpler build they control.

What should you agree before the project starts?

Who owns the code and the accounts, what happens to the site after launch, how many rounds of revision are included, and what counts as done. Ambiguity on those four causes most of the disputes in this category.

Choosing the build approach

IfChooseBecause
Your team edits weeklyCMS or builder they knowMaintenance is the recurring cost
The site is mostly staticSimpler buildLess to break and cheaper to host
Requirements are unusualCustomConfiguring around a platform costs more than building
You sell productsEstablished ecommerce platformPayments and tax are solved problems
You need an applicationCustomBusiness logic is not a content problem
Budget is tightFewer templates, done wellTemplate count drives cost more than page count

Frequently asked questions

What is the difference between web design and web development?

Design decides what exists and how it looks and behaves; development builds it. Most project problems occur at the seam between the two.

How much does web design and development cost?

Template count and integration count drive cost far more than page count. Twelve pages on three templates is cheaper than six pages on six.

How long does a website project take?

Six to twelve weeks for a standard business site. Content is usually the critical path.

Should I use WordPress, Webflow, Squarespace or a custom build?

Choose by who maintains it. The best platform is the one your team can actually edit without calling an agency.

Who owns the website when it is finished?

You should — code, hosting, domain, analytics and source files. Put it in the contract rather than asking at handover.

Do I need a staging site?

Yes. Without one, testing happens in public and update failures are visible to customers.

What is information architecture?

What pages exist and how they relate. It is usually the highest-value part of the project and the least visible in a pitch.

Why do website projects overrun?

Content, almost always. Design moves fast once agreed; writing forty pages does not.

How many revision rounds should be included?

Agree a number before starting. Unlimited revisions sound generous and produce projects that never finish.

Should design and development be the same team?

Not necessarily, but they must talk. A design handed over a wall produces either an argument or a silent compromise.

What happens after launch?

Someone has to maintain it. Agree that before launch rather than discovering it when a plugin update breaks something.

How do I know the project is done?

Define it up front: templates built, content in, forms tested to the right inbox, analytics firing, and handover delivered.

Related

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Contact Us