Support and hosting
Testing before launch
We test the journeys that matter on real devices and browsers, and automate the checks that should run on every release.
Overview
Every update is checked carefully before it reaches your customers.
Every bug a customer finds costs more than one caught before release, in support time and in trust. Releases that break features which used to work are especially damaging. Testing before launch checks that the journeys your customers rely on, such as signing up, paying or booking, still work on the phones and browsers they actually use.
First we write down the journeys that matter most and how to check each one. Those journeys are tested by hand on real phones, tablets and browsers, old and new, and every fault is logged. The most important ones are then scripted to run automatically on every release, so a broken checkout is caught in minutes rather than by customers.
You gain a test plan, an automated test suite and a short report with each release showing what was tested, what passed and anything held back. Testing uses realistic sample data, never real customer records. A healthcare patient app and a distributor's business system are tested this way, and we can also act as independent testers for another team's work.
- What you receive
- Test plan · Automated test suite · Release reports
- Typical technology
- Playwright · Vitest · BrowserStack
Who it's for
Is this right for you?
If your software rarely changes, a one-off test before each major release may be enough.
- A product where customers find bugs before your team does
- Releases that break features that used to work
- An app nobody has tested on older phones or other browsers
Scope
What goes into it
Every engagement is scoped to your goal. These are the parts most projects include.
- Test plansBased on your real user journeys.
- Automated testsEnd-to-end checks on every release.
- Device testingPhones, tablets and browsers, old and new.
- Performance testingHow it behaves under load.
- Accessibility checksKeyboard, screen readers and contrast.
Timeline
How a typical project runs
Usual length: usually 2 to 6 weeks to set up, then with every release. Your written scope gives the exact plan.
01Week 1
Key journeys test plan
We write down the journeys that matter most, such as sign-up, payment or booking, and how to check each one.
02Weeks 1–3
Device and browser sweep
We test those journeys on real phones, tablets and browsers, old and new, and log every fault.
03Weeks 3–6
Automated release checks
Key journeys are scripted to run on every release, so a broken checkout is caught before customers see it.
04Week 6 onwards
Release report
Each release comes with a short report: what was tested, what passed and anything held back.
One-time project
A fixed quote for an agreed scope, paid in milestones. You own the code and accounts once it's paid.
Monthly care plan
A monthly subscription that keeps your software secure, monitored and improving, with response times in writing.
Industries we have built this for
Getting started
What happens after you get in touch
- 01Tell us the problemA short form or a call. A senior lead replies within one working day.
- 02One callWe sign an NDA first if you need one, then go through your goals, users and current systems.
- 03Written scope and fixed quoteWithin 48 hours of the call, with milestones and a timeline.
- 04Build in milestonesYou see working software at every milestone, and you own what we build.
Questions
Before you ask
What changes the size of the job
- The number of journeys and screens to cover
- How many devices and browsers matter to your users
- Whether load and accessibility testing are included
Can you test an app another team builds?
Yes. We can act as your independent QA team.
Will testing slow down our releases?
Very little once it's set up. Automated checks run in minutes, and manual testing focuses only on what changed.
Do you test with real customer data?
No. We test with realistic sample data, so personal information is never exposed during testing.
How is this priced?
As a one-time project with a fixed quote, agreed after a short call and paid in milestones. After launch you can add a monthly care plan for hosting, updates and support.
Previous work
Projects in this area
The first two projects used this directly; the others are related work from support and hosting.
Client details hiddenCookware distributor
Sales and accounts system for a cookware distributor
We built a system to invoice shops, collect payments, buy stock and keep the ledgers balanced.We built the system a cookware dealer uses to invoice retail shops, collect payments, buy stock and keep every ledger in balance.
See what we built
Client details hiddenDigital healthcare company
Patient app for booking healthcare from a phone
We built a phone app where patients book doctors, order medicine and keep records in one place.We built the iPhone and Android app where patients book doctors, order medicine, call an ambulance and book lab tests, with their records in one place.
See what we built
Client details hiddenVetted matchmaking platform, UK
Vetting journey and vetting team portal for a matchmaking platform
We built a vetting portal that stops new members connecting with anyone until approved.We designed how a membership site keeps every new member away from others until a vetting team has approved them, and built the portal the team works from.
See what we built
Client details hiddenInterior design studio
Staff and client portal for an interior design studio
We built a portal where the studio follows enquiries, messages clients and prepares quotations.We built the portal where the studio follows enquiries, messages clients, prepares quotations and keeps its website up to date.
See what we builtMore in support and hosting
Tell us what you need built.
Share the problem in a few lines. After one call you'll get a written scope and a fixed quote within 48 hours.
