Everything we do starts from one belief: your customers already know what works, and almost nobody asks them. This page is how we ask them properly. Who tests, how a project runs, what stays private, what gets published, and what it costs.
Every test is built around the audience you need to hear from. We do not run products through a generic pool. We define the profile for the project, then match testers to the brief.
Vetted, returning testers who run products in real conditions.
Primarily across Europe, with active presence in the United States and Canada.
To the public and to the client. Identity never leaves Zandora.
Tester vetting is part of defining the project. Before we open a test, we narrow down the profile we want against the variables that actually shape product experience: geography, gender, orientation, age, relationship status, and any product-specific criteria a brief calls for.
For most pilots we run an open test where anyone in the pool can apply. For full tests, prototype work, and anything with tight criteria, we handpick. You can ask us to narrow further. European only. German only. Couples only. Long-term users of a comparable product. We will tell you honestly whether the pool can support the cut you want.
The pool and its demographic spread grow month by month. Cuts that were borderline six months ago are comfortable today, and we are adding testers in new regions and profiles continuously.
Testers are anonymous to the public and to the client. They are identified only by demographic shorthand. Where it adds context to the feedback, we surface relevant detail: testing with a partner, orientation, experience level with the category. Nothing more.
With additional context where relevant: "Female, 35, DE, tested with partner" or "Male, 42, SE, long-term lubricant user."
Every engagement starts with two questions. Are we testing one product, or comparing several? And at what stage of its life is the product, what are you trying to learn? The format and the context together define the test.
One product, or one product line, assessed on its own capabilities. The default format for a launch review, a category entry, or a deep evaluation of a single SKU. We map performance, usability, design, and fit against the audience the product is built for.
Two or more products tested head-to-head, by the same testers, against the same criteria. Useful for category positioning, market-gap analysis, or honestly placing your product against the competition before you commit to a campaign claim.
The context determines what the output looks like, and who it is for.
Released product, market-facing. The full deliverable: insight, proof and content, plus a published review article.
Published reviewPre-production product. Feedback before the design is locked. Run with NDA. Output stays inside your team.
Internal reportAn existing product you are considering changes to. Tests the current design against the audience to inform the next version. Run with NDA. Output stays inside your team.
Internal reportButtons, controls, companion apps. Where small friction shapes satisfaction. Runs on prototype or shipping product.
Internal reportThe same testing, for manufacturers. Get real market feedback on a product before you take it to brands, and use real-user testimonials in your pitch, sales decks and trade show materials.
B2B testimonial packageOther variants on request. Mixed-context engagements, multi-stage programmes, ongoing tester relationships. Scoped on the call.
Scoped per engagementFeedback over time, from your own buyers. A code inside the box takes buyers to our platform, where they review the product the same way our testers do. We filter out unserious responses, process the rest and update your reports every month. It shows what a single test window can't: how a product holds up in real hands over months.
Monthly reportingRunning your own tests? Brands can use our platform to run testing with their own customers or their own tester pool. Ask us about it.
Bigger than one product? See Research.
Timelines vary by project. What does not vary is the shape of the work. Below is how a standard test runs end-to-end, with the durations partners can plan against. A typical full test runs five to six weeks from brief to delivered report.
The test goes live on our tester portal. It can be public, where anyone in the pool applies, or private, where we hand-pick and invite. Geographic and demographic filters are set here. Testers who have flagged interest in the category get notified by email when applications open.
Partner choice: public vs. private, and how narrow the audience filter is.
We pick the testers for the number of slots on the test. Usually the Zandora team handles this against the agreed brief. For tests with special requirements we run selection as a collaboration. For prototype and pre-launch tests where the output is internal-only, the partner can take direct control of selection.
Partner choice: hands-off, collaborative, or partner-controlled.
Products are distributed to the selected testers. Normally handled by Zandora. The brand can also handle shipping directly when supply chain or unit control calls for it.
Partner choice: Zandora ships, or you ship.
Testers use the product over the agreed period and submit feedback through our tester portal. The window is set by what the product needs. Fast tests (lubricants, consumables, immediate-response products) can run three to four days. Complex programmes (long-term wear, partnered use, multi-feature toys) can run four to six weeks.
Typical: two weeks. Long enough for testers to use the product several times before reviewing.
Reviews come in. We synthesise. The full deliverable brings together insight for your product team, proof for your marketing and content for your channels. Duration depends on the number of testers and the number of reports the engagement calls for.
Reference points: pilots typically report in 1 week. Full tests typically report in 2 weeks.
Tester anonymity is absolute. Product confidentiality is configurable. Zandora always holds the rights to material the test produces, and grants partners a royalty-free license to use it. The scope of the license is what shifts between a pilot and a full engagement.
Testers are anonymous to the public and to the client. They appear in reports as demographic shorthand. No names. No photos that could identify them. No contact details cross over.
For prototype, early and pre-upgrade testing, NDA sign-off is part of the tester application. By the time we select, every confirmed tester has signed. No products move before the paperwork is in place.
All review content, images, and video submitted by testers is transferred in full to Zandora at the point of submission. This is the baseline that makes the rest of the rights structure workable.
Every engagement comes with a royalty-free license to use tester material in your own marketing. Full tests grant full access to quotes, images, and stories. Pilots grant a selected set partners can use in marketing and on packaging. The rights themselves stay with Zandora throughout.
Our integrity as a testing service depends on a simple principle. Publication is the default for every test designed to be published. The type of test, set at brief, determines whether an article is part of the deliverable.
Every standard test produces a review article. Some get front-page placement. Others go into our published archive. Placement varies. The fact of publication does not. A weak result is still published. It just isn't featured. Pilots are published like any other test.
No article is produced. The whole point of these engagements is internal learning before a product is locked or upgraded. Scoping determines outcome. If you need a private result, the test is commissioned as internal from the start.
The deliverable is a testimonial package for use in brand pitches and trade materials. Not published on Zandora. Used by the manufacturer in their own sales process.
Sometimes testers misunderstand how a product is meant to be used, so the test doesn't measure what it should. When that happens we call the result inconclusive, fix the instructions with you, and run the test again.
Some questions need more than one product. Our research studies put many products in front of the same testers over a longer period, to find patterns no single test can show.
We design and run the study. You contribute products to the open slots and receive the partner report.
You bring the question. We design the study around it, recruit the testers and report back.
20 to 30 testers, each testing 10 to 15 products across 11 categories. The question: how do preferences in one category predict preferences in another?
Learn moreWhat you keep: all data and findings about your product. General knowledge and trends from the study become part of our background knowledge.
Pricing: priced per study.
The pilot is a standing offer. Standard testing scales on a published ladder. Anything outside that ladder is quoted directly. All prices in EUR.
Credited in full against your first project. A low-barrier introduction to how we test: you see the full process and a complete deliverable.
Shipping setup: partner ships all samples to Zandora HQ in Denmark. Zandora distributes from there. Partner covers product cost, shipping to HQ, customs duties, import VAT, and any other import-related charges.
Pilots are published like any other test.
The tier you fall into depends on tester count, not test type. Any of the contexts in section 02 can be delivered at any tier, scoped to fit.
We recommend 40 or more testers for a high-confidence read. Smaller tests give a clear indication. Size the test to the decision it supports.
Core reporting. Quotes, themes, and structured pros & cons. Marketing or internal output appropriate to the test type.
Adds deeper segmentation, an expanded quote pool, and broader thematic analysis.
Adds strategic observations, trend analysis, and an optional debrief or presentation.
Standard tests and OEM/ODM tests produce all three: insight, proof and content, plus an internal report shaped to the type. Standard tests also include a published test article.
Prototype, pre-upgrade, and UI tests produce insight only: a targeted internal report. Scope is agreed at brief. Significant additions beyond the agreed scope may trigger an add-on.
Projects outside the standard tier ladder are quoted individually. Special requirements may also trigger add-on pricing within a tier. Either way, the conversation starts with a brief and ends with a written proposal. Research studies, continuous feedback and platform access are quoted separately. Continuous feedback is priced from the goals and reporting plan we agree at the start.
Partners with their own logistics can save the €50 per-tester handling fee. At higher tester counts this is a meaningful difference.
Zandora coordinates the full tester logistics chain. Recommended when you want a hands-off engagement or do not have international shipping infrastructure.
Shipping outside Europe may require additional quotation.
You ship directly to testers and save the €50 per-tester fee. Tester materials are individualized, so packages must match the correct tester.
Every project includes lottery samples that scale with tier. Tier 1 includes 1, Tier 2 includes 2, Tier 3 includes 3. Always shipped to Zandora HQ in Denmark. Product-dependent exceptions apply (for example, on very high-RRP products).
Required for complex or technical products, and for projects above 10 tester samples. One unit at HQ allows direct tester support, troubleshooting, and setup validation.
Pricing assumes Europe-based testers unless otherwise agreed. International logistics outside Europe may require additional quotation.
All tester participation is voluntary and based on Zandora's internal matching and selection process.
Tester wellbeing comes first. Zandora may decline projects that conflict with platform standards or tester safety guidelines.
For products where the RRP makes free sampling impractical, we can structure the project as a discounted-purchase test. Testers receive the product at 40–70% off RRP in exchange for completing the review. The partner still receives the full test deliverable.
Run through the Zandora tester portal, against a 10% commission on the discounted price.
Run through the partner's own webshop, using tester-specific codes or links from the portal. No commission.
Lottery and Zandora support samples for high-value projects are agreed case by case, scaled to product cost and project scope.
You have the operational picture. The next step is a brief and a conversation. We will come back with a tester match, a timeline, and a proposal you can take to your team.
Contact us Back to overview
