QA and Testing
Fewer bugs in production, and tests that catch them before release.
- How long2 to 6 weeks
- How we workFixed package
What you receive
Fewer bugs reaching your customers, and tests that catch them on every release, set up so your team can keep it going.
What should we test, and how?
You receiveA test strategy
Testing effort goes where bugs would hurt most.
What it is. A plan of what to test by hand, what to automate and what matters most.
Why it matters. Testing effort goes where bugs would hurt most.
Are our most important flows protected?
You receiveAutomated tests for your key journeys
The things that earn you money are checked every time.
What it is. Automated tests for sign-up, checkout and your other key journeys.
Why it matters. The things that earn you money are checked every time.
Will they actually run?
You receiveTests running on every release
Bugs are caught minutes after they are made, not weeks later.
What it is. Tests run automatically whenever code changes.
Why it matters. Bugs are caught minutes after they are made, not weeks later.
Can everyone use it?
You receiveAccessibility checks
More people can use your product, and you meet your duties.
What it is. Checks for the most common accessibility problems.
Why it matters. More people can use your product, and you meet your duties.
Is it getting slower?
You receivePerformance checks
Slowdowns are caught before customers complain.
What it is. Checks that warn when pages or jobs slow down.
Why it matters. Slowdowns are caught before customers complain.
What happens when someone finds a bug?
You receiveA bug report process
Nothing is lost, and the important bugs get fixed first.
What it is. A simple way to report, sort and track bugs.
Why it matters. Nothing is lost, and the important bugs get fixed first.
Can we keep it going?
You receiveTraining for your team
Quality keeps improving after we step back.
What it is. Training on writing and maintaining tests.
Why it matters. Quality keeps improving after we step back.
From brief to done
- 1
Week 1
Plan
The test strategy agreed.
- 2
Weeks 2 to 5
Build
Automated tests and checks running on every release.
- 3
Final week
Train
The bug process and training for your team.
What can a stranger see about our systems?
Outside-in security look. What anyone on the internet can see about your systems, and the five fixes that matter most.
- You give us written permission and the addresses to check
- We check certificates, email settings and anything exposed, from the outside only
- A short report with the fixes in order
- It is free. There is nothing to pay and nothing to sign.
- The report is yours to keep and share, whatever you decide.
- No sales call unless you ask for one.
Questions people ask
How much does it cost?
We send a written quote after your request: what it covers and what it does not. The tier, scope and timing set the price.
Could I just use AI for this?
AI drafts code and prototypes quickly, and we use it every day. It cannot decide what to build, prove that it is secure, or answer for it when real people rely on it. That is the part you are hiring us for.
Who owns the work?
You do. Code, designs, files and documents are yours, and the quote says so in writing.
Can we change the scope?
Yes. If something needs adding or removing, we agree it in writing before we do it.
What happens after?
Most people go on to Operate and Improve Plan, but there is no obligation. You keep everything we made.