Skip to content

Use case · product tests

TEST FEATURES, FLOWS AND COPY

Describe a feature, an onboarding step or a line of product copy, and ask which version a place would pick. Read which is ahead, and with whom, before you build it.

What you get

  • Many ideas, one question

    Put up to 12 feature ideas in one question and read the order they come back in.

  • Two versions of a step

    Describe two versions of a flow and put them side by side in front of the same twins.

  • Then ask why

    Interview twins from the group that went the other way and read their reasons in their own words.

  • Households or buyers

    Ask residents, or the modeled decision-makers at the businesses that would buy.

Studies you could run

  • Residents

    Which of these features would make you switch banking apps?

    A reading shows: The order of the features, and whether it changes with age.

  • Residents

    Sign up with a phone number, or with an email address?

    A reading shows: Which version is ahead overall, and whether older households part ways with younger ones.

  • Businesses

    Which of these reports would you open every week in your accounting software?

    A reading shows: Whether small employers and larger ones rank the reports the same way.

Questions

Who answers?
Simulated twins of the place’s population. Each twin is modeled on the real make-up of the place — age, household, work, housing — and weighted back to it.
Can it test a working prototype?
No. Twins read a description of a feature or a flow, not a working product.
Does it tell me how many people will use it?
No. It shows the order and the gaps between versions, not adoption.
Can I attach screenshots?
In the map workspace, where attachments are enabled. Twins read a neutral written description of each screenshot, not the image.

Bring us the product decision.

Tell us the place and the question, and book a time to run it with us. Already have an account? Sign in from the same page.

Get started