Launch
A focused site for a company that needs to exist online properly.
- Five to eight pages, written with you
- Identity refresh and design tokens
- Astro build, headless CMS, WebP pipeline
- Six weeks from kickoff to launch
Strategy, design and engineering under one roof, for companies that want a web presence they can measure.
Start a project
01 / What we do
We do not hand a design file to a separate build team. The people who draw the interface write the code that ships it.
We start with the business question, not the homepage. Research, positioning, information architecture and a content plan the whole team can execute.
Identity systems, design tokens and interfaces designed in the browser, so what you approve is exactly what ships.
Static-first sites and web apps on Astro, Next.js and a headless CMS. Fast by default, accessible by contract, owned by you.
After launch we keep measuring: search performance, speed budgets, editorial support and a quarterly review with your team.
02 / Selected work
Every project ships with a performance budget, a written accessibility statement and a number we agreed to move.
Checkout conversion up 31% in the first quarter, on a catalogue of 140 unique pieces.
Four weeks from kickoff to a pilot used by 12 finance teams.
2,300 bookings a month across 14 clinics, none of them by phone.
Case studies are written with the client, published with their numbers, and kept online after the contract ends.
Read the case studies03 / How we work
Four phases, each with a fixed scope, a fixed price and a demo at the end. You can stop after any of them and keep everything produced so far.
Interviews, analytics review, competitive read and a written brief. We leave with one sentence about what the site is for.
Identity, type, tokens, then real pages in the browser. Content is written alongside layout, never poured in afterwards.
Static-first stack, headless content, a shared board and a weekly demo. Your editors are trained before launch, not after.
Launch on the date written in the proposal. Then 90 days of measurement against the number we agreed to move.
A senior designer or engineer runs your project from kickoff to launch. No account layer in between.
A shared board you can open any day. Every decision, every file, every demo recording lives there.
Each phase is quoted before it starts. If we get the estimate wrong, that is our problem, not yours.
04 / The people
Eleven people, no juniors on client work, and everyone here writes for the Journal. The person you meet is the person who does the work.
Lead engineer, co-founder
Head of analytics
Cloud architect
Product designer, co-founder
We write down what we learn. Notes on performance budgets, accessibility audits and the occasional launch post-mortem, published in the Journal every other week.
Read the Journal0%
of clients come back for a second engagement.
“They asked better questions than our own board did. The site launched on the date written in the first proposal, which I had not believed.”
“Our engineers stopped complaining about the marketing site. In nine years, that has never happened.”
05 / Engagements
Three ways to work with us. Every figure below is a floor, quoted phase by phase, and never revised upwards mid-project.
A focused site for a company that needs to exist online properly.
A design system and a multi-market site or product front-end, built to grow.
A senior team on retainer for design, engineering and growth.
06 / Journal
Performance numbers, accessibility audits and the occasional post-mortem. Written by the people who did the work.
Every Synora proposal names the weight, the request count and the Largest Contentful Paint the site must respect. Here is how we set those numbers and what happens when a client wants a video in the hero.
Every Synora interface is designed in the browser, in the real typeface, with the real content, on the real grid. What that changed for clients, for engineers and for the work.
Not a badge, not a plugin. A page that says what was tested, what passed, what did not, and who to write to. Here is the template and the reasoning.
Six things almost every prospect asks in the first call. If yours is not here, ask anyway.
A Launch project takes six weeks. A Platform project takes ten to fourteen. The date is written into the proposal, and in 140 launches we have moved it four times, each time at the client's request.
Per phase, yes. Discovery is quoted first. At the end of it we quote Design, and so on. If a phase costs us more than estimated, we absorb it. If you change the scope, we re-quote the next phase, never the current one.
Often. Your designers and engineers join the shared board from day one. We document tokens, components and content models so the hand-over is a formality, not a project of its own.
Static-first. Astro for content sites, Next.js when there is an application to run, a headless CMS your editors can actually use, and images served as WebP with responsive sizes. No page builder, no plugin stack to babysit.
You do, from the first invoice. The repository is created in your organisation, the design files are in your workspace, and there is no licence to renew. If we part ways, nothing breaks.
Ninety days of measurement are included in every project. After that, most clients move to a Partnership retainer, or simply call when they need something. Both are fine with us.
Tell us what the site is for and what number it should move. We reply within two working days, with questions.
Tell us about the project