How we work
No long contract on a first conversation. Each stage is worth doing on its own merits, and each one is designed to make the next decision obvious rather than risky.
For: Any team that wants an outside read on where quality actually stands.
Includes
Outcome
A written assessment you can act on yourself, hand to your own team, or use to brief any vendor.
For: Teams who want proof before an ongoing commitment — and a working safety net either way.
Includes
Outcome
A real, running safety net in two weeks — and a clear-eyed view of what working together is like before anything ongoing is signed.
For: Teams who want quality owned, not supervised.
Includes
Outcome
A quality function that runs without you managing it, and evidence-based release decisions.
We scope and price after the health check, in writing, against defined deliverables. If we do not think we are the right fit for what you need, we will tell you that instead of quoting.
The path
Working principles
These are not aspirations on a website. Each one appears in the master services agreement, because a promise you cannot enforce is marketing.
Tests and frameworks live in your version control from the first commit. No proprietary runner, no vendor lock-in, nothing to migrate if we part ways.
An MSA and a per-engagement SOW define coverage, release frequency, response windows and what counts as new scope. It protects you from vague delivery and us from unlimited work.
A suite that is not maintained becomes a liability within months. Keeping it green and meaningful is part of the retainer, not a surprise.
NDA before anything technical. Scoped, least-privilege credentials. No production access unless the work truly needs it. Secrets in a manager, never in code or chat.
We test with synthetic or masked data by default. If real data is genuinely required, it stays in your environment under your controls.
If we think a release is risky, we say so in writing with the reasons. You make the call — but you make it informed, and the record exists.
Reporting
Test-case counts and pass percentages are vanity metrics — they go up whether or not your product is getting safer. These four tell you whether the engagement is working, and they are the ones we report against.
FAQ
We do not publish rates, because a number without scope is meaningless — the same "automation retainer" can mean four journeys or four hundred. After the health check we send a written proposal with defined deliverables, coverage targets and response windows, so you are comparing something real. Setup work and ongoing work are priced separately and stated plainly.
The health check commits you to nothing. A Release Readiness Sprint is a fixed two-week scope with no obligation afterwards. Ongoing engagements run monthly with a notice period we agree up front — typically short, because a partner who needs a long lock-in is telling you something.
We work primarily in IST with deliberate overlap for European and US teams. Working hours and response windows are written into the SOW rather than implied. We will not promise round-the-clock cover we cannot staff.
Read-only first: repository access, a walk through the product, existing tests and CI configuration, and your last few incidents. Incidents are the most informative artefact you have — they show where the product actually breaks, not where you assume it does.
You keep everything: the framework, the tests, the pipeline configuration and the documentation, all already in your repositories. We do a handover session and write down what is covered, what is not, and what we would have done next. No exit fee, no data extraction exercise.
That is the most common arrangement. Your engineers hold product knowledge nobody external can replace. We usually take the automation build-out and regression execution so that knowledge gets spent on judgement instead of on repetitive clicking.
Answer twelve questions about how your team tests today. You get a maturity score, the three gaps most likely to cause a production incident, and a 30/60/90-day roadmap — whether or not you ever work with us.