SaaS trial feedback form — capture the conversion blocker while there's still time to address it

Who this template is for

Trial feedback is the form most SaaS teams send too late. The default is to ask for feedback at the end of the trial — the day before it expires, or the day after it converts to paid — and by that point the user has either decided to convert or decided not to, and the feedback you get is post-rationalization rather than actionable signal. The teams that actually move trial → paid conversion rates send their feedback prompts mid-trial, typically day 3-7 in a 14-day trial or day 7-14 in a 30-day trial, when the user has had enough time to form an opinion but there's still time to address the blockers they reveal. The fields that predict conversion: "have you found value yet?" (the binary activation signal — users who haven't found value by mid-trial typically don't convert without intervention), "what's blocking purchase?" (the specific objection that can be surfaced to your support or sales team for outreach), "pricing perception" (is the price within budget — the most-undervalued field in SaaS feedback because users who think your price is too high cancel silently rather than respond to outreach), and decision-maker status for B2B (the sales-team handoff signal that determines whether the conversation needs to escalate). Stripe, Vercel, Linear, Notion, Figma, Datadog, PostHog, Anthropic Claude Pro and Max trials, Cursor Pro trials, GitHub Copilot trials all run variants of this pattern. This template gives you the mid-trial structure plus an end-of-trial version that captures why trials didn't convert — the two together close the feedback loop on the most economically valuable transition in SaaS.

From mid-trial prompt to qualified outreach in 24 hours

