writing
What happens after the app ships.
Notes on taking founder-built software into production, deciding what AI may safely change, recovering systems somebody else built and knowing who to hire.
Your AI-built app has paying users. What changes now?
The production controls a founder-built SaaS needs once customers, payments and private data make every release consequential.
The developer left. How to take over a live SaaS without breaking it
A controlled handover process for a live SaaS whose original developer, contractor or agency is no longer responsible for production.
What can AI safely change in a live app? A green, amber and red framework
A system-specific way to decide which AI-assisted changes a founder can ship, which need review and which require senior ownership.
A backup is not a recovery plan until someone tests the restore
A practical restore test for a live SaaS, including data, files, configuration, external services and the route back to a working application.
Should you rewrite your vibe-coded app? A rescue-or-rebuild decision tree
A practical way to decide whether an AI-built application should stay, be stabilized, be replaced in phases or be rebuilt.
Developer, technical advisor, fractional owner or CTO: who do you actually need?
A founder's guide to choosing implementation capacity, occasional advice, recurring technical ownership or full-time technology leadership.
What it costs to make an AI-built app production-ready
A published-price model for separating a contained fix, technical ownership, finishing the app and a rebuild.
You run the business. I own the technology behind it.
Reading about it is one option. Handing it over is the other. Thirty minutes, no access needed, and the prices are published.