A senior engineer on your bench, shipping under your brand.
You keep the relationship. I do the work under your brand, in your repos, on your terms: the NDA is signed before I see anything, the deliverable carries your logo only, and whether I ever speak to your client is your call.
Start to finish, you work with one senior engineer: the studio’s founder. When a build needs more hands than one, vetted collaborators I’ve worked with before join under the same accountability. You still deal with me, and I answer for what ships.
Capacity & availability
Your client’s work gets a senior engineer who isn’t split across five other accounts: I turn work away to keep it that way, and I treat that as a hard rule. Describe the engagement in a note and you get a real answer: yes, no, or the date I can actually start.
I am in Romania, so most of the collaboration happens without a meeting: a daily written update, a shared task board, one call a week in the hours we overlap. That is how a past engagement with a US-based agency ran. Same-day live pairing is the part it suits least, so say so upfront if you need it.
Stack & specialties
The default lane is back-end and architecture: where most scoping calls end up, and where most of 13 years in software has been spent.
Where I stop: front-end is workable, but it isn’t a specialty. If your project needs someone who lives in CSS and pixel-level UI work, you’ll hear that on the scoping call, not after the slot is booked. If you already have a front-end engineer, coordinating with them works fine.
“He stays with a job until we and our clients are fully happy, which is wonderful.”
That is one line out of a longer recommendation. All three sit unedited on the personal site: Henk Schram, Stacey White, and John Parenteau, from earlier engineering work.
White-label & NDA process
Standard NDAs get reviewed and signed without a two-week legal back-and-forth: most agency NDAs cover familiar ground, and delay here just burns the calendar you’re trying to protect. Work happens inside your repositories and your cloud accounts, and your client sees your brand on everything.
Your client owns the code and the IP, under the agreement you already signed with them. Nothing about the subcontracting arrangement changes that.
From your first message to weekly output
30 minutes on what the client needs and where I fit into your delivery. No quote on the call.
A written summary of scope, billing model, and price, before anything starts.
What shipped, what’s next, anything that needs a decision from you.
Documentation, access transfer, nothing left half-explained when the engagement ends.
How billing works
Priced per engagement, in writing, before work starts.
Three ways to engage me. We settle on the shape at the scoping call.
- A monthly block of reserved time. For steady senior capacity: invoiced monthly, renewed a month at a time, two weeks’ notice to end.
- A fixed price per stage. When the work splits into clear deliverables, agreed in writing before each one starts.
- An advance and a final payment. For a one-off project with a fixed end: a 50% advance when we start, the remaining 50% on handover.
One rule behind all three. The rate is agreed per engagement and fixed in the written scope before work starts, not renegotiated later.
Hot-fixes sit outside the three: scoped on their own, billed for the hours they take, closed with a written summary of what was done and why.
A fixed quote before you commit hours. The audits carry a fixed price agreed per scope (code, performance, security, or AI-readiness), delivered in 1–3 days as a written report.
Have a slot to fill?
Describe the engagement: model, rough scope, timezone constraints if any. The NDA goes out first, before either of us has said anything worth protecting.