02 · before or during the programme
Pod
Builds the pre-production capability that does not exist yet. You own the test code. It is not a residual team you inherit at the end.
Map · Pod · Cover
Independent QA that shows what regression is costing you, builds the test suite you own, and gives you a verdict on named journeys every cycle.
Start Here
01 · fixed scope
A fixed-scope assessment for new projects or existing regressions across your live platforms.
02 · before or during the programme
Builds the pre-production capability that does not exist yet. You own the test code. It is not a residual team you inherit at the end.
03 · recurring
The recurring service both routes lead to. Named live journeys stay checked as the system changes, with a verdict from a named lead each cycle.
Most teams start with Map, so the business case comes before anything ongoing. If your platform is live and you already know which journeys matter, start with Cover.
A build you intend to ship, checked on the journeys we agreed.
In your test environment or in CI, against that build.
Never in productionWhat ran, on which build, what happened, and what was not covered.
A named person assesses the evidence and states a verdict, with a stated limit on what it covers.
Whether to release is your call. We tell you what the evidence says.
The decision stays yoursNext release: the same journeys, checked again.
Start with Map. On live platforms it tells you what regression costs per platform and which journeys are worth covering. On a new project it names the journeys and what to build first. Either way you have the business case before you commit to anything ongoing. If the platform is live and you already know which journeys matter, say so on the first call. Cover may be the right door, and we will tell you either way. A new project usually goes Map, then Pod, then Cover. We settle it on that first call, and if the fit is not there we say so on the same call.
A technical and commercial read on each platform: what regression costs, where it is worth fixing, the first six to eight journeys named, a draft scope register and a sequenced roadmap. On a new project there is no regression cost to measure yet, so it produces the journeys, the register and the roadmap. It ends in a decision. That decision may be Cover, or Pod then Cover, or hire an engineer, or leave it alone, or decommission the platform anyway. We will say so if that is what the numbers show.
No. You are buying a service with an output, and we manage the people who deliver it. What you get is the working automation and the capability to keep producing it after we leave. The test code is yours, in your repository, from the first commit.
No. Checks run in the agreed test environment or in CI, against builds and release candidates intended for production. Cover builds the suite for a live platform. The suite never runs against production.
No. A named lead assesses the evidence each cycle and issues a verdict: verified, verified with residual risk, not verified, or not assessed. The release decision stays yours. We tell you what the evidence says. What to do about it is your call.
Minimum access by default. Work runs in your environments, repos and tools wherever possible; NDAs are standard; access is limited to the project team and withdrawn at close. We do not ask for production credentials, and test data is agreed or synthetic.
Independent testing and tool sales are two separate lines. In a QA assessment we do not recommend a tool because we sell it, and if there is a commercial interest in the recommendation, we say so in writing before you decide.
Launch
We opened on 28 September. What we kept seeing in how QA is bought, and what we do instead.
Read the articlePerspective
Test execution is the visible part. What a buyer is actually paying for is someone who has seen the failure before.
Read the articleGuide
Preparing a QA team for AI without losing the thing you were buying: what to ask of a tool, and where judgement still has to sit.
Read the articlePractice
A pass rate is not evidence. What a release decision needs, and why it has to arrive while the work is happening.
Read the article
Start here
Three steps, and the first one is a message.
Use the form below, or write to info@saucinco.com. A few lines about the platform and the release are enough.
We talk it through and recommend Map, Cover, or Map, then Pod, then Cover.
Every engagement starts with a fixed scope and ends in a decision about what comes next. Anything recurring comes after you have seen the result.
Careers
When there is a QA role, we hire dedicated software and AI enthusiasts who are looking to join a company that wants to make a difference.
Write to info@saucinco.com and attach your resume.