Most of what your website needs to say already exists — in the deck, the repo, the demo, the answer you give when someone asks what you are building. The work is turning it into something a stranger can read in thirty seconds. These are the four stages that do that.
We read what you already have — the deck, the README, the paper, the demo — then write the site: what the work is, who it is for, and why it holds up. You review sentences instead of staring at a blank page.
One token layer behind every screen, and every component drawn in the states it will really be in — so the site stays consistent as it grows instead of drifting page by page.
Typed endpoints, a real database, and forms that deliver, behind a typed React and Next.js front end. The site does work rather than only describing it.
Your domain, your certificates, your accounts, your repository. Merge a change and it is live in minutes — and after handover, that runs for you.
Four stages, run by the same people. Nothing is briefed out to a third party, nothing waits on a handover meeting, and you are never asked to supply copy you have not written.
We start with what exists: the deck, the README, the demo, the recording of you explaining the product to someone who did not get it. From that we settle three things — what you do, who it is for, and what makes the claim believable — and write the site around them. You get words on a page to react to, which is a far easier job than writing them, and nothing goes into design until the argument holds.
The approved copy is designed, not decorated. Type, spacing, colour and radius are defined once as tokens, and every screen resolves from that one layer — which is why the site still looks like itself after you have added six pages to it. Components are drawn in the states they will really be in: empty, loading, too long, failed. The pretty state is the easy one.
The design becomes a typed Next.js front end and whatever it genuinely needs behind it — endpoints, a database, a form that delivers, a place to post from. We build the half you can see and the half you cannot in the same week, so the front end is never written against an API that does not exist yet, and we add no service you did not ask for.
We point your domain, issue certificates, set up analytics and submit the site for indexing. Then you get the repository, the deploy that runs from a push, and a walk through changing the things you will want to change. Hosting can stay with us or move the same day. Nothing about the site is locked to us, which is the only handover worth the name.
Send the deck, the paper, the repo, the demo.
We'll send back a website.