For agencies and consultancies
Agencies send us the work they can't staff. Agents draft; two senior humans decide what ships. You get the Figma, the repo, and a live site with your client's name on it and nobody else's.
Most of what we build ships under someone else's name, which is why you won't find it in a portfolio.
Why agencies call
You won the project. Your team is already full.
Your designer left in the middle of the sprint.
The client wants a working site. You have a Figma file and no developer.
We pick it up wherever it stopped, and hand it back live.
How it runs
Most studios run these steps in a queue: research waits on the brief, design waits on research, code waits on design. We don't. The only two places anything waits are the rows in amber.
The amber rows are people. A senior designer picks the direction and throws out whatever looks generated. A senior engineer reads the code before it merges. Nothing reaches your client without both, because a pipeline that approves its own work is just a faster way to ship something wrong.
A senior designer and a senior engineer read every deliverable before it leaves. That is the one step we don't automate, and it is why you can put your name on the result.
End to end
Scope, deadline, the client's brand, whatever already exists. Twenty minutes on a call or a paragraph in an email. You get a fixed price and a fixed date back inside 48 hours, and an NDA before any of it.
Agents produce the research digest, the structure and the first screens in your client's brand. Then a senior designer throws out what looks generated and takes the file to finished. That second part is most of what you're paying for.
Components come out of the tokens, then a senior engineer reads them line by line before anything merges. Tests, accessibility and performance run on every pull request, so problems surface in week one instead of the day before launch.
We don't hand over a zip and wish you luck. Domain, analytics, forms, email and the CMS are connected and tested in production before we call it done. Then the whole thing moves to your organisation.
Not only websites
Most companies run on software that half fits. The gap gets filled with spreadsheets, and with people's time.
Your team keeps a spreadsheet next to the tool, because the tool doesn't fit how you work.
Every hire costs another seat. Every year. Forever.
You asked for a change eight months ago. It is still on someone's roadmap.
On a licensed tool, a change is a request and a vote you don't attend.
Here you order it, and it ships the week after.
The one your teams live in all day, running on your own database.
On your brand and your systems, not on an editor's.
The shared file twelve people edit and nobody dares break, turned into something that can't.
What we already do. Same pipeline, different output.
The code, the data and the hosting are yours. No seat count, no annual rise, no feature removed because it stopped fitting someone else's roadmap.
We rebuild what you bent to make it fit. We don't rebuild payroll, accounting or a heavy CRM. If a mature product does the job, buy the product — we will tell you so on the call.
One brief
Full coverage
One contact
One handover
Speed
Eight pages, a design system, a CMS and a deployment. Here is where the weeks actually go.
The time doesn't come from typing faster. It comes from not losing two weeks waiting for design to finish before code starts, and not losing a third in the handover between two freelancers who have never met.
Averages across our last projects of comparable scope. Ask on the call and we will walk you through a real one, dates included.
Before you ask
None of them are design problems. Here is how each one is handled, in writing, before it happens.
They usually do. Two rounds of revision are already in the price. Past that we re-quote the difference before touching anything, so the surprise arrives on a quote instead of an invoice.
Nine times out of ten the text is the long pole, and it is never the designer's fault. We build against realistic placeholder copy and swap the real thing in one pass, so a late Word document doesn't move the launch date.
Ask us on the first call, before you quote your client. If it has to run on their WordPress or their internal framework, sometimes the answer is yes. Sometimes it is an honest no, which is still cheaper than finding out in week four.
We ask for one person with the final say and one place to leave notes. If your client can't give you that, say so at the start and we will build the review rounds around it instead of pretending.
What doesn't change
A senior designer and a senior engineer review everything before it leaves. If it looks generated, it doesn't go out.
Figma file, repo, deployment, domain. All of it transfers on final payment. We keep no licence and reuse nothing.
NDA before the brief. Nothing your client gives us trains anything, and production credentials never leave your accounts. On internal tools: single sign-on, role-based access and a written data map before a line is built.
Engagements
from €4,500
One defined scope: a landing page, an app, a redesign. Designed, built and put live.
€3,200 / week
One week, full focus. For unblocking a project that is already live.
€6,800 / month
Eight days a month held for you. For steady overflow.
A tool that runs on your data is not a delivery, it is a service. Run covers hosting, monitoring and your change budget — so a modification is a week, not a roadmap. Quoted with the build.
Prices are for the work, not for hours. Nothing gets invoiced that you haven't approved on a quote first.
Fit
Saying no is how the dates stay real.
FAQ
No. We work under your name. We can use an address on your domain if you want one.
That is your call and it goes in the contract. We follow whatever you commit to, including a written statement of what was generated and what was authored if your client asks for one.
A small senior team directing the pipeline. The same people from brief to handover. No junior hand-off halfway through, no rotating roster.
Everything lives in your accounts from day one: your Figma, your repo, your Vercel. If we vanished tomorrow you would still have a working project and a developer could pick it up on Monday. That is deliberate, and it is worth checking with anyone else you outsource to.
Often yes. Send us the repo before you quote your client, not after. If it is in bad shape we will say so and tell you what it costs to work in it anyway.
You do, in full, once the final invoice is paid — Figma, repo, deployment, domain. We keep no licence and reuse nothing from your project.
That is the test we hold it to. Ordinary Next.js and React, typed, commented where it isn't obvious, with a written handover. If your developer can't take it over, we didn't finish.
Two rounds of revision are in every quote. If the direction is wrong after round one, that is on us and we redo it at our cost.
Either. Most take both, because the handover between the two is where projects usually lose a week.
Next.js, React, Tailwind, Supabase, Vercel. Ask about anything else — the answer is sometimes yes.
Send the brief. You get a yes or a no, a price and a date, inside 48 hours.