Review Request Email for SaaS

The trigger is everything. Send this the morning after a user completes their first real workflow and sees a result, not at signup. For a recurring-revenue tool that moment is the first closed billing cycle with a reconciled MRR number. For a reporting tool it is the first dashboard built. For a meeting scheduler it is the first booking confirmed. Wire the send to that product event through your ESP, not to a calendar date seven days after account creation.

Timing: send 24 to 72 hours after the activation event, on a Tuesday or Wednesday at 10am in the user's timezone. B2B inboxes are loudest midweek. A day-9 send beats a day-1 send by a wide margin because the user has actually formed an opinion of the product.

The offer matters more than the subject line. A concrete thank you converts better than a vague one. A $10 to $20 gift card, a one-month credit, or a charity donation will outperform 'help us out.' Route the incentive through G2's reviewer program if you link to G2, because G2 forbids direct paid incentives and will strip reviews that violate the rule. Capterra runs its own reviewer reward program with the same restriction.

The copy angle is outcome-first. Lead with the result the user already got, then ask in one sentence. 'You just closed your first billing cycle. If that number was useful, a 60-second G2 review helps another RevOps leader find us' outperforms 'We hope you are enjoying Recurlio.' In SaaS tests, outcome-first review asks convert 3 to 5x the rate of generic praise asks.

The CTA is one link to one review site. Deep-link to the write-a-review form on G2 or Capterra, never the product profile page. If you split traffic between two review sites, conversion drops on both. Pick the site that already has momentum for your category.

Numbers you can plan to: a post-activation SaaS review email with a $15 thank you typically converts 6 to 12% of opens to a published review. A monthly blast to the whole user base converts under 1%.

B2B inboxes are brutal. Outlook runs on Word's rendering engine. Gmail clips messages over 102kb. Apple Mail enforces dark mode by inverting colors. Here is how this template survives all three.

Nested HTML tables, not divs or flex. Email clients strip CSS and ignore flexbox. Every layout block is a table inside a table, with widths set on the td, so the structure holds in Outlook 2007 through Outlook 365.

Inline CSS on every element. Gmail and Outlook drop the <style> block for some accounts. Each td, p, and a carries its own font, size, and color inline, so the email reads correctly even when the head is removed.

Bulletproof VML button for Outlook's Word engine. Standard CSS buttons render as flat rectangles in Outlook, with no padding and no background fill. A VML rectangle wrapped in mso conditional comments forces the rounded, filled button to render in Word-based Outlook, and keeps the link clickable across the full area.

Live text, not images. Live text reflows on mobile, scales for accessibility, and loads instantly. Images get blocked by default in many Outlook and enterprise setups. This template uses text for the headline, body, and social proof, with images reserved for the logo only.

Dark-mode color-scheme meta. A meta name color-scheme set to light dark, plus a supported-color-scheme, tells Apple Mail and Outlook to respect your palette instead of auto-inverting the white background to black.

One mobile media query. A single max-width 480px query shrinks padding and font size on phones. More queries mean more clients that break.

Web-font fallbacks. The font stack starts with system fonts and falls back through Helvetica and Arial. Loaded web fonts fail in Outlook and most Gmail setups, so the design never depends on them.

Klaviyo: Open the campaign or flow email. Drag an HTML block into the canvas, or choose the HTML email type for a full-HTML build. Paste the exported HTML. Swap the Recurlio brand name, the #3b5bdb brand color, the G2 link, and the logo URL. Wire merge tags: {{ first_name|default:'there' }} in the greeting, {{ organization.name }} for the account, and an event property like {{ event.workflow_name }} for the outcome line. Set the flow trigger to a product event such as 'First Billing Cycle Closed' rather than a time delay from signup.

Mailchimp: Create a campaign, choose Code your own, then Paste in code. Paste the full HTML into the editor. Replace brand text, colors, and links. Wire merge tags: *|FNAME|* for first name, *|COMPANY|* for the account. Pass the outcome as a merge field if you want it dynamic, or hardcode the workflow name for a single-send campaign. Trigger the send from a customer journey tied to the activation event.

Testing: Send a test to a Gmail account, an Apple Mail account on an iPhone with dark mode on, and Outlook on Windows. Confirm the button is filled and clickable in Outlook, the headline and body are live text (select them with your cursor to check), and the layout holds at 375px wide. Run it through Email on Acid or Litmus if you have a license before you send to the full segment.