Still working next year.
An optional monthly care plan for the systems we built, so they keep doing their job after launch and someone is responsible for them besides you.
What you'd rather I handle
Hosting and monitoring
The system stays up, backed up and monitored, with someone responsible for noticing when it isn't.
Updates
Dependencies, security patches and the small changes that keep a system matching the business as it moves.
AI workflow upkeep
Where AI does part of the work, the prompts, models and exception handling are reviewed monthly. Models change, inputs drift, and someone has to notice.
A standing monthly call
What's working, what's annoying, what's next. Short, regular, and logged like everything else.
What optional means in practice
Documentation and a handover are standard build deliverables, so the care plan starts from a system that someone else could already run. Everything lives in your accounts. If you take it in-house, or to another provider, nothing has to be rebuilt and nothing has to be asked for.
Monthly, no fixed term. Stay because it's useful, not because it's hard to leave.
How every engagement works
- A fixed price, agreed in writing before any work starts.
- Everything discovery produces is yours to keep, whether or not we continue.
- You own the code, the data and the accounts it runs in.
- The care plan is optional, and if a smaller piece of work answers the question, that's what I'll propose.
Questions people ask
Book a call
A free call of twenty to thirty minutes about the problem, the rough scope, whether it fits, and what the next step would be. If it isn't a fit, I'll say so.
Book a call