Sell the build. We'll do it under your name.
You own the client, the brand and the relationship. We take the engineering half - on a fixed scope and a fixed price you can quote against - and stay invisible while your studio delivers it. The client keeps dealing with you, because they should.
How it works
- Your brand on the work, your studio in the room
- A written non-solicit before we meet your client
- A fixed price you mark up, quoted before you commit
48h
From your brief to a fixed scope and a price you can mark up
0
Client-facing mentions of us - everything ships under your brand
12 mo
Written non-solicit on every client we meet through you
100%
Of the code handed to you or your client, documented
The week after the pitch lands.
None of these are a studio problem. They're what happens when the work you sell is broader than the work you staff.
You won it, and now it has to be built
The pitch went well, the client signed, and the build is the half your studio doesn't do. The date is already in their launch plan and you're sourcing a partner with the clock running.
Your last dev partner went quiet mid-project
Replies slowed, then stopped, and you found out from your client rather than from them. You absorbed the apology, the timeline and the invoice - and you can't be in that position twice.
You're quoting work you can't estimate
The brief says portal, dashboard, integration. You need a number for the proposal this week and the honest answer is that nobody in the room can size it, so the margin is a guess with your name on it.
Managing freelancers is eating the margin
Three contractors, three time zones, and your project manager spending half a week stitching their work together. The rate looked cheap until you counted the hours spent coordinating it.
You're introducing a stranger to your client
Whoever builds it ends up in the room, on the calls and in the client's inbox. The worry isn't only quality - it's whether they turn up next year with a proposal of their own.
The build doesn't look like the design
Spacing drifts, the motion is gone, the states nobody drew got invented on the fly. Your client compares it to the deck you presented, and the studio's reputation is what's on the line.
Three arrangements. All of them quiet.
Which one fits depends on whether you've already won the work, already have the team, or are still trying to price the brief. Most studios start with one project and settle into a rhythm.
Send us a brief- Model 013 to 12 weeks
White-label build under your brand
You've sold the work and you own the client. We take the design and build it, invisibly, on a fixed scope and a fixed price - so you can price your margin at the proposal stage instead of hoping.
- A fixed quote against your scope, normally inside 48 hours, ready for your proposal
- Everything ships under your brand - your decks, your staging domain, your sign-off
- Your project manager stays the single point of contact, or we join client calls as your team
- Design honoured to the pixel: states, motion and the responsive behaviour nobody drew
How Website Development worksYou end up with
Work your client believes your studio built, delivered on your date.
- Model 021 to 6 months, rolling
Overflow capacity for a busy quarter
You have the team, just not enough of it this quarter. We take the builds your own developers can't reach, in your process and to your standards, and step back out when the pipeline settles.
- Named people at an agreed allocation, booked a month at a time
- Your tools, your rituals, your definition of done - we adopt the studio's process
- Small pull requests your leads review, so quality stays a decision you make
- Month to month with 30 days' notice, because agency pipelines aren't linear
How SaaS Development worksYou end up with
Two or three more projects delivered this quarter without a permanent hire.
- Model 03During the pitch, then the build
The technical half of your pitch
You're pitching something you can't size - a platform, a portal, an integration into systems you've never seen. We sit behind you during the pitch, cost it honestly, and build it if you win.
- A scoping call on the brief and a written estimate you can price against
- Architecture and feasibility answers for the proposal, in language a client reads
- One of us on the pitch call as your technical lead, under your brand, if it helps
- The same numbers carried into the build - the estimate isn't reopened after you win
How SaaS Development worksYou end up with
Bigger briefs answered with confidence, and a quote that survives delivery.
Letting someone near your client.
Subcontracting puts your relationship and your reputation in someone else's hands. Here is what we sign, in writing, before that happens.
We stay behind your brand
Your studio presents the work, your staging domain, your documents. If it helps to have us on a client call we'll join under your brand and your email - and if you'd rather the client never hears our name, they won't.
We don't go around you
A written non-solicit on every client we meet through you: no direct approach, no proposal, no quiet renewal conversation. Your client relationship is the thing you're actually protecting, and it stays yours.
A fixed number you can price against
A written scope and a fixed price before you commit to your client, normally inside 48 hours. You mark it up however your studio prices, and change requests are quoted the same way rather than appearing on an invoice.
Your design survives the build
We build from your files, ask about the states you didn't draw, and flag anything that won't hold up responsively before it becomes a compromise. The delivered thing should be comparable to the deck you presented.
You always know where it is
A staging URL from the first week, a written update on an agreed day, and replies inside a working day. No four-week silences, and no client finding out about a slip before you do.
Handed over so you keep the retainer
Code in your account or your client's, conventional patterns, a README that runs in one command and a walkthrough for whoever maintains it. The ongoing relationship is yours to keep - we'll support it quietly if you'd rather not.
From your brief to your client's launch.
Nothing here commits you to anything until the scope is signed - and the estimate is free whether or not you win the pitch.
A call about the brief
Thirty minutes on what's been sold or what you're about to pitch, what exists in design already, and the date the client has been given. Signed under a mutual NDA if you want one first.
A fixed scope and a fixed price
In writing, normally inside 48 hours: what's in, what's explicitly out, the delivery date and the number. Yours to mark up and drop into your proposal as it stands.
Kickoff in your process
Design files reviewed, questions answered in one batch rather than a drip, and a staging URL live before the week is out. Your project manager keeps the client, we keep the build.
Updates you can forward
A written update on an agreed day, screenshots your account team can send on, and slips flagged the week they appear rather than the week they land.
Delivered, handed over, invisible
Deployed into accounts you or your client own, documentation and a walkthrough, and two weeks of close support included. Your studio launched it.
The ones asked before the first brief.
Anything about a specific service lives on the FAQ, and how we arrive at a number is on the pricing page.
Forward the brief you're pitching.Get a number back in 48 hours.
Estimates are free whether you win it or not, and we'll sign a mutual NDA before you send anything. Worst case your studio gets a second opinion on what the build is worth.