Reward Survey Completers with a Discount Code
Pair a targeted survey with a discount code on the thank-you screen — incentivize the feedback you actually asked for, at the moment it matters.
Incentives are great at getting people to act — and terrible when you bolt them onto everything. Pay for every bug report and you get noise: people farming the reward, low-effort submissions, a pipeline you have to wade through. The signal gets worse, not better.
What incentives are good at is getting people to finish something you asked them to do, at a moment that matters. That is exactly what a survey is: a specific question, fired at a specific moment. So that is where the reward belongs.
SeggWat does this with the survey widget's thank-you screen. Finish the survey, and the last frame shows a discount code and a button. No separate reward system, no per-user billing plumbing — the survey already knows the person completed it.
Why a survey, not a feedback button
A feedback button is open-ended and unsolicited. You don't know who will click it, what they'll say, or whether a reward would help. A survey is the opposite:
- Targeted. Trigger it on
/pricingwhen someone hesitates, or in your cancel flow when intent is highest. - Bounded. You asked one or two questions. A reward nudges people to finish them, not to invent reasons to contact you.
- Attributable. Completion is a clean signal. The thank-you can be shown only to people who answered every required question.
That last point is the whole game. You're rewarding a completed answer to a question you cared about — not buying volume.
How it works
- Create a coupon in your billing provider — Stripe, Polar, or anywhere you take payment. Say
SAVE30, 30% off the first three months. - Build a survey in SeggWat and target it where it counts (pricing page, post-onboarding, cancel flow).
- Set the survey's thank-you screen to Discount offer (coupon + CTA): a headline, the coupon code, a button label, and a button URL — typically your checkout or upgrade page with the code prefilled.
- Choose who sees it. Show the offer to everyone, or only to people who completed every required question.
- Publish. When a respondent finishes, the widget renders the code in a copyable block and keeps the thank-you open a few extra seconds so they can grab it.
You own the code; SeggWat just shows it at the right moment. Your billing system handles redemption exactly as it would for any coupon — SeggWat never touches your billing data.
Where it earns its keep
Two placements do most of the work:
The pricing-page survey. Catch someone weighing the plans. Ask what they're evaluating and what's holding them back — then close with a discount that nudges the decision while you've got their attention.
The cancel-flow survey. Ask what's not working on the way out. A win-back offer on the thank-you screen turns a churn signal into a second chance, and you keep the answer either way.
In both cases the reward is doing what incentives are actually good at: getting a specific action finished at a high-intent moment.
Get started
Surveys are a Pro feature. If you're on Pro, this takes a few minutes:
- Create a coupon in Stripe or Polar (or your billing tool of choice).
- Build a survey and set its thank-you screen to a discount offer in the survey widget.
- Target it at a moment that matters and publish.
That's the whole loop — a question worth answering, rewarded the moment it's answered.
Related Posts
Feature Request Template: A Copy-Paste Format That Gets Used
A simple, copy-paste feature request template — plus a shorter form for your users and a weekly process to triage requests without drowning in a spreadsheet.
The Public Trust Layer: Pair a Status Page With a Feedback Board
Users don't just want features — they want to trust you. Here's how a public status page plus a public feedback board and changelog form a simple trust layer for a small SaaS.
In-App Feedback for iOS, in Two Lines of SwiftUI
The SeggWat iOS SDK drops a native SwiftUI feedback button into any app — bug reports, screenshots, star and NPS ratings — with zero dependencies and no web view. It submits to the same project as your web widgets.
