Payment and test plan
Payment locks the scope. We turn your selection into a plan that can be run: which flow, which scenario, which device. The plan lands in the panel and testing does not start until you approve it.
01Sign-up and scope
Scope summary
02Payment and test plan
Test plan
03Execution
Daily summary
04Report
Report + PDF
05Re-test round
Re-test results
The moment payment is taken the scope is locked in writing — it never expands one-sidedly afterwards. We then turn your chosen services into scenarios and your analytics into a device and browser matrix. The plan lands in the panel for your approval; not a single test runs before you sign off. The point is to remove surprise: both sides know what will be tested, in the same words.
What we need from you
- Payment and scope approval
- A test environment URL and accounts in at least two roles
- User analytics if you have them — device and browser share
What we do
- We turn your chosen services into step-by-step scenarios
- We derive the device and browser matrix
- We map the scenarios onto a distribution plan for the network
What this step produces
- A scenario list, each one step by step
- The device and browser matrix
- A scope locked by your approval
Questions about this step
Can I change the scope after paying?
Shrinking it is always possible and the difference is refunded. To grow it you add line items in the panel; nothing proceeds until the price and date impact is approved.
What if I cannot provide a test environment?
If we must work in production, scenarios that write data drop out of scope — and you see that plainly at plan approval.
Don't test the next release alongside your users.
Sign up in the panel, pick what you want tested, pay. The first findings start landing in the same panel within hours.