The University of Bristol’s Temple Quarter Enterprise Campus sits next to Temple Meads station. The university reported completion of the main construction phase on 11 May 2026. For a Bristol team developing a product, the practical question is what separates a promising demonstration from a service that another person can use, support and maintain.
What can be kept from the prototype?
A code review establishes which parts can support the first release. It checks whether a new developer can reproduce the build, how accounts are created and recovered, where secrets are stored and what happens when a dependency fails. Each finding becomes a concrete decision: keep, repair or replace. You receive that assessment before deciding on the larger development step.
Privacy starts with the data map
The data map records what is collected, why it is needed, where it goes and when it is removed. The UK regulator, the Information Commissioner’s Office, explains that data protection by design is a controller responsibility throughout the lifecycle. A software supplier is not automatically a processor: the actual processing arrangements determine the role. For this project, those arrangements are written down alongside access permissions, retention settings and the services used to operate the app.
A first release needs a bounded journey
The first release follows one complete user journey, including its failure paths. For example, a booking feature needs cancellation, interrupted payments and confirmation delivery as well as its happy path. The agreed acceptance criteria describe these cases in ordinary language. Anything outside that scope is priced as a later decision, so a new idea does not silently expand the current step.
Make the handover reproducible
Handover includes the build instructions, deployment process and account inventory needed to run the delivered version. A release is tagged in your repository, configuration is documented and secrets are kept out of source code. If your own developer takes over, the documentation gives them a starting point for rebuilding and operating that version.
Choose the starting point
A prototype starts with review; a defined new workflow can start with a First Version.
- Existing code to assess: App Check at $2,000
- A stalled build to recover: rescue from $27,800
- A new service to validate: First Version (MVP) from $27,800
Read the UK overview for the working arrangement. Local context: University of Bristol campus update; privacy guidance: ICO: data protection by design.