Tools and providers
SmartSurvey: council landing-page features and public sector prices
Assess SmartSurvey's council-branded landing pages, survey embedding, Public Sector Enterprise prices and Salesforce costs for lead-generation workflows.
Treat a landing-page survey as part of a planned enquiry journey, not a substitute for deciding what makes a useful lead. Define the question, the information needed and the intended follow-up. For a council-branded project, assess presentation, response collection and the cost of connecting answers to a sales workflow.
Council branding and website embedding
SmartSurvey's features include branded landing pages matching a council's identity and website survey embedding. Those are the relevant presentation capabilities for a council-branded survey project. Define whether visitors should answer on a branded page or through an embedded survey, then test the chosen arrangement.
Set a narrow purpose before specifying questions. For a lead-generation project, request only the information needed to assess the enquiry and arrange an appropriate response. Keep that purpose visible in the buying brief, and make CRM integration a separate requirement rather than assuming it follows from website embedding.
Public Sector Enterprise prices
The SmartSurvey pricing table gives annual prices of £9,000 for Public Sector Ent (A), £15,000 for Public Sector Ent (B) and £22,000 for Public Sector Ent (C). Use the user, response and email allowances to assess the intended setup.
| Plan | Users | Responses | Emails per month | Annual price |
|---|---|---|---|---|
| Public Sector Ent (A) | 5 | 10,000 | 30,000 | £9,000 |
| Public Sector Ent (B) | 10 | 30,000 | 60,000 | £15,000 |
| Public Sector Ent (C) | 15 | 50,000 | 150,000 | £22,000 |
| Public Sector Ent (D) | 20 | 100,000 | 300,000 | £28,500 |
| Public Sector Ent (E) | 30 | 250,000 | 750,000 | £35,000 |
| Public Sector Ent (F) | 50 | 500,000 | 1,500,000 | £42,000 |
| Public Sector Ent (G) | Unlimited | 50,000 | 150,000 | £48,500 |
| Public Sector Ent (H) | Unlimited | 200,000 | 600,000 | £55,000 |
| Public Sector Ent (I) | Unlimited | 500,000 | 1,500,000 | £61,000 |
Do not rank the plans by response volume alone. Public Sector Ent (C) has 15 users, 50,000 responses and 150,000 emails per month at an annual price of £22,000. Public Sector Ent (G) has unlimited users with the same response and monthly email figures at an annual price of £48,500.
These are Public Sector Enterprise options. All quoted costs exclude VAT at the prevailing rate and expenses where applicable. Build the software budget around the selected subscription, required connections and implementation work. Keep monthly email allowances separate from the response column when estimating expected activity.
Salesforce costs and API limits
Access to API and webhooks is included in the yearly subscription. Access to the Salesforce integration costs £5,000 per year. Treat the connection as a distinct buying decision: specify the destination fields, proposed update rules and who should review exceptions before accepting the workflow.
Illustrative budget example: Public Sector Ent (A) costs £9,000 annually, and access to the Salesforce integration costs £5,000 per year. Adding those inputs gives £14,000 per year, excluding VAT at the prevailing rate and expenses where applicable. Use that subtotal for those selected items, not as a complete implementation budget.
SmartSurvey's API is limited to 180 requests per minute and 10,000 per day. Estimate requests for the proposed workflow, including any planned retries or updates. Put the intended connection, operating assumptions and acceptance checks into the commercial contract, rather than treating API access as an unrestricted route for moving responses.
Example: lead capture, qualification and routing
Example workflow: use a council-branded survey project to collect an enquiry, assess its relevance and prepare an appropriate follow-up. Treat the following steps as a proposed process to test, not a promise of automatic configuration. Keep research responses separate from decisions about future marketing contact.
- Capture the enquiry. Example question"What would you like help with?" Decide whether a branded landing page or an embedded survey better fits the intended visit. Specify which contact details are necessary for the requested response, and test the wording before making the survey available.
- Qualify the response. Example review rule"Send enquiries about the intended service to the responsible team; review other requests separately." Define the fields a reviewer needs and avoid treating every completed survey as a sales-ready lead. Record the decision criteria before connecting the response workflow.
- Route the information. For a proposed Salesforce workflow, name the destination fields and decide whether a response should create a record or update an existing one. Test the intended mapping with fictional responses. Include duplicate handling, missing values and ownership in the acceptance checks for the connection.
Make the operating workflow explicit before testing: identify who reviews the response, who approves its destination and who handles a failed transfer. Keep a record of the expected result alongside each test response. Accept the connection only when the observed result matches the intended process.
Privacy checks before follow-up
The ICO's direct marketing guidance calls for clear explanations of how information will be used and respect for people's absolute right to object to or opt out of direct marketing at any time. Distinguish answering an enquiry from deciding whether to send subsequent marketing.
The Privacy and Electronic Communications Regulations 2003 (as amended) (PECR) and, where relevant, data protection law apply to technologies that store information on, or access information stored on, someone's device. Include data protection checks when reviewing the intended page, embedded survey and any proposed tracking technologies.
When to shortlist SmartSurvey
Shortlist SmartSurvey for a council-branded survey project when branded landing pages or website embedding match the brief and the Public Sector Enterprise budget fits. For a Salesforce-connected project, include the integration charge and test the intended response mapping. Base the choice on the configured journey, not branding alone.
Before committing, review security claims alongside the proposed data fields, access permissions and transfer route. Retain the selected plan, budget calculation and test results with the buying decision. Choose the setup only after the presentation, qualification process and response destination have each passed their agreed checks.
