Four questions. Each one saves you money.
Every engagement starts with the business problem, not the technology. Find your question below.
“Should we build this?” “What are we missing?” “Why isn’t this working?” “Is it still working?”
Someone’s pitching a technology or AI project. Maybe a vendor, maybe your own team. You need to know: is this real, or hype?
- A clear yes, no, or not yet, with the reasoning
- Written evaluation: business case, technical feasibility, data readiness, organizational fit
- What needs to be true for it to work, or the reasoning to explain a no
- You’re being pitched an AI solution and can’t evaluate the claims
- Your team wants to build something and you don’t know if it’s worth it
- You need someone technical in the room who isn’t selling anything
You’re about to make a big technology bet: an acquisition, a platform choice, build or buy. Your team has a recommendation, but you’re not sure you’re seeing the full picture.
- Independent technical assessment: what’s sound, what’s risky
- Architecture, technical debt, and scalability for acquisitions
- A clear analysis of trade-offs and a recommendation you can act on
- You’re doing due diligence on an acquisition
- You’re making a major platform decision
- Your team is too close to the problem to see it clearly
You launched something and it’s not delivering, or a project stalled and nobody can explain why. Nobody wants to be the one who says “this might not work.” That’s what I’m for.
- Root cause: technical, organizational, or strategic
- A clear call: fix, pivot, or kill
- The action plan, or the cost analysis to make the call without finger-pointing
- An initiative is behind schedule and nobody can explain why
- You shipped something that isn’t delivering
- You suspect the answer is to kill it and need the data to back it up
Your technology investment is live. It’s working, you think. Most teams can’t answer whether their systems are better or worse than last month with actual data.
- A measurement system built for your specific application
- Scoring logic, thresholds, and an integration plan for ongoing monitoring
- The ability to answer “better or worse than last month?” with data
- You can’t answer “how do you know it’s working?” with data
- You find out about performance problems from user complaints
- You’re reporting AI results to a board and need numbers you trust
For mid-market companies that need senior technical leadership but aren’t ready for a full-time hire. I work two to three days a week with your team on architecture decisions, engineering team development, vendor evaluation, and technology strategy. Weekly check-ins, ad-hoc decision support, and a direct line when something urgent comes up.
I take on a small number of these engagements at a time. The goal is to build your technical capability so you don’t need me anymore.
Limited availability · Quarterly commitment · When do you need a fractional CTO? →
No pitch, no discovery script. You describe the decision; I tell you honestly whether I can help.
You know the cost and the timeline before we start. I’ll push back if the scope doesn’t match the goal.
Not a list of options. A clear call you can act on, with the reasoning behind it.
Get my thinking in your inbox — one idea per issue, no spam.
Three a week: the Tuesday newsletter, Foto Friday, and Sunday’s Weekly Intel. No spam. Unsubscribe anytime.
If any of this sounds like where you are, let’s talk. Get in touch →
Colorado Front Range · In-person and remote · Schedule a call