What a project includes.
One thing, done properly: the design and the build of a front end, and the numbers to show it works. We are not an agency and there is nothing else on the menu.
What you get
The design
Type, colour and layout as a token system rather than a set of screens, so the site stays coherent at the twentieth page as well as the first. Done in the browser, because that is where the type actually wraps.
The build
Vite, React and TypeScript, output as static files with every route prerendered. It runs on any host that can serve a folder, and it will still run there in five years.
The proof
Lighthouse, keyboard and screen-reader passes, bundle sizes, and load times from the deployed site. Delivered as numbers you can re-run yourself, not as a claim.
What decides the cost
We do not publish a price, because the same number would be wrong for most people reading it. These are the five things that actually move it, in the order they move it.
Unique templates, not pages
Forty pages built from four layouts is a smaller job than eight pages that are all different. Count the layouts.
Whether the motion is bespoke
Reveals and transitions from the system are close to free. A mechanism designed for your argument alone — the kind of thing the plane in our own header is — is not.
How many languages
A second language is not a second site, but it is a second set of copy, a second set of metadata and a routing decision that is expensive to reverse later.
Whether the content exists
Writing is design material here, so if the words do not exist yet, someone has to write them. That is real time whether it is ours or yours.
Whether anything has to talk to a server
A brochure site is static and cheap to host forever. A form, a booking flow or a login adds a backend, and a backend adds maintenance.
After one call we can usually give you a number. If we cannot, we will tell you exactly what we would need to know in order to.
How it runs
Six stages with a checkpoint at each one. You see the work and approve it before the next stage starts, so there is no reveal at the end and nothing to be surprised by. This site was built in exactly these stages.
Direction
Concept, palette, type, layout system. Nothing is coded yet.
Foundations
Tokens, typography, primitives, and one section at final quality.
The main page
The home page complete, including whatever the one mechanism turns out to be.
Everything else
Remaining templates, forms, error states.
Infrastructure
Prerender, metadata, structured data, sitemap, social images.
Audit
Lighthouse, keyboard, reduced motion, mobile, bundle size. Fix, re-run, report.
Dates come with the quote, once the number of templates is known. We would rather give you a schedule we can keep than a fast one we cannot.
What we do not do
Said plainly, so nobody spends a call finding out.
- WordPress, page builders, and themes bought from a marketplace. This is the whole reason the studio exists, so there is no version of a project where we do it.
- A CMS for content that does not change. It is a maintenance cost and a security surface bought to solve a problem most sites do not have.
- Projects where the content does not exist and nobody has agreed to write it. That is not a scoping problem, it is the project quietly not being ready.
- Work where success cannot be described as something observable. If nobody can say what the site has to make happen, we are the wrong studio and would rather say so now.