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
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
What you get
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.
What it costs
| Build type | Price from | Typical timeline | What it includes |
|---|---|---|---|
| Restyle in place | $4,800 | 3–5 weeks | New type, color and imagery on your existing structure. No ranking risk. |
| Single landing page | $1,400 | 1–2 weeks | One template, copy, form, tracking |
| Brochure site, 5–8 pages | $9,500 | 6–8 weeks | 2–3 templates, content plan, structured data, redirect map |
| Business site, 10–16 pages | $18,000 | 8–13 weeks | 4–6 templates, service pages, full technical standard |
| Site plus content program | $36,000 | 14–20 weeks | 30–60 pages, internal linking, keyword-led architecture |
| Bilingual site, 12–20 pages | $26,000 | 12–18 weeks | Two languages written natively, correct hreflang |
| Ecommerce, under 200 SKUs | $34,000 | 12–18 weeks | Catalog, checkout, product schema, analytics |
| Ecommerce with integrations | $78,000 | 20–32 weeks | ERP, PIM or fulfillment integration, data migration |
| Accessibility remediation | $4,000 | 3–6 weeks | Existing 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 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.
When you should not rebuild
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 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
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.
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.
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
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.
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
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.
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
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.
How long it takes
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.
What you can do to make it faster
- Name one decision-maker with the authority to approve without a committee.
- Gather your content, or agree at the start that we write it.
- Book the photography in week one — it takes weeks to arrange and it is worth more than most design premiums.
- Provide access on day one: registrar, DNS, hosting, current CMS, analytics, Search Console.
- Block four to eight hours a month for approvals, interviews and decisions.
- Tell us what you will not do, before somebody plans around it.
What is in the contract
| Item | Our terms | Why it matters |
|---|---|---|
| Scope | Itemized deliverables plus explicit exclusions | Vagueness always resolves in the agency’s favor |
| Definition of done | Written, agreed before we start | Ends the argument about the final invoice |
| Revisions | Fixed count per stage, stated | Prevents both scope creep and corner-cutting |
| Templates | Counted and named | A ten-page site with nine templates is a different job |
| Content | Who writes it and who approves it, with dates | The leading cause of overrun |
| Redirect map | Produced before development starts | Decides whether you keep your rankings |
| CMS | Open-source and self-hostable | You can leave whenever you want |
| Domain, hosting, DNS | In your name | No hostage situations |
| Source files | Transfer on final payment | You paid for them |
| Accessibility | WCAG 2.2 AA | Stated as a standard, not as an aspiration |
| Performance | Numeric targets: LCP, CLS, INP | ‘Fast’ is not a specification |
| Browser support | Named matrix | So nobody argues about it later |
| Post-launch | 30 days included | Launch week is when things surface |
| Training | Recorded | Survives the person who attended leaving |
| Payment | Milestones tied to deliverables | Not to calendar dates |
| Offboarding | Written process with a timeline | Agreed before you need it |
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
- Rebuild a site that already converts and merely looks dated.
- Publish your menu, price list or service list as a PDF.
- Build on a platform you cannot take with you.
- Launch without a redirect map.
- Spend on design before fixing a form that does not work.
- Add a chat widget that costs you a second of load time for a handful of conversations.
- Buy stock photography when your own work photographs better.
- Build forty pages before validating that four of them index.
- 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
- If you want the cheapest possible site, a template you set up yourself will genuinely serve you better.
- If you need a rebuild in three weeks, we cannot do it properly in three weeks and we will not pretend to.
- If approval requires six people to agree, the project will cost more and take longer than either of us wants.
- If you are not prepared to be interviewed, the content will be generic and it will not rank.
- If your constraint is capacity rather than demand, more inquiries are not a benefit and you should spend the money elsewhere.
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.
| Environment | Support level | Notes |
|---|---|---|
| Chrome, current and previous | Full | Desktop and Android |
| Safari, current and previous | Full | macOS and iOS. iOS Safari behaves differently and is tested separately |
| Firefox, current and previous | Full | Desktop |
| Edge, current and previous | Full | Chromium-based |
| Samsung Internet, current | Full | Significant share on Android in several markets |
| iPhone SE through Pro Max | Full | Smallest and largest current viewports |
| Android, 360px to 430px wide | Full | Where most local search actually happens |
| Tablet, portrait and landscape | Full | Both orientations |
| Screen readers: VoiceOver and NVDA | Full | Keyboard navigation and announced errors |
| Internet Explorer | None | Discontinued. Supporting it costs more than the traffic is worth |
| Throttled Slow 4G | Performance tested | The condition your visitors are actually in |
| 200% browser zoom | Full | A 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.
| Included | Restyle $4,800 | Brochure $9,500 | Business $18,000 | Content program $36,000 |
|---|---|---|---|---|
| Discovery and unit economics | Light | Yes | Yes | Yes |
| Search-led sitemap | No — existing kept | Yes | Yes | Yes |
| Unique templates | Restyle of existing | 2–3 | 4–6 | 6–9 |
| Pages | Existing | 5–8 | 10–16 | 30–60 |
| Copywriting | Existing kept | Yes | Yes | Yes |
| Photography direction | Optional | Optional | Yes | Yes |
| Structured data per template | Yes | Yes | Yes | Yes |
| Redirect map | Not needed | Yes | Yes | Yes |
| WCAG 2.2 AA | Yes | Yes | Yes | Yes |
| Numeric performance targets | Yes | Yes | Yes | Yes |
| Analytics and conversion tracking | Yes | Yes | Yes | Yes |
| Internal linking program | No | Light | Yes | Yes |
| Second language | No | Add $9,000 | Add $11,000 | Add $14,000 |
| Recorded training | Yes | Yes | Yes | Yes |
| Post-launch support | 14 days | 30 days | 30 days | 60 days |
| Source files on final payment | Yes | Yes | Yes | Yes |
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.
Watch: build quality and search
Three from Google Search Central that bear directly on the material above.
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.
Every guide we publish, grouped by what you are trying to do.
Getting found in search
AI, AEO and what is changing
Paid media and lead generation
Websites and design
Choosing and working with an agency
Social, content and brand
By industry and by situation
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.
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.
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.
| Asset | Should be registered to | What goes wrong otherwise |
|---|---|---|
| Domain name | Your business | You cannot move host or agency without permission |
| Hosting account | Your business | You cannot take a backup or migrate |
| CMS administrator account | A named person at your business | You cannot grant or revoke access |
| Analytics property | Your business | Your historical data leaves with the agency |
| Design files | Delivered to you in an open format | Future work restarts from screenshots |
| Code repository | Accessible to you | Nobody else can maintain the site |
| Third-party licenses | Your business | Renewals 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.
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.
| Symptom | Repair | Rebuild | Why |
|---|---|---|---|
| Looks dated, ranks well | Yes | No | Styling is separable from structure |
| Slow on mobile | Usually | Sometimes | Often images and scripts rather than the build |
| Cannot be edited without a developer | No | Yes | The ongoing cost outweighs the build |
| URL structure prevents ranking | No | Yes | Structure is not restylable |
| CMS no longer supported | No | Yes | Security decides it |
| Fails accessibility | Sometimes | Sometimes | Depends whether it is markup or structure |
| Needs new functionality | Sometimes | Sometimes | Depends 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.
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?
How long does a website take to build?
Do I need a new website, or can the current one be fixed?
Will a new website improve my Google rankings?
What is a redirect map and why does it matter?
Which platform do you build on?
Who owns the website when it is finished?
Do you write the content?
What about accessibility?
How fast will the site be?
Do you do ecommerce?
Can you build the site in more than one language?
Do you host the site?
What happens after launch?
Do I need ongoing maintenance?
How many pages should my site have?
Can you work with our existing SEO or marketing agency?
What is in the contract?
Why do you tell people not to rebuild?
How do I get started?
How long does a website project take?
Who writes the content?
What does a website cost?
Do we own the site at the end?
What happens after launch?
Will the new site keep our rankings?
WordPress, Shopify or Squarespace?
How many revision rounds are included?
Do we need a designer and a developer?
What is a staging environment?
How do we handle accessibility?
What about hosting?
How is the project managed?
What if we need changes after launch?
Do you build in a page builder?
How do we measure whether it worked?
What content management training is included?
How long should a website last?
Sources and further reading
- web.dev: Core Web Vitals explained
- web.dev: Largest Contentful Paint
- web.dev: Cumulative Layout Shift
- web.dev: Interaction to Next Paint
- Google PageSpeed Insights
- Google Rich Results Test
- Google Search Console
- W3C Markup Validation Service
- Schema.org: LocalBusiness type
- Schema.org: Service type
- Schema.org: FAQPage type
- Schema.org: HowTo type
- W3C: WCAG 2.2 quick reference
- Google Search Essentials — SEO starter guide
- Google: creating helpful, reliable, people-first content
- Google: intro to structured data
- Google: LocalBusiness structured data
- Google: FAQPage structured data
- Google: Article structured data
- Google: Product structured data
- Google: title links in search results
- Google: control your snippets
- Google: robots.txt introduction
- Google: sitemaps overview
- Google: consolidate duplicate URLs
- FTC: CAN-SPAM Act compliance guide
- FCC: telemarketing and robocall rules (TCPA)
- FTC endorsement guides — reviews and testimonials
- FTC: rule on consumer reviews and testimonials
- HHS: HIPAA guidance on online tracking technologies
- US Census Bureau QuickFacts: New Jersey
- US Census Bureau: American Community Survey
- US Census: Statistics of US Businesses
- Bureau of Labor Statistics: New Jersey data
- US DOJ: web accessibility guidance under the ADA
- W3C: WCAG standards overview
- WAVE accessibility evaluation tool
- Google: localized versions and hreflang
- WordPress documentation
- MDN: web performance
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.
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
| If | Choose | Because |
|---|---|---|
| Your team edits weekly | CMS or builder they know | Maintenance is the recurring cost |
| The site is mostly static | Simpler build | Less to break and cheaper to host |
| Requirements are unusual | Custom | Configuring around a platform costs more than building |
| You sell products | Established ecommerce platform | Payments and tax are solved problems |
| You need an application | Custom | Business logic is not a content problem |
| Budget is tight | Fewer templates, done well | Template 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.
