Outputs, outcomes, and how I work.
I don't need a
job description.
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.
Numbers, not narratives.
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.
Spec → backend → frontend → infra → ship. No handoffs, no waiting on someone else's queue.
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.
Not demoware. Auth, infra, monitoring, payment rails ready. Plug into real users on day one.
Plnr · Zenox · MemContext · and counting. Built, published, maintained — used by real developers.
Shipped fast. Still running.
MemContext is the flagship. The rest are real plugins and production-ready apps — built end-to-end, all live.
This is the deal.
Four principles. They show up in every project I ship.
AI-first, not AI-enabled.
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.
Ship first. Polish in production.
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.
No tickets. Just outcomes.
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.
I own the whole stack.
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.
More than the code.
The work doesn't end at the IDE. Here's the other half of how I show up.
More than the code. I ship internal tools for the team, and I'm a team player.
I build the team's tools.
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 lift the team.
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.
People over frameworks.
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.
Work History
Building scalable solutions and leading development teams
Kakiyo OÜ
CurrentChief Technology Officer
Lead Developer
Full Stack Developer
- ●Migrated millions of rows from Appwrite to PlanetScale.
- ●Lowered latency from 2.8 seconds (P50) to 20 ms (P50) and 90 ms (P90).
- ●Removed latency bottlenecks across critical user flows.
- ●Crafted end-to-end features from product requirements to production rollout.
- ●Created the hiring pipeline for the company.
- ●Managed the team across delivery, reviews, and technical direction.
- ●Reduced the overall infrastructure cost by 50%.
Roles I take.
Not tasks. Not tickets. The whole engineering function — for as long as you need me there.
Fractional CTO / Founding Engineer
The default engagement. I take ownership of the engineering function — architecture, hiring, reviews, AI direction, infra. Deeply embedded, long-term. Your team treats me like a co-founder.
Zero-to-MVP
First engineer in. Idea → live product in weeks, not quarters. Full stack, AI included, shipped to real users. No deck. Just code.
Build your AI layer
Own the AI surface end-to-end. Agents, RAG, tool calling, MCP, the observable infra around models. Production-grade, not demoware.
Take over a stalled engineering function
When shipping has stopped, I come in, find what's broken, kill the dead weight, and get the team moving again in weeks.
Strategic plugin & integration work
When the leverage is high enough to justify it — MCP servers, CLIs, IDE plugins. I've shipped Zenox, Plnr, and MemContext on this pattern.
I ship every day.
What I actually shipped. Live, public, every day.
“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.
Book a 30-min call
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.
- No sales pitch, no roadmap theatre
- Concrete next steps you can run with
- Honest take on scope, time, and trade-offs