Prove autonomous testing on your application in 8 weeks
Your application, your team, your baseline. We agree the scope and the success criteria before Sprint 1, measure where you stand in the first week, and compare against it in the last one. You end with a working suite and enough evidence to decide either way.
- 8 weeks, 8 sprints
- Up to 10 critical flows
- Baseline measured in Sprint 1
- You own the tests
The shape we recommend
This structure comes from the pilots we have run with enterprise QA teams, and it is what we suggest as a starting point: long enough to reach a suite people trust, small enough in scope to stay honest, and finite so the decision actually gets made. We publish it in full so you can weigh it before the call rather than after it. Where your context calls for something different, we shape it with you.
8 weeks, run as 8 weekly sprints, with a decision at the end.
Up to 10 critical user flows of one web application, agreed before Sprint 1. Flows can be exchanged one for one as you learn what matters.
5 tests built by our engineers, weekly runs, a live stability dashboard, a benefit assessment against your baseline, a viability report, and a closure presentation for your stakeholders.
Around 20 further tests, built by your people with our coaching. The point is that the suite still works when we are not in the room.
A named decision maker on your side commits to a go or no-go at the end of Sprint 8, against criteria agreed in writing before Sprint 1.
You own every test. They export as plain Playwright code and keep running without Wopee.io.
Fixed, so you can plan and budget
- The price, agreed before Sprint 1 and credited in full if you continue.
- Eight sprints, ending in a go or no-go rather than a renewal conversation.
- The effort we ask of your team, published above so you can plan for it.
- Test ownership and the exit terms, whichever way the decision goes.
Shaped with you
- Which flows we cover, and in what order.
- The route to your environment: VPN, allow-list, or a jump host.
- Sprint cadence, aligned to your release train rather than ours.
- On site or remote for Sprint 1 and Sprint 8.
- How much coaching your team wants, and how quickly they take over.
- Whether related areas such as API or mobile belong in scope for you.
What we need from your team
This is the part most vendors leave out, so we put the numbers up front. A pilot with a team that cannot spare the time stalls around Sprint 3, and nobody benefits from that.
Time
3 to 5 person-days
per sprint, across the team
Roughly 20 to 35 person-days over the 8 weeks: building tests with our coaching, reviewing runs, and giving feedback.
People
- A QA or test lead as pilot owner, named before kickoff.
- The testing team, for the hands-on work.
- SRE or DevOps for environment access in Sprint 1, then on request.
- Stakeholders for the Sprint 8 demo and decision.
Before kickoff you need
- A non-production environment with working test accounts and stable test data.
- Network access for our agents to reach it. We agree the route on the first call.
- The initial 5 test cases you want covered first.
- A named decision maker and a date for the Sprint 8 decision.
Eight sprints, one decision
Sprint 1 and Sprint 8 can be on site or remote. Everything in between is remote.
Not sure your application is a fit? That is what the first call is for. We will tell you if it is not.
How we measure
Every pilot records a baseline in Sprint 1 and compares against it in Sprint 8. The criteria are agreed in writing before work starts, so the result is read rather than interpreted.
- Flow coverageHow much of the agreed critical scope is under automated test.
- Time to a scenarioHow long a test case takes to create, before versus with Wopee.io.
- Regression cycle timeHow long a full pass over the agreed scope takes.
- Test stabilityThe share of runs that fail for reasons other than your product.
- Team adoptionHow many of your people can run and review tests unaided.
We report each of these against your own baseline. We do not quote percentages from other customers as your expected result, because every application and every team is different.
Is a pilot right for you now?
Read this as a self-check rather than a sales filter. If several of these are a no, we will say so on the first call and suggest a better quarter instead of starting something that stalls.
- A named pilot ownerA QA or test lead who will run this alongside us.
- 3 to 5 person-days per sprintAcross the team, for building tests, reviewing runs, and feedback.
- A non-production environmentWith working test accounts and stable test data.
- A route to that environmentVPN, allow-list, or a jump host. We agree it on the first call.
- An application that is hard to automateCanvas, nested iframes, dynamic data, heavy SPA state, or an SSO-protected enterprise stack.
- Someone who decidesA named signer for the go or no-go at the end of Sprint 8.
- A reason to act this quarterA release, an audit, a migration, or a regression backlog that keeps growing.
- Openness to publicationWe publish the technique, never your data. Named or anonymised, your call.
What a pilot does not do
Worth knowing before you spend budget on it.
- It does not replace your QA teamIt gives them a suite that keeps working, and the coaching to run it themselves.
- It does not promise a defect countOur agents build and stabilise a regression suite. How many bugs that surfaces depends on your application.
- It does not cover every platformNative mobile, desktop applications, and APIs on their own are out of scope. A pilot covers one web application.
- It does not driftThere is no rolling extension. Sprint 8 ends with a decision either way.
Both endings are clean
At the end of Sprint 8 you have a viability report, a working suite, and a decision to make. Neither answer leaves you worse off than you started.
You continue
The pilot fee is credited in full against your first year. The suite grows from the foundation you already built, and your team keeps our support.
You stop
You keep every test, exported as plain Playwright. We revoke our access and delete your data within 30 days. Nothing runs on our side afterwards.
Your data stays in the EU by default, a custom region or a full on-premise deployment is available, and we never train models on your code, test data, or screenshots. SOC 2 and ISO 27001 are on our roadmap, and we are happy to complete your supplier security questionnaire before the pilot starts.
Start with a 30 minute call
It is not a product demo. We go through the questions on this page for your organisation: which application and which flows, who owns the pilot and who decides, whether the capacity exists this quarter, and what your security review needs from us. If it fits, we send you the pilot charter pre-filled from that conversation. If it does not, we will tell you on the call.