Website builds that are fast, findable, and easy to own
People rarely buy a new website because they want a new website. They buy it because leads aren't converting,
nobody can update the old one, or Google ignores half the pages. We build around that problem first, choose
the platform second, and hand over a site your team can actually run.
Astro on Cloudflare is our default; WordPress, Webflow or Shopify when your team's editing habits or your
commerce needs make them the better fit.
Every build ships with structured data, a redirect map from the old site, analytics and conversion tracking,
and forms tested end to end into your CRM.
Performance targets are Google's Core Web Vitals thresholds; accessibility is built to WCAG 2.2 AA, the
current W3C Recommendation, and tested by hand as well as by tools.
Our published estimate for a standard ten-page brand site is two to three weeks. Content readiness sets the
pace more than code does.
Live work you can inspect: Good Life Insurance Group, Squeaky Clean Turf, Summit Tracker, and the site
you're on.
Who this is for
Service businesses whose current site gets traffic but not enquiries.
Companies running two or three sites that should be one, splitting their brand and their backlinks.
Teams that need something a theme can't do: an estimator, a quote builder, a gated portal, a pricing table
driven by real data.
Businesses moving off a platform that has become expensive or fragile to maintain.
Anyone about to spend more on ads who suspects the landing pages are the real bottleneck.
If you need a one-page placeholder by Friday, a hosted site builder will serve you better and cost less. Come
back when the site has to earn its keep.
What's included in every build
Discovery and information architecture. The sitemap and page briefs exist before any design
does, along with an inventory of every URL on your old site.
Design system. Color, type and spacing tokens plus a component library, so page number 40
looks like page number 4.
Accessibility to WCAG 2.2 AA.WCAG 2.2 added criteria that trip
up many templates, such as a
minimum pointer target size of 24 by 24 CSS pixels. We test keyboard paths, contrast, focus order and form errors rather than installing an overlay widget.
Performance budget. Built and verified against Google's thresholds — LCP within 2.5 seconds,
INP of 200 milliseconds or less, CLS of 0.1 or less at the 75th percentile (web.dev).
Structured data. Organization, Person, Service, LocalBusiness, Product and BreadcrumbList as
they apply, matching what's visible on the page.
Redirect map. Every old URL that earned traffic or links gets a page-level 301.
Measurement. GA4 and Google Tag Manager with named key events for the form submits and
bookings that matter, plus Search Console and Bing Webmaster Tools verified before launch.
Forms wired to your CRM, with notification recipients confirmed and a test lead traced all
the way into the pipeline.
Security basics. HTTPS everywhere, security headers, and spam protection on every form.
Documentation and a handover session for whoever will edit the site.
How a build runs
Discovery
The business goal, the two or three conversion paths that matter, who edits the site, and an inventory of
existing URLs, forms, integrations and tracking.
Content and IA
Sitemap and page briefs. We check content readiness early because missing copy, not code, is what delays
most launches. We can write or edit copy, with your subject-matter review.
Design
Key templates designed in Figma on top of the design tokens, reviewed on real devices, not just a desktop
artboard.
Build
Components first, then pages. Interactive pieces are isolated so the rest of the page stays static and fast.
Business data such as pricing lives in one place and every component reads from it.
QA
Accessibility checks, performance traces on each template, structured-data validation, redirect testing
against the old URL list, and labelled test submissions through every form into the CRM.
Launch and handover
Redirects live, sitemaps submitted, tracking verified in real time, then documentation and training. We stay
on for an agreed post-launch window to catch anything real traffic reveals.
What we need from you
One decision-maker who can approve design and copy within a few days.
Access to the current site, domain registrar, DNS, analytics and Search Console.
Your brand assets, real photos of your team, work and premises, and any existing copy worth keeping.
A list of where leads should go and who should be notified.
Time from a subject-matter expert to review anything we write about your services.
Mistakes we design out
Designing pages before anyone knows what they'll say.
Launching without a redirect map and discovering the loss in Search Console a month later.
Contact forms whose notifications still go to a former agency's inbox — we found exactly that during the
Squeaky Clean Turf project.
Prices typed into five different pages, so one change leaves four of them wrong.
Tracking bolted on after launch, which means the first weeks of data are unusable.
4000-pixel images uploaded straight from a camera, and hero carousels nobody clicks.
A lazy-loaded hero image. It delays the exact element Largest Contentful Paint measures, and HTTP Archive's
2025 Web Almanac
found about 16–17% of pages still do it.
An accessibility overlay script installed in place of fixing the markup underneath.
Choosing the platform, honestly
We have a default, but the right answer depends on who edits the site, how often, and whether you sell online.
This is the trade-off table we walk clients through:
Platform
Best when
Watch out for
Astro on Cloudflare
Marketing and content sites where speed, security and hosting cost matter. Static HTML at the edge, no
plugin stack to patch, interactive pieces added only where needed.
Schema, redirects and feeds live in code rather than plugins. Editors work through Git or a headless CMS
we connect.
WordPress
Large editorial teams publishing daily, or when a specific plugin genuinely does the job.
Ongoing updates, PHP upgrades and plugin conflicts. Budget for
maintenance from day one.
Webflow
Designer-led brand sites where marketing wants visual control without a developer.
Heavier custom logic and large dynamic data sets are harder than on a code-first stack.
Shopify
Anything where commerce comes first. Shopify states it is
certified Level 1 PCI DSS compliant, so you aren't building checkout security yourself.
Theme and app sprawl. Headless storefronts are possible but add engineering — see our
Shopify page.
One update on our own default. Cloudflare's
Pages documentation now
tells developers to start new projects on Workers, which serves
static assets
and supports most Pages use cases. New Astro builds therefore deploy to Workers using
Astro's Cloudflare guide; existing Pages sites, including some of the projects below, keep running where they are until there's a
reason to move.
The deciding question is rarely technical. It's who will make the next hundred edits. If that's a marketing
coordinator with no developer, a visual editor wins even if it's slower. If it's a small team comfortable with a
pull request, a code-first site is faster, cheaper to host and has far less to patch.
Launch checklist, with the numbers behind it
Every item has a pass condition. The thresholds come from the standards bodies and platforms themselves, and the
context column explains why each one gets checked rather than assumed.
Check
Pass condition
Why it matters
Core Web Vitals
LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1 on every template
Only 48% of mobile sites met all three in 2025 (Web Almanac)
Automated accessibility scan
Zero WAVE and axe errors on each template
The
WebAIM Million 2026
found detectable WCAG failures on 95.9% of top home pages, 56.1 errors per page on average
Manual accessibility pass
Every flow usable by keyboard alone, visible focus, labelled form errors
WebAIM notes automated tools can't detect every conformance failure
Touch targets
At least 24 × 24 CSS pixels or adequately spaced
WCAG 2.2 success criterion 2.5.8
Headings
One H1 per page, no skipped levels
Screen reader users navigate by headings; WebAIM found skipped levels on 41.8% of pages
Redirects
Every old URL with traffic or links returns one 301 hop to a live page
Protects rankings and bookmarks earned by the old site
Structured data
Validates in the Rich Results Test and matches visible content
Markup that contradicts the page is ignored or worse
Forms
A labelled test lead reaches the right CRM record and the right person
The most common silent failure we find on inherited sites
Analytics
Page views and key events visible in GA4 real-time reports
Data from launch day forward is usable
Indexing
No stray noindex; sitemap submitted; staging blocked by authentication, not robots.txt
The classic launch-day mistake
Pricing and timelines
Builds are quoted as a fixed scope after discovery. The variables are page count, how much copy we write,
integrations (CRM, booking, commerce), and custom interactive features. Our
web design page publishes the timelines we work to: two to three weeks for
a standard ten-page brand site, longer for custom applications. Good Life Insurance Group's 77 pages went live
over a weekend with AI assistance, but that depended on the content being ready.
Hosting is billed by the provider directly, in your account. On Cloudflare it is effectively free at small
business scale — the Squeaky Clean Turf write-up compares it with the two hosting bills it replaced. No
percentage fees and no long contracts, consistent with our pricing page. If the new site
replaces an old one with real search traffic, the move is handled as a
site migration.
Platforms we work in
The tools a build touches, from design file to production.
Two WordPress sites rebuilt as one 64-page Astro site on Cloudflare Pages, with Shopify handling checkout
and an interactive estimator that reads the same pricing data as the rest of the site.
A PIN-gated insurance CRM mockup on Cloudflare Workers, Durable Objects and D1 — the same stack we use when
a "website" turns out to need application logic.
Checks a live site for SEO, security headers, accessibility, consent and Core Web Vitals. Run it on your
current site to see what a rebuild would need to fix.
It depends on page count, how much copy you need written, integrations and custom features, so we quote a
fixed scope after a discovery call rather than publishing a rate card. You'll know the full price before any
work starts.
How long does a website build take?
Our published estimate is two to three weeks for a standard ten-page brand site. Larger sites and custom
applications take longer. The biggest variable is usually how quickly content and approvals arrive.
Will I be able to edit the site myself?
Yes. On WordPress, Webflow and Shopify you edit in the platform. On Astro we connect a headless CMS or set up
a simple Git-based workflow, and the handover session covers the edits you'll make most often.
Will my Google rankings drop when the new site launches?
Not if the migration is handled properly. Every build includes a redirect map and pre-launch checks; for
larger or riskier moves, see our site migration service.
Is an accessibility overlay enough to meet WCAG?
No. Overlays add a toolbar on top of the page but don't fix the underlying markup, labels or focus order that
WCAG tests. We build the fixes into the templates and verify them with automated tools plus a manual keyboard
and screen reader pass.
Do you use AI to build websites?
Yes, with a human accountable for every change. Buddy, our own agent, helps draft schema and content and
reviews code. Everything is reviewed before it ships, and we disclose AI assistance on the pages where it's
used.
Who owns the website and code?
You do. Client work is your IP unless we explicitly agree otherwise, and domains, hosting and analytics are
set up in your accounts.
Tell us about your build
Share your current URL (if any), what the site needs to do, and when you need it live.
John, Kristy, or Sandeep will reply.One of the three of us will respond personally within 1 business day. No SDR queue.
Message received.
One of us will reply directly within one business day. While you wait, run a free
Buddy audit on your account.
Top 25 references
The primary sources, standards, research, and tools we rely on for this work. Every link was checked on
2026-10-11. We aren't affiliated with these publishers unless noted.
Official documentation
Web Vitals— web.dev (Google Chrome) The LCP, INP and CLS thresholds every template is tested against before launch.
SEO Starter Guide— Google Search Central Google's baseline on titles, URLs, links and content that a new site should get right on day
one.
Guidance on Web Accessibility and the ADA— U.S. Department of Justice (ADA.gov) The DOJ's guidance that businesses open to the public must make their websites accessible.
Organization— Schema.org The vocabulary behind the Organization markup that ties a site's logo, contact points and profiles
together.
How Long Do Users Stay on Web Pages?— Nielsen Norman Group Why the first seconds decide whether a visitor stays, and what that means for the top of every page.
Designing Effective Carousels— Nielsen Norman Group Usability findings on carousels and when a static hero does the job better.
AI disclosure: This page was drafted with AI assistance and edited by a human. Third-party facts
link to the official source they came from (checked 2026-10-11); platform names and logos belong to their owners
and do not imply a partnership or endorsement.
