Product venture
inwrk.ai
Captures tasks, leads, and decisions from WhatsApp groups without changing how your team talks. Bootstrapped until product-market fit is clear.
Founder, inwrk.ai · advisor on engineering systems at scale
I build software.
Right now: inwrk.ai. I write about where product and engineering slow down after product-market fit, and what to change when delivery gets heavy.
Selected work
Case studies and writing on how product, engineering, and governance stay aligned as teams scale.
Featured case study
Milkbasket
In early 2017, I joined Milkbasket as an advisor to the CTO during a period of early growth. The product had already launched and demand was increasing. Much of the engineering work, however, had been delivered through external vendors rather than an internal engineering team. This approach had helped the…
Read case studyCase study
CARPL.ai
CARPL.ai develops an AI platform for radiology workflow automation and clinical quality improvement. The company was expanding its product capabilities and exploring opportunities to deploy the platform across external ecosystems, including integrations with organizations such as GE. I joined the company for a six-month period to help stabilize engineering operations,…
Long-form
The Engineering Reset Method
A practical method for resetting product engineering systems when they begin to slow down after product–market fit.
What I'm doing now
One venture build and two bounded advisory offers. Methods and write-ups are linked from each block.
Visit inwrk.ai
Engineering Reset
A 30-day diagnostic and optional 90-day reset when engineering slows after product-market fit: align product, engineering, and governance so founders stop arbitrating every decision.
Example: Milkbasket case study
Agentic Engineering
A focused sprint for teams already using Cursor, Codex, or Claude Code:
- Human and agent workflows with clear ownership
- Review standards matched to your risk profile
- Guardrails so throughput stays predictable
How I work
I stay hands-on when it creates leverage: unblocking a critical path, setting a standard, or shipping work only I can own. I step back when the work starts to route through me instead of the system.
Early growth often needs founder intensity. Sustained growth needs clear ownership, fewer parallel bets, and decision rights that do not sit with one person by default.
Get in Touch
If you're building something serious and want to exchange notes, or if your engineering systems need a reset, reach out.