Web development
Site builds
A whole site, compiled once, deployed as files an edge can serve without thinking.
The engagement
What it costs and how long it runs
Stated up front, because these are the questions everything else depends on. The price is where the work starts, not a quote: scope moves it.
- Starts from
- $12,000
- Typical length
- 4 to 8 weeks
- Delivered as
- A repository and a deployment
- Handover
- Documentation and a walkthrough
Detail
What the work is
A complete site, compiled once into plain HTML. Routes, components and content in TypeScript, deployed to an edge that only has to serve files.
Most sites that feel slow are not slow because of what they contain. They are slow because a framework has to arrive, parse, and reconstruct in the browser a page that was already known at build time. A build that ends in HTML skips all of it.
The work starts from your content rather than from a template: what kinds of thing you publish, which fields they have, and which of those a reader actually needs. Routes and components fall out of that, and the pages are generated by walking the data rather than being maintained one at a time.
You are left with a repository you can read. Every page is a function, every design decision is a named export, and the output is a directory of files that any static host will serve.
Scope
What it includes
Everything below is part of the price. Anything not on this list is quoted separately rather than assumed.
- Routing, layout and component design from your content model
- Structured data, sitemap, feed and manifest generated by the build
- Deployment to Cloudflare, with cache headers written to match
Process
How it runs
In this order, with each step finishing in something you can look at rather than a status update.
1. Model the content
We write down what you publish as types: the fields, the relationships, and which pages each kind of thing generates. This is the part that decides how much of the site maintains itself.
2. Build the components
Layout, typography and colour become named exports, so a change of look is one edit rather than a pass over every page. Accessibility checks go into the build at the same time.
3. Generate and audit
The build renders every page, then parses each one back and fails on missing titles, broken heading outlines, images without alt text and contradictory ARIA.
4. Deploy and hand over
Cache headers written to match the assets, a preview environment, and a walkthrough of the repository so your team can add a page without asking anyone.
Outcomes
What is different afterwards
Not what happens during the work, but what you are left holding when it is over.
Nothing to hydrate
The browser receives markup and a stylesheet. There is no runtime to download, so there is no gap between the page appearing and the page working.
A build that refuses bad pages
SEO and accessibility regressions stop the build instead of shipping and being found in someone else's audit months later.
Hosting that costs nothing to scale
Files on an edge network have no origin to fall over, no runtime to meter, and no traffic spike that turns into an invoice.
Services
The other three
They combine: an audit often ends in a build, and a migration usually starts with one.
From $4,000 · Performance engineering
Performance audits
A measured account of what your pages actually send and how long it takes to paint, followed by the specific changes that would move the numbers.
From $6,000 · Accessibility consulting
Accessibility reviews
A review against WCAG, done in the markup rather than in a dashboard, with automated checks added to your build so the findings stay fixed.
From $18,000 · Web development
Migrations
Moving a site off a framework it has outgrown, keeping every URL, redirect and search ranking intact through the change.
Sound like the right one?
Describe the site, what you want to be different about it, and roughly when.