I don't do
quick fixes.
I've been a CTO for 8+ years and I've learned one thing the hard way — there are no shortcuts in engineering leadership. Real change takes time. It takes someone who shows up consistently, earns the team's trust, and sticks around long enough to see the results.
That's what I do. I become your CTO — part-time, but fully committed. I sit in on your standups, review your architecture decisions, talk to your engineers, and tell you things you might not want to hear.
How I work
I use AI every day. My teams use AI every day. But I've also seen what happens when AI-generated code ships without anyone truly understanding it — things break in weird ways six months later and nobody knows why. So every decision that goes through me has a human behind it who can explain and defend it. That's non-negotiable.
I don't believe in "transformation frameworks" or 90-day plans that look great in a slide deck and fall apart on day 5. I believe in showing up, understanding what's actually going on, and making things better one decision at a time. Sometimes that means rewriting your deployment pipeline. Sometimes it means having a difficult conversation with a senior engineer. Often it means both.
Where the CTO fits
The CTO sits at the intersection of business and technology — responsible for technical vision, team structure, and making sure the right things get built the right way.
What I actually help with
Technology audit & architecture decisions
I look at what you have and help you figure out what you actually need — not what's trendy. This means reviewing your codebase, your infrastructure, your deployment pipeline, and your technical debt. I'll tell you what's solid, what needs fixing now, and what can wait. No 200-page report nobody reads — a clear, prioritized list of what matters.
Team assessment & hiring
Building the right team, not just a bigger one. I've grown teams from 3 to 50 people, and I know what works. I help you figure out if you need a senior backend engineer or a DevOps person, whether your team leads are in the right roles, and how to structure your engineering org so it doesn't fall apart at 20 people. I also help write job descriptions, review candidates, and sit in on technical interviews when needed.
Process improvement
The boring stuff that nobody wants to do but that makes everything else possible. How do you do code reviews? How do you handle deployments? What happens when something breaks at 2am? Do you have proper CI/CD or are people still deploying from their laptops? I help you set up the processes that let your team ship fast without breaking things — and more importantly, I help you kill the processes that are slowing you down for no good reason.
AI adoption that actually works
Not "let's sprinkle some AI on it" — a real strategy for where AI helps your team and where it creates more problems than it solves. I help you figure out the right tools, set up proper guardrails, and make sure someone's accountable for everything that ships. The goal is a team that moves faster with AI without losing the ability to explain and defend their own code. If you suspect your codebase already has AI slop, start with an AI Audit.
Vendor & agency oversight
I run a 50-engineer agency myself, so I know exactly what good delivery looks like — and what corners get cut when nobody's watching. If you're working with external developers, I can review their work, sit in on their demos, and tell you honestly whether you're getting what you're paying for. I've seen too many founders spend six figures on code that needs to be rewritten within a year.
Product roadmap & technical strategy
From MVP to scale, I've done it multiple times. I help you decide what to build next, what to defer, and what to kill. I help you figure out if you should build or buy, monolith or microservices, and whether that "quick refactor" is actually going to take three months. The goal is a roadmap that balances business needs with technical reality — not a wishlist that makes your investors happy but your engineers miserable.
Why me and not someone else
I'm not just giving advice from the sidelines. I co-founded mindnow, a 50-engineer digital agency that builds real products for real clients. I built seojuice.com from zero to 10K MRR with my own hands. I maintain open source projects with 5,000+ stars on GitHub. When I tell you something works or doesn't work, it's because I've lived it, not because I read it in a book.
And if you ever need more hands than just mine — I have an entire team behind me.
Where this ends
My goal is to make myself unnecessary. We build a solid product together, create a 6-12 month technical roadmap, and eventually I help you find and onboard a full-time CTO if that's the right path. I'm not here to create a dependency — I'm here to plant something that can grow on its own.
Some clients work with me for 3 months and then they're set. Others keep me on for a year or more because the value compounds over time. There's no right answer — it depends on where you are and what you need.