I work with founders on the redesign: engineering organizations, operating models, and AI-era workflows that hold up as the company scales.
Currently building inwrk.ai. Previously ran engineering resets at Milkbasket and CARPL.ai as an operator and advisor.
Full write-ups of past engineering resets — the friction, the intervention, and what changed.
Case study
From vendor-driven development to an internal team of ten-plus engineers owning the platform, within roughly a year.
Read case studyCase study
Sprint-based execution, documented architecture, and a platform narrative clear enough for partner and investor conversations.
Read case studyThe engineering organization that works from 10 to 50 people is rarely the one you need from 50 to 200.
A 30-day diagnostic of how decisions become shipped software, then a bounded 90-day reset — but only if the friction is structural. If it isn’t, you get a stabilization plan and we stop there.
For teams already using Cursor, Codex, or Claude Code. The issue is rarely tool access — it’s workflow design: how tasks become code, how AI output gets reviewed, and how teams stay coherent while shipping fast.
A two-to-four-week sprint that ends with a runbook, review standards, and a KPI baseline your team owns.
For services companies that want to build products. The hard part isn’t the software — it’s picking the right opportunity and validating it before you commit a team to it.
We evaluate the opportunity, write the product thesis, and build the execution plan together.
Current venture
inwrk captures tasks, leads, and decisions from WhatsApp groups without changing how your team talks.
This is my own startup — bootstrapped, and currently deployed with organizations whose critical business processes already run inside WhatsApp.
I’ve spent my career as a founder and operator, not a career consultant. At Milkbasket, I helped take engineering from zero internal engineers to a team of more than ten that owned the platform — in about a year. At CARPL.ai, I spent six months restructuring engineering execution and documenting the architecture ahead of platform partnerships.
Engagements are bounded by design: diagnostic first, reset only if the problem is structural, then exit. If the honest answer is that you don’t need me, that’s the answer you’ll get.
My operating philosophy is simple: early stages require founder intensity, sustained growth requires restraint. Most of my work is helping founders know which one the moment calls for.
Long-form writing on how product, engineering, and governance stay aligned as companies move through growth stage.
If you're navigating growth, an acquisition, or an engineering organization that isn't keeping up with the business, book a discovery call or email me directly.
Start a Conversation