components.email

Engagement that stays
in the inbox

Polls, tabs, timers, and video. Interactive components that keep people in the email. Export HTML that fits your ESP and CRM campaign workflow.

See it in action

Fewer hoops, same outcomes

Classic campaigns chain actions, CTA clicks, site loads, cookie consent and form submits.Each step loses people. Fold the valuable action into the email: more engagement, less application-switching, creative built for curiosity.

Same campaign goal, fewer steps when the survey stays in the inbox.

Typical pathHandoffs across inbox, website, and form
Sent
Opened
CTA click
Site opens
Survey
Submit
In-email pathSurvey and confirmation without leaving the inbox
Sent
Opened
Survey in email
Submit

What we've seen in usage

Components

Each type is a focused, exportable block. Able to be tuned for client quirks, measurement, and brand-level craft.

Timers

Live countdowns for launches and deadlines. Before and after states, styled to match your brand, with open-time insights.

Tabs

Layered stories in a small footprint; taps reveal what caught attention so the next send can follow the thread.

Polls

Quick votes with per-recipient results and optional hidden tallies until someone takes part. Curiosity without leaving the inbox.

Video

Motion that stays in the message. Webp-first delivery, sensible fallbacks, and formats that respect client limits.

Geolocation

Hero creative that shifts with where someone opens. Regions, countries, or areas you define on a map.

Imagery

Hero art with tap or hover hotspots so detail and discovery stay in the email, not on a landing page.

Reminders

Calendar nudges and secondary prompts that keep momentum inside the same send.

Social feeds

Fresh posts from your connected channels rendered into the message. Social proof that does not send people away.

Time-of-day

Creative that shifts with morning, afternoon, or evening windows. Allow your creative to remain relevant regardless of open time.

Weather

Hero swaps from live conditions at open time. Rain, sun, snow, and buckets you control. Magic from the user’s perspective.

Maps

Store maps with ranked pins from the user’s nearest locations surfaced in one static image. No find a store page required.

GIFs

Personalised or sequenced GIF frames with merge and overlay support. Motion without a browser tab.

Twelve starting points. Built for curiosity and sending.

FAQs

How components, ESP export, and pricing fit together for production teams.

What does this platform actually help my team do?

It helps CRM and lifecycle teams design interactive email components. Forms, polls, timers, tabs, video, and more. Keep the experience in the inbox, preview it, and export HTML for your ESP. The goal is reliable, repeatable creative without rebuilding fragile markup on every send.

Do we need a developer for every campaign?

No. We’ve created a component editor that allows users to configure the component, preview it, then export HTML for your ESP. Developers matter when you need custom endpoints, data contracts, or deeper integration.

Will this work with our CRM/ESP stack?

Exports are portable HTML intended for major ESPs and CRM-connected senders. Braze, Salesforce Marketing Cloud, Klaviyo, HubSpot, Customer.io, and platforms in that class. You wire personalization the same way you would for any template, using your vendor’s merge tags and rules.

How is pricing structured as we grow?

Two parts: a platform tier for workspace access, plus server usage tied to which component types you run and how much traffic they see. The calculator on this page reflects that mix so estimates track production load instead of a flat seat count alone.

How can we evaluate this before a full rollout?

Treat it like any high-stakes creative change: pick a pilot audience, ship one or two components in a real campaign, and compare engagement and completion to your usual flow. Preview and test sends in the inbox clients you care about, then expand once rendering and results look right.

Send feedback

Tell us what broke or what you wish existed—we already capture page and module context.