← Compare survey tools

Salesforce charges $13,500 a month to turn survey answers into records. We think that is just what a survey is.

This is the one competitor whose architecture we are not arguing with. Salesforce Feedback Management does the right thing: responses become records in your org. Our disagreement is entirely about the price of the ticket, and about what it will not let you do with your own questions.

Pricing and plan limits verified July 2026

Credit where it is due

What Salesforce Feedback Management is genuinely great at

If your procurement team is nervous about buying feedback tooling from a young company, read this section carefully, because most of it is true and it matters.

  • It is first-party. Salesforce's own security review, roadmap, support and contract vehicle. For some buyers that ends the conversation, and that is a legitimate way to decide.
  • The architecture is right. Responses are records in your org, next to the data they belong to. That is the correct model — it is the same conclusion we came to.
  • Nothing to integrate. No connector, no mapping project, no export step. Same as us, and for the same reason.
  • Safe harbour. Nobody was ever fired for buying the Salesforce option.
  • On the “you are a young product” question, our answer is architecture, not denial: your data is in your org either way. If AutoSurvey vanished tomorrow, your records do not.

The evidence

What their own documentation says

Nothing below is our characterisation of Salesforce Feedback Management. Each item is either something Salesforce Feedback Management publishes about itself, or something we observed firsthand in a real account and can show you.

$13,500 per org, per month

Starter is $13,500 per org per month — $162,000 a year — and includes 100,000 responses per licence term. Growth is $46,000. These are Salesforce's own published add-on prices, not an analyst estimate.

Salesforce all-add-ons price list (PDF), verified July 2026. Note: the older knowledge article often cited for these figures is dead; the add-ons PDF is the live source.

The free tier below it stops at 300 — and that is a total, not a monthly allowance

Salesforce Surveys, the tier included below Feedback Management, stops collecting at 300 responses. It is worth being precise about what kind of 300 that is: a cumulative entitlement balance, not a monthly allowance. Salesforce’s own usage documentation describes an Allowance covering “all contracts up to the current date, including 300 free survey responses for each contract”, and states the value “isn’t reset when a contract is renewed”. Their renewal wording sits awkwardly with itself in places and we are not going to resolve it on their behalf — but the part that matters here is not ambiguous: there is no monthly reset.

Two further things get conflated, and they are not the same fact. Writing an answer into a field on a record — Survey Data Mapping — is documented as available with the Feedback Management Starter and Growth licences on Enterprise, Unlimited and Developer editions, and it sits behind Advanced Settings, which platform surveys do not include. Separately, attributing a response to a person at all has no default configuration: Salesforce’s own words are that there is “no default functionality or configuration to automatically relate survey responses directly to a user, lead, person account, or contact”, and that doing so “requires implementing Apex”.

300 default per Salesforce Knowledge Article 000394564 (published 12 July 2026); the cumulative-allowance wording per “View the Usage of Survey Responses” (help.salesforce.com); the record-field licence requirement per “Create Survey Data Maps to Create or Update Records”; the attribution gap per KB 000391879. ★ We say nothing about how collection behaves AT the cap: no Salesforce document we could find describes whether it warns, and we have not observed an org at the cap ourselves.

Your questions are records you are not allowed to edit

This is the detail that decided the matter for us. Feedback Management stores survey questions as records — and the SurveyQuestion object supports query and retrieve only. No create, no update, through the API. There is no import of any kind, so there is nothing to bulk-load and nothing to bulk-edit. Active versions lock, and changing a live survey means cloning it.

“Salesforce’s own $13,500/month product stores survey questions as records — then makes them read-only. AutoSurvey’s questions are records you can actually edit.”
Salesforce object reference for SurveyQuestion, verified July 2026.

Before you author anything, you stand up Experience Cloud

Authoring is a Flow-based builder, and the delivery surface needs Experience Cloud configured first. That is a project with an admin on it, before question one exists.

Salesforce Feedback Management published setup documentation.

What we are actually claiming

Not that Feedback Management is bad — that it is priced for a different buyer than the one we build for. A programme team with a real feedback problem and no six-figure line item cannot buy it, and the free tier below it cannot write to a record field. That gap is the whole reason AutoSurvey exists.

