Why an RFP

A review analytics RFP makes vendors answer the same questions, so you can compare them fairly. It also forces your team to agree what you need before demos start.

1. Background

  • Your business, locations and regions.
  • Review sources and approximate monthly volume.
  • Languages customers write in.
  • Teams who will use the tool.

2. Scope

  • Sources to cover: for example Google Maps reviews of all stores, Google Play reviews of the app.
  • Users and roles: CX, regional managers, store managers, product.
  • Decisions to support: priorities, location coaching, release checks, leadership reporting.

3. Requirements

  • Classification into topics built from or adapted to our feedback.
  • Sentiment per topic with the supporting text.
  • Breakdowns by location, region, period and app version.
  • Small-sample handling.
  • Reply workflow, if needed.
  • Export and API access.

4. Data and security

  • Where data is stored and processed.
  • Access controls and roles.
  • Retention and deletion.
  • Use of AI models and whether our data is used to train them.
  • Certifications and policies.

5. Hands-on test

Provide a sample of your reviews and ask each vendor to answer three or four real questions, with the reviews behind each answer. For example: which stores have rising billing complaints, what changed after a policy change, which topics drive one-star reviews.

Free review snapshot

Want this done for your own reviews?

No commitment. We use your details only to send your snapshot and follow up. Privacy policy

6. Pricing format

Ask for pricing in a fixed format: per location, users, sources, onboarding, taxes, contract length and renewal terms, so quotes can be compared line by line.

Pricing models

Review management software in India: pricing models explained.

Review management software in india pricing models explained

7. Scoring

  • Test results: 40%.
  • Requirements fit: 25%.
  • Data and security: 15%.
  • Cost: 15%.
  • Support and onboarding: 5%.

Adjust the weights to your priorities, but agree them before responses arrive.

An example

A retail chain ran an RFP with four vendors. Feature checklists looked similar; the hands-on test separated them. Two vendors could not show the reviews behind their numbers, and one misclassified most mixed-language reviews. The chain shortlisted the remaining one for a trial.

Common mistakes

  • Feature checklists only.
  • No test on your data.
  • Weights set after seeing responses.
  • Excluding the teams who will use it.

Common questions

How long should vendors have?

Two to three weeks is common.

How much data should we share?

A representative sample, with personal data minimised.

Should we pay for the test?

Usually not; some vendors offer a paid pilot.

Who should score?

CX, operations, IT and a business owner.

Checklist

  • Background and scope.
  • Specific requirements.
  • Data questions.
  • Hands-on test.
  • Fixed pricing format.
  • Agreed weights.

In short

Describe your scope, ask specific requirement and data questions, include a hands-on test on your own reviews, fix the pricing format and agree scoring weights before responses.

After the RFP

Shortlist two or three vendors on their scores and run a trial on a wider set of your reviews, with the people who will use the tool day to day. Check references from businesses with a similar number of locations. Agree the scope of onboarding and the first results expected before you sign.

Doing this with Falcon

If you are evaluating Falcon: it analyses Google Maps reviews of your stores and Google Play reviews of your app; classifies every review against a taxonomy built from your own reviews, with an exact supporting quote behind each label; finds and summarises specific issues; shows negative share by topic, store and month with small samples flagged; lets your team assign, draft and track replies, which are posted in Google Business Profile; and opens the reviews behind every number.