CTO judgment, when you need it
A second opinion from a CTO who's been there.
Start with a free call. It takes 20 minutes. Tell me what's going on and we'll figure out if we're a fit. If we are, you get decisions like this one instead of a report that runs 40 pages.
Don't rewrite.
A few services cause most of your bugs. Fix those first. You'll start shipping faster in a couple weeks.
Example question. Details changed.
Straight answers to expensive questions.
The questions founders bring me most often, and what I usually end up telling them.
“Should we rewrite this app?”
Probably not.
Rewrites take 3x longer than planned. There is almost always a cheaper path.
“My devs aren't fast enough.”
Maybe, or your features are too big.
Slow teams usually have a sizing problem before a people problem.
“Should we move to microservices?”
Not yet.
Microservices solve a scaling problem. Most teams adopt them years too early.
“AI writes half our code. Is it safe?”
As safe as your guardrails.
AI and humans both ship bugs. Tests, reviews and knowing which parts can't break matter more than who typed it.
“We're hiring a senior engineer. How do we tell if they're good?”
Ask them to cut a feature in half.
Strong seniors make the problem smaller before they write any code. Watch what they keep.
“Should we build this or buy it?”
Buy it, unless customers pay you for exactly that.
Every tool you build is one more system your team has to keep running.
Your answer depends on your team, runway and stage. That's what a Deep Dive is for.
Everyone's busy. The roadmap still slips.
More tickets moving isn't more product shipped. When the roadmap keeps slipping while the board stays full, that's a question for a CTO, not a developer.
A task board with 9 tickets in progress, 6 in review and nothing shipped. A handwritten note says: this is the problem. 15 things in flight, nothing done. Finish before you start.
Bring the diagram. I'll mark it up.
Your situation is specific. Team size, runway and stage change the right answer. A repo, a diagram, or just the problem is enough to start.
What I help with
- Whether to rewrite
- Whether your devs are the problem
- Evaluating senior hires
- Breaking features down so they ship
- Quick fix vs. ideal fix vs. the right fix
- Where AI writes code and where humans own it
27 years of watching these decisions play out.
Rewrites that never shipped. Microservices nobody needed. The senior hire who looked great on paper. You don't have to learn these the expensive way.
-
1998
Started on EDI systems at Union Pacific Railroad.
-
The long middle
Fortune 500s, startups, the military and hedge funds.
-
2018
Built and sold a SaaS company.
-
Today
Helping founders make the call before it gets expensive.
His insights were invaluable, providing me with the confidence and peace of mind I needed to move forward. I highly recommend Kyle...
Kyle's advice is extremely valuable... We were lost and needed someone to tell us exactly where we can improve our process without fluffing things up... Kyle did exactly that...
Kyle brings the rare mix of strategic thinking, technical depth, and crisp communication. He jumped in fast and added value immediately.
How we can work together
CTO Deep Dive
$400 one time
90 minutes. Bring your architecture, codebase, technical problem or difficult decision. We'll work through it together and figure out what to do next.
Book a Deep DiveCTO Advisory
$1,200 / month
A session of 90 minutes every week. Four Deep Dives would cost $1,600.
Start with a diagnostic callFractional CTO
$3,000+ / month
Scoped to your company. Strategy, architecture, leadership and hands on technical execution when needed.
Start with a diagnostic callHow I think
A few of the opinions you'll be paying for.
Ready to stop winging it?
20 minutes. Tell me what's going on. We'll know if we're a fit.
Book a free diagnostic call