Market Research Software Buyer's Guide: Requirements, Demos, Pricing Models and Contracts

Buying market research software is a procurement decision as much as a technical one. The feature list matters, but so do the requirements you write, the way you run demos, how pricing scales with your volume and what the contract says about your data. This guide walks through each stage in order, so that the choice you make is one you can explain and defend later.

Stage 1: Write a one-page requirements brief

Most poor software decisions start with a vague brief. "We need something to manage projects" invites every vendor to show their strongest feature rather than your most pressing need.

A one-page brief keeps everyone focused. It should cover:

• The jobs. Which parts of the research workflow must the software handle: bids, scripting, sample, quotas, suppliers, fieldwork, reconciliation, invoicing, reporting?
• The people. Which roles will use it daily, and which only occasionally? Include external users such as freelancers, suppliers or clients if they need access.
• The volume. How many projects, users and countries in a typical year? This shapes pricing as much as features.
• Must-haves and nice-to-haves. Be strict. If everything is a must-have, nothing is.
• Data in and out. What must be imported at the start, such as supplier lists or templates, and what must you be able to export at any time?
• Constraints. Budget range, timeline, internal approval steps and any client or quality requirements you already work under.

Share the brief with vendors before the first call. A good vendor will tailor the demo to it; one that ignores it has told you something useful.

Who should be in the buying group

Keep the group small but representative. A typical mix is one person from sales or bidding, one project manager, one sample or fieldwork manager and one person from finance. Each sees a different part of the workflow, and each will spot gaps the others miss. A senior sponsor should own the final decision, but the people who will use the software daily should own the scoring.

Agree up front how the decision will be made: who scores, which criteria carry most weight and what would rule an option out entirely. Writing this down early prevents a late favourite from bending the process.

Stage 2: Map research software features to your workflow

Vendors describe research software features in their own vocabulary. Translate everything back into your own stages so you can compare like with like.

You may not need every row. A team that already has strong reporting might focus entirely on build, field and close. What matters is that every vendor is asked the same questions in the same order. For a wider view of categories, see our guide to the best market research tools.

Stage 3: Run demos that test real work

A scripted demo is designed to impress. Your job is to make it reflect a normal week instead.

Before the demo

Send the vendor a short, anonymised version of a recent project: the countries, the quota cells, the number of suppliers and one change that happened mid-field. Ask them to run that project in the demo.

During the demo

Let the person who will use the software every day sit at the front and ask questions. Managers can observe and take notes on the scorecard.

• Create a project from a bid or brief, not from a pre-built example
• Define quota cells and assign at least two suppliers
• Show live counts, terminates and over-quotas per supplier per cell
• Add a new quota cell mid-field and show what changes
• Remove poor-quality completes and show where that is recorded
• Close the project and show the reconciliation figures
• Export the data and the project summary
• Show what a supplier or freelancer would see with limited access

After the demo

Write up the answers the same day, against the same checklist for every vendor. Note anything that was described as coming soon. Roadmaps change, so score only what you saw working.

Stage 4: Understand market research software pricing models

Market research software pricing varies widely, and the headline figure rarely tells the whole story. Rather than comparing list prices, compare what each model would cost you at your real volume, and at the volume you expect in two years.

Many vendors combine models, for example a project allowance on an annual plan with user limits attached. That is reasonable, as long as you understand which limit you are likely to hit first. Ask each vendor to quote against your brief, including onboarding, training and any charges for data export or additional storage.

Useful pricing questions to put to every vendor:

• Which limit, such as users or projects, are we most likely to reach first at our volume?
• Is unused allowance carried over, or does it reset at renewal?
• Are occasional users, such as freelancers or client viewers, charged in the same way as full users?
• What would it cost to move up a tier mid-year, and to move down at renewal?

Total cost also includes your own time. A cheaper tool that needs a lot of manual workarounds can cost more in staff hours than a pricier one that fits your process.

Stage 5: Check the contract before you sign

Research data often includes respondent information, client briefs and commercial terms with suppliers. The contract should protect all three. Professional codes such as the ICC/ESOMAR International Code set out researchers' duties to participants and clients, and your software arrangements should not make those duties harder to meet.

Points to check:

1. Data ownership. It should be clear that your data remains yours.
2. Export and exit. How, in what format and at what cost can you take your data out, during the contract and at the end?
3. Access control. Can you set roles so that each user, supplier or client sees only what they should?
4. Changes and incidents. How will you be told about planned updates or unplanned problems that affect live projects?
5. Renewal terms. What notice is needed, and how can prices change at renewal?
6. Support and onboarding. What is included, in which hours and through which channels?

Ask for these answers in writing. Where a vendor makes a claim about security, certification or compliance, ask for the evidence rather than relying on a slide.

Stage 6: Decide, then plan adoption

When the scorecards are in, the decision is often clearer than expected. If two options are close, prefer the one your daily users found easier, because adoption is what turns software into value.

1. Confirm the choiceShare scores and reasons with everyone who took part.
2. Agree a start dateNew projects begin on the new system from a fixed date.
3. Prepare the basicsLoad supplier lists, templates, users and roles before day one.
4. Train by roleShort sessions for project managers, sample managers and finance separately.
5. Review after closeCheck the first month-end close-out and fix gaps quickly.

Keep the old process available for projects already in field, but do not let new work start there. Running two systems for new projects is the most common reason adoption stalls.

Where Sampledge fits

Sampledge is a family of connected products from Frequent Research, built around research project and sample management. For buyers comparing research operations software, the centre is SampTrek, which keeps projects, quotas, suppliers, live fieldwork, respondent and incentive records and reconciliation together. Around it, SampBidx handles bids and proposals, SampCode covers scripting, and Talk2Tax manages invoicing and accounts so closed projects can move into billing.

Workspace plans are annual and range from Starter Pack (350 projects, 10 users) to Premium (unlimited), with the Pro plan including marketplace integration. Current prices are on the pricing page, and common questions are answered in the FAQ. If you are still deciding between a connected platform and separate tools, our market research platforms evaluation guide offers a scorecard you can reuse, and our explainer on sample management software covers the fieldwork side in detail.

Ready to put Sampledge through the demo checklist above? Book a demo and send us an anonymised recent project beforehand, or create a workspace to explore on your own.