- AI
- Fractional CTO
- Software Architecture
- Technology Strategy
Code Got Cheap. Judgment Didn't.
AI made writing code fast and cheap. It didn't make deciding what's worth building any easier — and that's where most technology budgets go to die.
Workshop Blog
Practical notes for founders and operators making consequential decisions about software, products, and AI.
The model is rarely what makes the difference. Where AI belongs in a service business, and the work around it that keeps your operations running.
Most technology projects fail before anyone writes code. Here are the five judgment mistakes we see most often, and how to avoid them.
Every technology partner says they start with discovery. Six checks tell you which ones investigate your business and which ones are just selling.
A developer will happily quote you an app for a process nobody has written down. That's the problem.
Your technicians finish the job, then finish it again at a desk. That second pass is where details go to get forgotten, mangled, or never written down.
Every time your team uses a public AI tool for real work, your data takes a trip you didn't plan. Private AI is the version where it doesn't.
Someone on your team has probably pasted something sensitive into ChatGPT or another public AI chatbot. Nobody told you, and there's no log to check.
AI made writing code fast and cheap. It didn't make deciding what's worth building any easier — and that's where most technology budgets go to die.
Straight talk on software design, product development, and AI — written from the work, not for the algorithm.