The feedback prompt fires at the mid-trial mark — day 3-5 for a 14-day trial, day 7-10 for a 30-day trial, scaled appropriately for shorter or longer trial windows. The trigger can be email, in-app modal, or both (the in-app modal converts higher; the email captures users who haven't logged in recently). The form is 5-8 questions in a single page, with conditional logic so users who self-identify as "having found value" see a different set of follow-up questions than users who self-identify as "not yet finding value." The activation question is the first field — a binary or 3-point scale that classifies the user into found-value / on-track / blocked. Users who report blocked status see follow-up about the specific blocker (which feature, which workflow, which integration) and the likelihood-to-convert NPS-style score. Users who report found-value status see follow-up about pricing perception and decision-maker context. Pricing perception is a structured field (typically "within budget," "at the upper limit," "above budget but I'd justify it for X," "above budget and I can't justify it") because the open-text version of this question gets ignored by users who don't want to negotiate. Decision-maker status is captured as "I am the decision-maker," "I'm recommending to a decision-maker," or "this is a personal trial." On submission, the data routes simultaneously to product analytics for cohort tracking (users who reported blocked status and didn't convert form a cohort the product team learns from), to CRM (HubSpot, Salesforce, Pipedrive, RD Station for Brazilian B2B) for sales-team outreach when the criteria match (decision-maker = yes + likely-to-convert high + specific blocker that sales can address), and to the trial-management system for any in-trial offers triggered by the response (e.g., trial extension for users who report needing more time, pricing-tier downgrade for users who report pricing as the blocker).

What's included

Each field below is here because experienced trial-conversion teams have learned it predicts the trial-to-paid decision. Customize the fields per your trial length and your ICP, but keep activation, pricing perception, and decision-maker status because those are the three predictive signals that most teams under-capture.

Built for the SaaS categories where trial conversion is the dominant revenue lever

• B2B SaaS (the primary use case)

  The category where trial-to-paid conversion most directly drives revenue. Standard B2B SaaS trial conversion rates run 15-25% for self-serve products, 25-40% for sales-assisted trials; moving these by even 2-3 percentage points materially impacts the company's growth trajectory. The trial-feedback prompt at mid-trial reveals the conversion blockers in time to address them — sales-team outreach to high-fit users who reported a specific blocker that sales can resolve typically lifts conversion 5-15% for the responding cohort. The fields that matter for B2B specifically: decision-maker status (so the sales team knows whether to expect a multi-stakeholder conversation or a solo trial-user buying personally), team size (so the sales motion matches — SMB vs. mid-market vs. enterprise), pricing-tier preference (the user's mental anchor for what they'd pay), and the specific feature blocker. Stripe, Notion, Linear, Figma, Vercel, Datadog, PostHog, Snowflake, MongoDB Atlas all run variants of this. For Brazilian B2B SaaS (RD Station, Pipefy, Conta Azul, Bling, Omie, Movidesk, Octadesk, ContaWise), the same pattern applies with the additional Brazilian context that conversion to paid often involves a sales-assisted path even for products that look self-serve, because Brazilian B2B buyers expect a human conversation for purchases above certain thresholds (typically R$2k+/month).

• Developer tools (often free-tier-to-paid rather than time-bounded trial)

  Different model than time-bounded SaaS trials. Most developer tools have a free tier with usage limits, and the "trial" is the period when a user is approaching or hitting those limits — which is when the feedback prompt should fire. Vercel's free tier limits before requiring paid, GitHub Actions minute limits, Anthropic Claude API free credits, OpenAI API free credits, Cursor's free tier limits, GitHub Copilot Free tier limits, PostHog's free tier event limits, Stripe's processing limits before fees scale. The feedback at the "approaching limit" moment reveals whether the user is hitting limits because they're getting value (positive signal — likely to convert) or because they're testing without genuine intent (negative signal — unlikely to convert without intervention). The fields for developer tools differ in vocabulary: language and framework, project scale, team size, willingness to upgrade vs. workaround, pricing model preference (per-seat vs. usage-based vs. flat). For developer-tool trials specifically, the open-text "what would unblock you to upgrade" question tends to be unusually high-signal because developer users articulate their specific friction better than other personas.

• Consumer subscription with trial

  Netflix, Spotify, Apple Music, Disney+, Apple TV+, Apple Fitness+, Amazon Prime, Audible, Kindle Unlimited, Calm, Headspace, MasterClass — all use time-bounded free trials (typically 7, 14, or 30 days) that convert to paid automatically unless the user cancels before the trial ends. The trial-feedback prompt here is less about influencing the conversion decision (consumer subscriptions convert automatically) and more about (1) reducing involuntary churn from users who would have wanted to cancel but didn't notice the trial-end, and (2) gathering content-quality and discovery-quality feedback that informs product decisions. Mid-trial prompts in consumer subscriptions are often gated to engaged users (the user has used the product N times) so the feedback reflects actual experience rather than trial-window randomness. For Brazilian consumer subscription (Globoplay, HBO Max Brasil, Disney+ Brasil, Spotify Brasil, Netflix Brasil), the same pattern applies with Portuguese-language prompts and content-availability feedback being especially important because Brazilian streaming-rights are different from US.

• Vertical SaaS (industry-specific products)

  Trial-feedback for vertical SaaS captures industry-specific blockers that horizontal SaaS doesn't surface. A vertical SaaS for restaurants captures "does it integrate with my POS" as the dominant blocker; a vertical SaaS for clinics captures "does it integrate with my EHR" as the dominant blocker; a vertical SaaS for construction captures "does it work with the project-management tool we already use." The integration-blocker is so often the dominant trial-feedback signal in vertical SaaS that the form should surface it as a structured field with the named common integrations as multi-select options. For Brazilian vertical SaaS, the locale-specific integration tools matter: PDV anchors (Stone POS, Linx, Sischef, Saipos) for restaurants; EHR anchors (Tasy, MV, Memed, iClinic, Doctoralia) for clinics; construction anchors (Sienge, Builders 360). For Spanish vertical SaaS, the equivalent local-platform integrations matter similarly.

• AI products with trial credits or trial period

  The most-recently-grown SaaS category for trial dynamics. Anthropic Claude Pro and Max trial, Cursor Pro trial, GitHub Copilot trial, Perplexity Pro trial, Gemini Advanced trial, ChatGPT Plus trial, the local-language AI product trials. The feedback for AI products differs in content from other SaaS because the value perception is unusually personal — "the model felt smart at my task" vs. "the model didn't get what I was asking" is a more important signal than feature parity. The fields that matter: primary use case (writing / coding / research / customer support / data analysis), model performance perception (how the AI compared to expectations), specific failure cases (where did the model not do well), and the integration intent (API / web / extension / mobile). For Brazilian AI product trials, language-specific performance is critical — "how well did the model respond in Portuguese?" is a separate question from "how well did the model respond in English?" because most foundation models still have stronger English performance than Portuguese performance.

• Enterprise software (longer trials, multi-stakeholder decisions)

  Different trial dynamics than self-serve SaaS. Enterprise trials typically run 30-90 days (vs. 7-14 for self-serve), involve multiple stakeholders on the buyer side (the user evaluating, the user's manager, the IT/security team, procurement), and require a more structured trial-management process. The feedback prompt for enterprise trials is typically less of a self-serve survey and more of a structured account-management check-in — the customer-success manager sends the form as part of weekly trial-status touchpoints. The fields that matter: stakeholder status (which role is responding — evaluator, decision-maker, IT/security review, procurement), specific use case validated (or not), security/compliance review status (passed / in progress / blocked / not started), integration requirements assessed (passed / in progress / blocked / not started), and timeline to decision. For Brazilian enterprise SaaS (the large Brazilian SaaS players selling to multinational corporate buyers — TOTVS, Senior Sistemas, Linx for retail, Movile portfolio), the same enterprise-trial dynamics apply with Brazilian-specific compliance items (LGPD review status, fiscal compliance for SaaS providers) added to the checklist.

Tune the form to your trial length, your ICP, and your conversion motion

Start with the timing. Mid-trial prompts at day 3-5 of a 14-day trial, day 7-10 of a 30-day trial, day 15-30 of a 90-day enterprise trial. End-of-trial prompts at day 12-13 of a 14-day trial, day 28-29 of a 30-day trial, day 85-90 of a 90-day enterprise trial. Send both — the mid-trial captures the in-window conversion-influencing signal, the end-of-trial captures the post-decision why-didn't-it-convert signal. Decide whether the prompt is email-only, in-app-only, or both. The dual approach (email plus in-app) converts highest because email reaches users who haven't logged in this week and in-app reaches users who are actively engaged. Customize the activation question to your product — "have you completed X" is more specific than "have you found value" and produces more actionable signal when X is your product's key activation event. Customize the pricing-perception question to your pricing tiers — surface the specific tier you're hoping the user will choose and ask whether it matches their budget. For B2B, the decision-maker status field is non-optional — the sales team's outreach motion depends entirely on whether the user is buying personally, recommending to their team, or evaluating on behalf of a larger procurement process. Add conditional save-attempt logic for users who report "won't convert" — surface trial extension for users who need more time, downgrade-tier for users who report pricing as the blocker, integration-help for users who report integration as the blocker. Send the responses to product analytics (Mixpanel, PostHog, Amplitude, Segment as the routing layer), to CRM (HubSpot, Salesforce, Pipedrive, RD Station for Brazilian B2B) for sales-team outreach triggers, and to the trial-management system (Stripe Billing, Chargebee, Recurly, Vindi for Brazilian recurring) for any trial-extension or pricing-tier adjustments. Translate the form into the languages of your trial users — Brazilian and Spanish-speaking B2B trial-users respond at higher rates to native-language prompts.

SaaS trial feedback FAQ

Related templates