Key takeaways
- Owning outright means you receive the source code, prompts, credentials and a walkthrough, with 30 days of free maintenance after handover.
- No vendor lock-in: host it anywhere, change it anytime and keep costs predictable.
- Ownership also means responsibility for hosting, updates and monitoring. Choose it when you have, or can hire, the technical capacity.
- A managed monthly plan is still available. The right answer depends on who you want carrying the day-to-day.
What “own it outright” includes
When you choose this option, the project is delivered as a complete handover, not a login to someone else’s platform. You receive:
- Source code in a repository you control
- Prompts and configuration for any AI components, so the behavior is yours to inspect and change
- Credentials and access transferred to accounts you own
- A walkthrough and documentation covering how it works and how to run it
- 30 days of free maintenance after handover, so early issues are on us
The exact terms are written into your proposal, so there are no surprises about what is and is not covered.
Why ownership matters even more with AI
Renting automation is convenient until something changes outside your control. With AI systems that list is long:
- Platforms raise prices or retire features you depend on
- Model providers update, reprice or deprecate the models your prompts were tuned for
- A vendor’s terms, hosting region or data handling shift, and your compliance team has to react
- A vendor is acquired, pivots or shuts down
Owning the code and prompts means none of those events can strand you. You can host it anywhere, switch model providers when it makes sense, modify it anytime and never depend on a single vendor. It also keeps long-term costs predictable, because you pay for infrastructure and usage you can see rather than a bundled subscription. And because the data lives in your own infrastructure, privacy and AI governance conversations get a lot simpler.
Own vs managed: how to choose
| Question | Own it outright | Managed monthly |
|---|---|---|
| Upfront cost | A one-time project price, agreed up front | A setup fee, then a flat monthly cost |
| Ongoing cost | Your hosting and usage, plus any support you choose | A predictable monthly amount |
| Who maintains it | You, or whoever you hire | We do |
| Who gets the 3am alert | Your team | We monitor and respond |
| Flexibility | Maximum: change anything, host anywhere | High, within the agreed scope |
| Best for | Teams with technical capacity and a strong need for data control | Teams who want it to just work |
What you take on when you own it
Ownership is a trade: you gain control and give up the safety net of someone else running it. Be honest about the day-to-day:
- Hosting and uptime: keeping the service running
- Updates: API changes, library upgrades and model changes
- Monitoring: noticing when it breaks, ideally before customers do
- Security: patching, rotating secrets and controlling access
Our honest take
If nobody on your team is comfortable looking after a small piece of software, a managed plan is probably the better fit. If you have that capability, or a developer you trust, owning it outright is hard to beat.
What the 30 days of free maintenance are for
The first month in production is when real-world surprises show up: an edge case nobody mentioned, a connected app that behaves differently from its documentation, a small adjustment the team wants once they see it working. The free maintenance window means those early issues are looked after by the people who built it, while the context is still fresh. Your proposal spells out exactly what it covers.
How to prepare for a smooth handover
- Name a technical owner, even if it is a part-time responsibility
- Create the cloud, repository and API accounts the project will live in
- Decide where secrets will be stored and who can access them
- Plan basic monitoring so you hear about failures
- Book time for the walkthrough with the people who will run it
Not sure whether to own or rent? How we price automation explains the options, and the free audit helps you decide with real numbers.
Frequently asked questions
What do I actually receive when I own the automation?
You receive the source code, the prompts and configuration, the credentials and access, and a walkthrough with documentation, along with 30 days of free maintenance after handover.
Do I need a developer to own it?
Not a full-time one, but someone has to look after hosting, updates and monitoring. If you do not have that person, a managed plan or a separate support arrangement may suit you better.
Can I move to a managed plan later?
That is worth discussing when we scope the project. We are happy to talk through ongoing support separately if your needs change.
Are the code and prompts really mine?
Yes. The point of owning it outright is that the code, prompts and credentials are yours, so you are not locked in to us or to any single platform.