Launch check
An independent check before a product or major feature goes live.
Discuss your launchYour next release.
Independently
tested.
On-demand QA for startups and development agencies. We test the journeys that matter and give your developers clear, reproducible findings.
✓ An independent perspective. A practical next step.
✓ProofRun / Findings•••
Clarity before
you ship.
you ship.
Core user journeysPassed
Mobile sign-upIssue found
Billing workflowBlocked
Evidence included. Next steps clear.
Reproducible by design.Steps. Context. Evidence.
Built for teams that ship.Independent testingActionable bug reportsAgreed scope, every time
Less guesswork.
More useful findings.
A good bug report moves the work forward. See how we turn testing into clear context, reproducible steps, and practical priorities.
Northstar / Release checkFictional web app · Illustrative example
Sample reportTesting scope
Account creation, saved filters, date-range exports, and billing access.
Environments
Chrome 130 / macOS 14
Safari 18 / iPhone 13, iOS 18, 390px
✓ Account creation Pass! Mobile sign-up Fail! Filters & export Fail− Billing access Blocked
Prioritised issues 03
Coverage noteBilling was blocked because the supplied account lacked billing access. No billing outcome is asserted.
Clear coverage, including what could not be tested.Agreed fixes can be retested.
An independent check before your next release.
For startups where founders and developers do the testing too. Get another pair of eyes on your working app before a launch, a major feature, or an important customer.
Testing for your startupGet your work checked before client handover.
For agencies balancing several projects and limited QA capacity. Get an independent check against the agreed brief, acceptance criteria, and expected user journeys.
Testing for your agencyThe journeys that matter.
The details that trip people up.
Functional and exploratory testing for websites and web applications, shaped around your build and its users.
Let’s define your scope01
First impressions to first success
Sign-up, login, onboarding, forms, validation, navigation, and error states.
02
Everyday workflows
Critical journeys, account settings, client requirements, and acceptance criteria.
03
Different screens. Real conditions.
Responsive layouts and mobile behaviour across agreed browsers and devices.
04
What changed, and what it touches
New features, relevant regression checks, and retesting of agreed fixes.
Standard scope covers functional and exploratory web testing. Security audits, penetration testing, load testing, accessibility certification, native mobile testing, and automated test-suite development are outside the standard service.
A clear process.
From build to findings.
Scope, turnaround, browser and device coverage, and retesting are agreed before testing begins.
- 01
Share the context
Tell us about your build, requirements, and important user journeys.
- 02
Agree the scope
Define the checks, environments, testing window, and access arrangements.
- 03
We test and review
Explore the agreed journeys and review findings for clarity and reproducibility.
- 04
Get actionable findings
Receive your report with priorities, evidence, and steps your team can follow.
- 05
Close the loop
Your team fixes the issues. We retest the fixes agreed in your scope.
Test credentials and access are arranged after your initial enquiry through an agreed channel.
For the moments
you need another look.
A focused check or a repeatable part of your release rhythm. Start with the work in front of you.
Handover check
Check the agreed requirements before a client review or delivery.
Plan your handoverRecurring release testing
Repeat checks around ongoing releases and evolving user journeys.
Talk about regular testingA few things
you might be wondering.
Clear expectations before we start.
What do you need from us?
A working build, an outline of what needs testing, important user journeys, and any requirements or acceptance criteria you have. We agree access and test credentials after the initial enquiry.
Can you test a staging environment?
Yes. We can test an accessible staging environment. We agree access arrangements, test accounts, and suitable test data before starting.
Can you work without a detailed test plan?
Yes. We can define a practical scope from your build, goals, and key journeys, then combine functional checks with exploratory testing.
Which browsers and devices are covered?
We agree the browser and device combinations for each engagement based on your users and priorities. Coverage is documented in your report.
How quickly can testing be completed?
Turnaround depends on scope, build complexity, access, and availability. We agree a testing window before work begins.
What does the report include?
Your report records scope, environments, journeys and checks performed, and what passed, failed, or could not be tested. Issues include priority, user impact, reproduction steps, expected and actual behaviour, and screenshots or video where appropriate.
Do you retest fixes?
Yes, for the issues and retesting window agreed in your engagement. We document the outcome of those checks.
Can we book testing regularly?
Yes. Recurring release testing can support an ongoing release cycle. We agree scope, timing, and coverage around your team’s needs.
Is automated testing included?
Automated test-suite development is outside the standard service. ProofRun starts with functional and exploratory testing of websites and web applications.
Put your next
release to the test.
Send us your build. Get clear bug reports, evidence, and a practical view of what’s ready to ship.
Prefer to talk it through?
Book a call✓
For startups.
For agencies.
For your next release.