Salesforce's own research makes our argument better than we can

This is the part we would rather you heard from them. Salesforce Research's State of Sales, 5th edition (2022) — a double-anonymous survey of 7,775 sales professionals across 38 countries — found reps spend only 28% of their week actually selling, with 8.8% of the week going to manually entering customer and sales information.

To be clear about what that number is doing here: it is not a criticism of Feedback Management, which removes exactly this work — that is the whole point of it, and we said so above. It is here because the company selling the $13,500-a-month answer has already measured and published how expensive hand-moving data between systems is. We are not arguing with their diagnosis or their architecture. We are arguing about the price of admission.

Salesforce Research, State of Sales 5th edition (2022), p.14; double-anonymous survey of 7,775 sales professionals, fielded August to September 2022. Scoped as published, to sales reps. Not linked: Salesforce’s document host refused our request, so we could not re-confirm the sentence on a resolving page ourselves.

Stage by stage

The whole race, not the first lap

Every tool on this site is fast at stage one. The interesting question is what the other five stages cost you.

Stage Salesforce Feedback Management AutoSurvey
Authordraft the questions A Flow-based builder, with Experience Cloud configured first. No question import of any kind.Salesforce setup documentation Describe what you want to learn and AI drafts it in about 15–30 seconds, with the right Salesforce field types. AI authoring is included — no separate Salesforce AI license, no Agentforce project.
Publish gatewhat stops you sending $13,500 per org per month for Starter; $46,000 for Growth. Starter includes 100,000 responses per licence term.Salesforce all-add-ons price list (PDF) One per-org price. Logic, scoring and question types are not the upsell. The deploy job runs in 30–60 seconds.
Distributereach known contacts Native, and good — at that price. Salesforce campaign send, list or triggered email, public link or QR, or Experience Cloud. The recipient is already a Salesforce record, so “who answered?” is never a matching problem.
Collectwhat happens at the cap Included in the licence term at Starter: 100,000 responses. On the free Salesforce Surveys tier below it: 300 responses — a cumulative total per contract, not a monthly allowance — after which collection stops. Writing answers into record fields requires a Feedback Management licence.Salesforce KB 000394564 · “View the Usage of Survey Responses” · “Create Survey Data Maps to Create or Update Records” Your own org's limits. No per-response meter deciding whether you are allowed to read your own data.
Land in CRMthe expensive stage Native. This is the one competitor that gets this stage right, and it is why the architecture costs what it costs. This stage does not exist. Responses are created as records in your org, linked to the contact and campaign on arrival. Nothing to map, nothing to sync, no export step.
Actdo something about it Native. Score fields are stamped at submission, so the Flows you already run branch on the answer immediately — Tasks, Cases, alerts, reports, Einstein.

Cells marked Not published are ones where Salesforce Feedback Management does not publish a figure and we will not estimate one. Where a cell cites firsthand observation, we hold the screenshot.

Questions people actually search for

How much does Salesforce Feedback Management cost?

Starter is $13,500 per org per month, which is $162,000 per year, and includes 100,000 responses per licence term. Growth is $46,000. Source: Salesforce's own all-add-ons price list PDF, verified July 2026.

What is the response limit on free Salesforce Surveys?

300 responses — and it is a cumulative total rather than a monthly allowance. Salesforce's usage documentation describes an allowance covering all contracts up to the current date, including 300 free responses for each contract, and says that value is not reset when a contract is renewed. Collection stops at the cap. We make no claim about how it behaves at the cap, because no Salesforce document we found describes that. Writing answers into record fields requires a Feedback Management licence. Sources: KB 000394564; 'View the Usage of Survey Responses'; 'Create Survey Data Maps to Create or Update Records'.

Can I edit Salesforce Feedback Management survey questions through the API?

No. The SurveyQuestion object supports query and retrieve only — there is no create or update through the API. Active survey versions lock, and changing a live survey requires cloning it.

Bring the questionnaire, not an export

There is no export to import from — Feedback Management has no question export, and SurveyQuestion is read-only through the API. So bring the questionnaire itself: paste the question list, or bring a spreadsheet or CSV, and AutoSurvey builds it out.

Run it in a sandbox first, the same way you would test any other change before it touches production.