For studios
Development Capacity Under Your Brand
Design and marketing studios win work they can build most of. This covers the rest: the WooCommerce checkout, the integration nobody quoted for, the performance problem that appeared after launch. Under your name, talking to your team, and nowhere near your client.
Start with a pilotSee what I build
- Per project, or a retained block of days
- EET · Bacău, Romania
- None, unless you ask
- One paid pilot task
The terms
What A Studio Actually Needs To Know
The four questions every studio asks before subcontracting anything, answered before you have to ask them.
Your Brand, Start To Finish
Commits, documentation, staging URLs and handover notes carry your name. If your client sees a repository or a deploy log, it says your studio on it.
No Contact With Your Client
Unless you put me in the room. Where a call is genuinely faster than three rounds of relay, I join as your team, introduced under your studio and briefed by you.
No Poaching, In Writing
A non-solicitation clause in the agreement, not a promise in an email. Your client stays your client after the project ends, and after the next one.
One Developer, Named
The same person for the whole engagement. No rotating bench, no junior doing the work while a senior attends the calls, no account manager between your project lead and the code.
How it starts
A Paid Pilot, Before Either Of Us Commits
A sales call tells you how someone sells. One small real task tells you how they work.
Send One Defined Task
A landing page, a template, a plugin fix: something real but bounded, with a deadline that matters slightly. Quoted fixed price before it starts.
Watch The Communication, Not The Code
Most studios can tell whether the code is good. What decides a partnership is whether questions arrive early, whether estimates hold, and what happens when something goes wrong mid-build.
Then Decide
If it worked, we write down rates, notice periods and how briefs get handed over. If it did not, you have paid for one landing page and learned something cheaply.
There is no retainer to sign before the pilot, and no minimum after it. A partnership that needs a lock-in to survive is not one worth having.
Fit
Where This Works, And Where It Does Not
This suits studios that sell design, strategy or marketing and hit a build they would rather not staff for: a store with real complexity, an integration into a client's ERP, a platform decision they do not want to make alone.
It suits studios less well when what they actually need is a second full-time developer. One person has a finite number of days, and a partner who is quietly at capacity is worse than no partner. Where that is the shape of the problem, I will say so rather than take the work and stretch.
Currently taking on new studio partners. If you are weighing several, ask each of them for a fixed price on the same small task and compare what comes back.