Writing
I write about the part of delivery that happens after the software works: who owns a system once the project ends, where exceptions really go, and why perfectly good implementations quietly fail to land. The decisions I got wrong are in here too, because those are the ones worth reading.
The software is rarely the problem. Three structural failure modes that repeat everywhere, the reason ownership is standing rather than a job title, and the one signal that tells you a rollout actually took — which no adoption dashboard can measure.
The most expensive decision in a revenue cycle programme is usually the fastest one made. What a demo cannot show you, why switching later costs months of payer-by-payer re-enrollment, and what I would measure instead if I were choosing again.
Start a conversation
I work with SaaS companies, software teams, agencies, healthcare organisations and growing businesses that need clearer coordination and reliable follow-through from planning through delivery.