Name the flows and what "working" means
Write down the three to five journeys that earn or keep customers: signing in, signing up, the main form, an incoming integration, the main screen. For each, write one sentence of what a test user does and one of what they should see. If you cannot write the sentence, that flow is not yet specified, and that is the first finding. A list like this is the unit of every job we offer in this area.
- One flow, one sentence of action, one sentence of result.
- Mark which flows involve money or personal data: they need extra care and sometimes a separate scope.
Choose the size of purchase
If one flow is broken now and reproducible, a single repair with its own test fits: the sign-in callback (£195), the login session (from £295), the incoming webhook (from £295), the form (£245), the blank-screen states (£245) or a general bug repair with a regression test (from £295). If several flows are shaky and you want them dependable together, with an automated check for each, that is a project (from £3,500, quoted after we read your list). If you want the flows watched afterwards, a monthly service (£395 a month) runs checks every week against a test account. All prices are untested, and each is paid only after the agreed checks pass and you sign off, or under terms agreed in writing for the monthly service.
- The monthly service has no round-the-clock cover and no response-time guarantee.
- None of these is a security audit.
What to prepare, and what not to send
Prepare the list of flows, a staging environment or a way to run the app with test data, a test account for each flow and the name of the person who reviews and merges. Do not send passwords, tokens, secrets, cookie values, real customer data or an access invitation in your first enquiry. After the scope and price are agreed in writing, we use a repository or fork you control, test accounts you can revoke and synthetic data, and your team merges and deploys. Production keys stay with you.
- An enquiry does not start work, charge you or book capacity.
- We are a new service and have no client delivery record to show; the worked examples are synthetic.
What this will not do
It will not rebuild the app, guarantee that nothing ever breaks again or take over incident response. It will not repair faults inside a third-party service, and it will not deploy to production for you. If a flow only fails with live customer data or production keys that you cannot share, we will say so and stop rather than work around the boundary. The aim is a short list of flows, each with a check that fails when it breaks, and a person on your side who accepts the result.
- If most failures sit in a service you cannot change, we say so before you pay for anything.
Sources and limits
- Playwright: Visual comparisons Checked 2026-10-11.
- Browser tests can compare a page against stored reference images; reference images depend on the environment in which they were generated.
- GitHub: Best practices for using webhooks Checked 2026-10-11.
- An integration endpoint should respond with a 2XX within 10 seconds and process work afterwards.