AI Built Your Business App. Who Maintains It?
Oracle's new application-composition announcement makes creation easier to imagine. UK businesses still need a plan for ownership, access, testing and the awkward second year.
Operations leaders and software buyers
5 min read
30 October 2026
2 sources
Define
Workflow + owner
→Build
Small first version
→Test
Roles + exceptions
→Operate
Support + backup
→Exit
Export + recovery
The app needs a maintainer and an exit route as well as a first release.
The prototype proves that a screen can be made. The operating model proves that the business can depend on it.
- 01Choose a small workflow with an owner and stable data.
- 02Test permissions, exceptions and recovery before real users depend on it.
- 03Price support, changes and an exit route as well as initial generation.
A faster route to a first application
Oracle announced App Composer on 27 October as part of its OpenAI collaboration. Oracle says users can build applications with Codex, connect approved data and workflows, and use managed deployment and lifecycle controls. Those are product claims; buyers should verify availability, pricing, generated artefacts and operational responsibilities in their own contract.
A UK facilities company might use a generated app to track site inspections. The first screen can be built quickly, but its value depends on whether an inspector can work with intermittent connectivity, correct a mistake and find the latest approved checklist.
Ask what happens on a difficult day
Map the real workflow before generating it: who creates an inspection, who can amend it, what evidence is retained, and what happens when a site is closed. Test duplicate submissions, missing photographs, changes in staff roles and a lost connection. These edge cases determine whether the app replaces a spreadsheet or adds another reconciliation task.
Give the application a named business owner and a technical maintainer. Require source or an understandable representation, deployment instructions, a test suite proportionate to the risk, backup and a documented way to export data. Confirm which components and licences remain necessary to run it.
Budget for the second year
Compare build and run costs over a realistic horizon: licences, hosting, monitoring, fixes, access reviews, data migration and changes to connected systems. A prototype that saves two weeks of initial work can still be expensive if every small change needs specialist intervention.
Use a pilot with real, non-sensitive or appropriately protected data and measure completion time, error correction and support requests. Expand only when the owner can explain who responds to failures and how users recover their work.
Use this before approving the work.
- 01Name business and technical owners before release.
- 02Test access, offline behaviour and exception handling.
- 03Document backup, deployment and data export.
- 04Compare ongoing support costs with the existing process.
Research and references supporting this article. Interpretation and recommendations are Thalenor’s.
The facilities-company scenario is illustrative; feature availability and commercial terms may differ by customer.
Published and reviewed on 30 October 2026. This article provides general technology and operational information, not legal, tax, medical or regulatory advice.