Three client questions
Clients ask three things. Can I see it before it goes live? Which version is live, and what changed? And if it goes wrong, how fast can you go back? Each answer needs a mechanism, not a promise. A preview answers the first, a numbered release with a changelog answers the second, and a rehearsed rollback answers the third, with the honest limit that a rollback restores code, not data or settings.
Choose by what is missing
If clients review from screenshots, start with automatic previews for every pull request, from £695, which use test settings and give fork pull requests no secrets. If versions are chosen by feel and notes are written from memory, release automation from £595 computes the version from agreed rules and records one tag per release. If nobody has tried going back, a rollback rehearsed on staging starts at £595. Each is untested, covers one repository or service and is paid after you sign off.
Or all three, in order
Delivered together, previews come first, then versioned releases, then a rollback that points at releases the pipeline has named, as one project from £2,250 after a quote, which adds an end-to-end run-through on staging and one combined handover. It needs a staging environment separate from production, a host or CI route that supports previews and a person on your side who holds deploy credentials. We rehearse on staging and never run anything on production. A monthly rehearsal at £395 a month can then check that the release path still works.
What to send first
Describe how a change reaches the client today, where staging is and what the host is. Do not send credentials, code or client data. Prices are published test prices for services we are launching; this page does not show that agencies have asked for them. A separate one-feature preview job exists for a single new feature in a private preview, and is a different offer.
Sources and limits
- Vercel environments Checked 2026-10-11.
- A preview deployment is created for pull requests and non-production branches.
- GitHub environments Checked 2026-10-11.
- Environment protection rules, such as required reviewers, must pass before a deploying job runs.
- Conventional Commits 1.0.0 Checked 2026-10-11.
- Commit types map to patch, minor and major version increments.