Technical decisions set the ceiling. I help founders raise it.

I work with Seed–Series B founders at technical inflection points, helping teams of 2–20 engineers make better architecture and org decisions in 30–90 days.

Sound familiar?

Your engineers are stuck rewriting the same system

Every roadmap discussion turns into a debate about technical debt, but nobody can agree on what to build instead.

You don't trust your architecture under scale

You're about to raise a Series B or enter a new market, but you're not sure your current system can handle 10x the load.

You're hiring but don't know what to hire for

Your team disagrees on whether you need a senior backend engineer, a data platform lead, or an ML specialist.

You're exploring AI but unsure where to start

Everyone says you need an AI strategy, but you can't distinguish real opportunities from hype.

What changes after 30–90 days

Your architecture supports 10x scale without rewrites

Clear direction on what to build, what to buy, and what to ignore—validated against your actual growth trajectory.

Your team aligns on a clear technical direction

Engineers stop debating first principles and start shipping. Decisions stick because everyone understands the reasoning.

Your hiring plan matches your actual system needs

Job reqs tied to concrete technical gaps, not vague feelings about what "strong companies" have.

You stop debating worst-case outcomes

Technical decisions anchored in real data and trade-off analysis, not fear and hypothetical scenarios.

How I work with you

Weeks 1–2: Diagnose

I embed with your team—sit in standups, review architecture docs, interview your engineers. I map your technical reality against your business goals and identify the 2–3 decisions that matter most.

Weeks 3–4: Decide

I facilitate architecture and org decisions with your founding team. We document the reasoning, trade-offs, and rationale so the decisions outlast my engagement. I own the facilitation; you own the call.

Weeks 5–12: Drive execution

I stay embedded as your technical partner. I run architecture reviews, unblock engineering decisions, and help you hire against the plan we've set. I influence daily execution; you retain full control.

What I own vs. influence
  • Own: Architecture facilitation, technical decision frameworks, hiring strategy, AI readiness assessment
  • Influence: Daily execution, code reviews, sprint planning—your team runs these
  • Never: Rewrite your codebase without consensus, make unilateral hiring decisions, bypass your founders

Engagement models

Technical Reset
30 days

Diagnostic engagement. Deep architecture review, decision audit, and actionable roadmap. Ideal for founders who need clarity before a fundraise or major pivot.

Architecture + Org Rebuild
60 days

Facilitate major technical decisions and restructure your engineering org. Ideal for teams scaling past 10 engineers or entering new markets.

Scale Readiness
90 days

Full technical partnership through a scaling inflection point. Architecture, org, hiring, and AI strategy. Ideal for Series B prep or post-raise execution.

Fractional engagements limited by design for high-touch involvement.

Technical depth, practical pressure.

Stanford CS, Georgia Tech MS, early patent on vector embedding architectures that now run modern AI. Kauffman Fellow.

First software engineer to VP at Bellwether Coffee, through $100M raised. Scaled 0→18 engineers across 12 countries while shipping production systems across 3 continents.

I specialize in AI-native architecture, agentic systems, and LLM-backed applications— not classic CTO advisory. I embed with founding teams where technical decisions carry existential weight. I don't hand over a deck. I sit in the room.

Ready to raise your ceiling?

Schedule a 45-minute technical review. We'll map your inflection points and decide if there's a fit.

Apply to work together