For founders
Taking select clients

Need a technical partner for your backend?

I help early-stage founders build and scale their technical foundation. I own architecture, implementation, and deployment so you can focus on product and growth, and I stay accountable for how it holds up as you grow.

01What I help with

What I help with

  • MVP architecture that won't collapse at first traction
  • Scaling preparation: what to fix before it becomes a fire
  • Refactoring fragile systems without full rewrites
  • Backend technical leadership when you don't have a CTO
02How I think

How I think

  • 01Every decision has a tradeoff. I make them explicit so you can choose.
  • 02Optimize for change. Early-stage means pivots, so the architecture has to flex without falling over.
  • 03Reduce risk before it becomes a crisis. Technical debt costs more the longer you carry it.
  • 04Think in failure modes. What happens when this breaks? When traffic spikes? When you need to refactor?
  • 05Ship fast, but avoid the mistakes you can't undo. Some shortcuts are cheap; others cost you for years.
03Engagement models

Engagement models

01

Project-Based Backend Builds

MVP backend, new service, or major feature. Fixed scope, clear deliverables. I own the architecture and implementation from design to deployment.

02

Ongoing Technical Ownership

Retainer for architecture decisions, code reviews, and hands-on work. I become your technical partner. Available for questions, reviews, and critical path work.

03

Architecture Audits

One-off review of your system. I identify risks, bottlenecks, and improvement opportunities. Deliverable: a report with prioritized recommendations.

04Not a fit if

Not a fit if

  • You need someone to implement specs without technical input
  • The work is primarily frontend-focused
  • There is no clarity on goals or expected outcomes
  • Decisions are driven purely by speed without considering long-term impact
05Working together

What working together looks like

  1. Week 1

    Map your product constraints, business risks, and technical debt.

  2. Week 2

    Architecture proposal with clear system boundaries and tradeoffs.

  3. Weeks 3-4

    Implement core foundation and observability.

  4. Month 2+

    Stabilize, refine, and scale responsibly.

06Contact

If this sounds like a fit.

I work with a small number of founders. Send me an email with what you're building and what you need.

Not hiring, just curious about the work? See the products & systems