For agencies and studios

Your senior backend engineer,
on your team, under your name.

18 years of production engineering, available by the month. I work inside your process, ship under your brand, and never appear in front of your client.

Book a 20-minute call See how it works ↓
Available now 2 retainer slots open NDA on request

The four things you’re actually worried about.

White-label by default

Your client never learns my name. I use your email, your project management, your invoice. If you want me on a client call, I’m a member of your team and I introduce myself that way.

One person, start to finish

The person you scope with is the person writing the code. No account manager, no handoff to a junior after the pitch, no translation layer between what you asked for and what ships.

I work in your stack, your tools, your repo

Your Jira, your Slack, your branching strategy, your review process. I adapt to how your team already works — you don’t onboard a vendor, you add a seat.

No subcontracting. Ever.

Every line of code is mine. Nothing is passed to a partner shop, an offshore team, or an agency-of-an-agency. If I can’t do it, I tell you that instead of finding someone who says they can.

Where I’m the right call — and where I’m not.

Bring me in for

  • Backend architecture and API design — REST, GraphQL, event-driven
  • Python / FastAPI, Node, TypeScript, PostgreSQL
  • AWS infrastructure — ECS, Lambda, RDS, SQS, IAM, cost control
  • Auth, payments, permissions, and the parts that break at 3am
  • Data pipelines, integrations, and third-party APIs that fought back
  • Document processing and AI extraction pipelines
  • Rescuing a project someone else left half-built
  • Technical scoping and estimates before you quote a client

Not the right fit

  • Design and front-end polish — that’s what your team is good at
  • Native mobile
  • Pure WordPress or platform theming work
  • Anything where you need four engineers next Monday
  • Work where you need someone client-facing under their own brand

A real sequence, lowest risk first.

  1. 20-minute call

    You tell me what you’re stuck on or what you keep turning down. I tell you honestly whether I’m the right person. No deck, no discovery process.

  2. Paid trial engagement

    We start with one scoped piece of work — usually one to two weeks, fixed fee. You see how I work before either of us commits to a month, and you get shippable work either way.

    The lowest-risk way to start. A trial can close in days.

  3. Monthly retainer

    If it worked, we set a monthly capacity block. Predictable for your forecasting, predictable for mine. 30 days notice on either side.

  4. Standing capacity

    Over time I learn your codebase, your clients, and your standards, and you stop scoping every request from zero. Most agency relationships get cheaper to run in month four than month one.

Monthly capacity, priced in the open.

Bought as capacity, not hours. Commit to more and the effective rate drops. Most agencies land on Delivery.

Support

$4,000/mo

Capacity
~1 day / week
Best for
Maintenance, small features, being on call for the hard question
Response
2 business days
Includes
Async Slack access, code review

Delivery

Most common

$7,500/mo

Capacity
~2 days / week
Best for
An active client project with a real roadmap
Response
Next business day
Includes
Everything in Support, plus architecture and scoping

Embedded

$10,500/mo

Capacity
~3 days / week
Best for
Multiple concurrent projects or a long build
Response
Same day
Includes
Everything in Delivery, plus client-call availability under your brand

Not ready for a monthly commitment?

Overflow blocks: 20 hours at $150/hour, used within 60 days. Good for a single stuck feature or a second opinion on an architecture decision. Most agencies start here or with a trial engagement, then move to a retainer once the work is steady.

Unused capacity doesn’t roll over. Retainers are invoiced on the 1st, net 15. 30 days notice to pause or end, from either side.

Proof you can’t manufacture.

Faultline

An incident management platform I designed, built, and operate solo — ECS service health checking across customer AWS accounts via cross-account IAM, SQS worker pools, flap suppression, and circuit breakers. Live in production at fltln.io.

This is the level I work at when nobody is checking: production infrastructure, real failure modes, real customers.

See the architecture
  • Python
  • FastAPI
  • TypeScript
  • React
  • SvelteKit
  • Node
  • PostgreSQL
  • AWS
  • Docker
  • Terraform

Recent independent client work includes ROCO Films (WooCommerce site, ongoing maintenance) and Kimmie’s Cleaning Service (Shopify Functions discount engine, ongoing retainer).

The awkward questions, answered.

Will my client know you exist?

Only if you want them to. Default is no — I use your email address, your PM tool, and your brand. I’ve signed NDAs and white-label agreements before and I’ll sign yours.

What if we need you and you’re booked with another agency?

I hold capacity for retainer clients, which is what the tiers are actually buying. If you’re on Delivery, your two days are yours whether or not you use them. I cap total retainers at three so this stays true.

What happens if you get hit by a bus?

Everything is documented, in your repo, using your conventions — not in my head. If I disappear tomorrow, your team or your next engineer picks it up from the README and the commit history. That’s a condition of how I work, not a favor.

Can you talk to our clients?

Yes, on the Embedded tier, as a member of your team under your brand. I don’t hand out cards and I don’t take side conversations.

Do you sign non-solicits?

Yes. I’m not building a client list out of your relationships — I have my own practice, and poaching would end it.

What’s your notice period?

30 days either direction. I’d rather you leave easily than stay reluctantly.

Twenty minutes, no deck.

Tell me what you keep turning down and I’ll tell you whether I can take it.

Book a call

Or email direct: [email protected]