Scope of a test
A whole journey, not a page.
Your panel follows one complete customer journey, from the moment they start looking to the moment they are done. That is how real customers use your service, and it is where the most useful insight lives.
What it looks like
Two typical journeys.
We split every journey into tasks, and the tasks follow your product teams. Each team can go straight to its part.
Finding a home loan
- Search the way they ordinarily wouldGoogle, an AI assistant or a comparison site
- Navigate from your homepageTesting the call to action
- Complete the calculators
- Explore where they would go nextSuch as booking a meeting
- Search for interest ratesA scenario-based task
- Digest information on different loans
- Interact with the terms
- Ask the chatbot a question
Buying insurance
- Search the way they ordinarily wouldGoogle, an AI assistant or a comparison site
- Complete the quote form
- Compare cover plans and rates
- Search for a common questionTesting navigation and service design
- Read a landing page with key policy information
- Review the policy terms
- Ask the chatbot a question
- Use the site searchTesting the search function
Why end to end
Your customers don’t see your org chart.
It tests how customers really move
Teams own slices. Customers live the whole journey. The handoffs between teams, products and systems are where journeys most often break, and the only way to see them is to follow a customer all the way through.
It validates the happy path
You find out whether the journey works the way it was designed to, for everyone, before you invest in changing it.
It shows when people leave the screen
Where would they search, ask an AI, use a comparison site or pick up the phone? Those moments are your most expensive channels, and your clearest signal of where digital falls short.
Every team sees its part
We split the journey into tasks that match your product teams, so the calculator team or the login team goes straight to what matters to them.
What we can test
Live, in testing or still on the drawing board.
Live services
About six in ten tests run on live websites and apps, exactly as your customers find them.
Test environments and betas
Catch problems before release. We work with test accounts and credentials you provide.
Prototypes
Useful early on. Screen readers don’t work well with design tool prototypes, so we will say when a prototype limits what blind participants can tell you.

One test, many teams
No seats. No licences.
Anyone with your organisation’s email can log in to the research repository. So one journey builds understanding of diverse customers across every team it touches: product, design, engineering, content, service and leadership.
Nothing gets people interested like watching real customers use the thing they built.
What we need from you
Minutes, not weeks.
We do the heavy lifting. We aim to deliver within five business days of brief sign-off.
- A link, and a sentence on what you want to learn
- A 20 minute call, if you would like one
- Your red pen on the research plan we draft
- Test accounts or credentials, if the journey needs them
Which journey matters most?
Tell us, and we will draft the scope. It takes 30 minutes.

