Outputs, outcomes, and how I work.
Tell me the outcome. I'll ship it.
AI-first engineer. CTO at Kakiyo. I build crazy fast, iterate in production, and ship custom plugins for every tool I use. Best fit for founders who don't write tickets and judge on what's live.
What I've shipped, who's paying for it, and what changed because of it.
Cut response times from 2.8s to 20ms (P90: 90ms). Same product, completely different feel.
Rearchitected the stack at Kakiyo, halved the monthly cloud bill.
Owned features from product spec to production rollout. Frontend, backend, infra, the whole loop.
Moved live production data from Appwrite to PlanetScale without dropping a single request.
Full Stack Dev → Lead Developer → Chief Technology Officer. Promoted twice in under a year.
Every product I ship is production-grade — clean codebase, auth, infra, and the rails to plug a payment provider in tomorrow.
Plnr · Zenox · MemContext · and counting. Built, published, maintained — used by real developers.
MemContext is the flagship. The rest are real plugins and production-ready apps — built end-to-end, all live.
Four principles. They show up in every project I ship.
I don't just use AI tools — I build the plugins, agents, and CLIs that extend them. Zenox for OpenCode, Plnr for codebase planning, MemContext for any MCP client. If a tool I use is missing something, I ship the extension myself.
I'd rather have it live and rough than perfect and unreleased. Real users teach you more than planning sessions ever will. Iterate against feedback, not against assumptions.
Tell me the user problem and the constraints. I'll handle scope, architecture, and trade-offs. Skip the JIRA ceremony — give me a definition of done and I'll get there.
Frontend, backend, infra, AI integrations, code review, hiring. I work like a founding engineer because that's how startups actually win. Specialization slows founders down.
The work doesn't end at the IDE. Here's the other half of how I show up.
I'm not just into tech. I love building internal tools for the team, and I'm a team player.
Admin dashboards, hiring pipelines, code review workflows, deploy scripts, internal APIs. If something is slowing the team down, I'll automate it before anyone files a ticket.
I review code, mentor juniors, write docs that don't suck, unblock teammates daily. I work like a co-founder, not a contractor — your team becomes my team.
Users, teammates, founders — they matter more than the framework du jour. I optimize for what actually works for them, not what trends on Twitter this week.
Building scalable solutions and leading development teams

Pick one. Or all of them. I work end-to-end.
Idea to live product in weeks, not quarters. Full stack, AI included, shipped to real users — not a Figma deck.
Agents, RAG, tool calling, MCP, the infra around models. Production-grade and observable — not demoware.
MCP servers, CLIs, IDE plugins, browser extensions. I extend the tools your team already lives in.
Take over, stabilize, ship. I'll find the bottlenecks, kill the dead weight, and unblock the team in weeks.
Deeply embedded, long-term. Architecture, hiring, reviews, infra, AI direction — the whole engineering function.
No LeetCode theatre. Just GitHub — the only proof that actually matters.
“If you're a founder
building something real,
let's talk.”
30 minutes. No deck needed. Just bring the problem and what done looks like — I'll handle the rest.
Tell me what you're building, where you're stuck, and what shipping looks like. I'll tell you exactly how I'd approach it — whether or not we end up working together.