# From AI prototype to a usable release

Prepared by Joel Mathers, MathersLabs. Reviewed 17 October 2026.
https://matherslabs.com/solutions/ai-prototype-to-production

Use this as a scoping worksheet. It is not a security certification or a universal launch gate. AI tools can help implement and test these behaviours; someone must define the expected outcomes and inspect the evidence.

For each relevant item, record: expected behaviour / observed result / evidence / owner / next action. Mark items not applicable with a reason.

## Product boundary
- [ ] Name the first real user and the one journey they need to complete.
- [ ] Define what must work for release and what is explicitly deferred.
- [ ] Replace sample data and demonstrate the journey using realistic inputs.

## Accounts and permissions
- [ ] Test with two separate organisations and different staff roles.
- [ ] Try direct record/file access, not just the visible navigation.
- [ ] Confirm removed users and expired invitations lose the expected access.
- [ ] Keep secrets out of browser bundles and logs.

## Data and business rules
- [ ] Validate important rules on the server, including prices and ownership.
- [ ] Handle invalid, empty, long, duplicate and unexpected inputs.
- [ ] Preserve the version of information that was accepted or approved.
- [ ] Agree exports, retention, backup and restoration where applicable.

## Failures and integrations
- [ ] Double-submit a request and inspect duplicate records or charges.
- [ ] Interrupt a connection and verify retry/recovery behaviour.
- [ ] Simulate a failed external service and show a truthful status to the user.
- [ ] Decide who receives alerts and who can repair or replay failed work.

## Interface and usability
- [ ] Identify the main action and remove competing visual emphasis.
- [ ] Use consistent typography, spacing, colours and components.
- [ ] Check empty, loading, error, success and disabled states.
- [ ] Test narrow mobile screens, long content and keyboard navigation.
- [ ] Check that success messages correspond to completed system actions.

## Release and ownership
- [ ] Reproduce the build and staging setup from documented instructions.
- [ ] Confirm ownership and access to code, hosting and third-party accounts.
- [ ] Rehearse deployment and a suitable recovery/rollback procedure.
- [ ] Name the person responsible for incidents and ongoing maintenance.

## Decide the next step
Continue yourself when you can verify the relevant behaviour within your time and risk constraints. Commission a focused review when the uncertainty is specific but unresolved. Scope an implementation when the required outcome and acceptance checks are clear.

Bespoke MathersLabs implementation starts from £3,000. Diagnostic reviews are scoped separately. Bring the completed worksheet to https://matherslabs.com/contact rather than commissioning an unspecified rewrite.