Name your product and Juma researches it, designs a 5 to 7 email onboarding sequence around your activation moment, then writes every email end to end.
Give Juma a product name and URL and it reads the site for the real features, value props, and audience. Then it designs the onboarding sequence before writing a word of copy: how many emails, the send timing, and the single goal for each one, all anchored to the product's activation moment, the first action a new user takes to feel the value. Most onboarding sequences run 5 to 7 emails over about two weeks, with the welcome email arriving within seconds of signup.
Then Juma writes every email: subject line, preview text, and body copy, and delivers them as a styled HTML preview, a PDF, or plain text ready to paste into the team's email tool.
An onboarding sequence works when every email moves the user toward one outcome: the activation moment, the first action that makes the product click. Juma researches the product, identifies that moment, and builds the sequence backward from it: the welcome email drives the single first action, the next few reinforce it and introduce the features that follow, and later emails deepen the habit. The output is a sequence map, one row per email with its send timing, its single goal, and the messaging angle, before any copy is written. The team approves the structure first, so the emails are never a feature dump.
Map the onboarding sequence to our activation moment first. One row per email with send timing, the single goal, and the messaging angle, before writing any copy.
The body copy never gets read if the subject line does not earn the open. Juma writes two or three subject line options per email and a matching preview text for each, then explains the angle behind them. The lines follow what the data supports: 30 to 50 characters, front-loaded value, no all-caps, and a preview text that extends the subject rather than repeating it. First-name personalization is played out, so Juma leans on specificity and curiosity instead. The team picks the winner per email or runs the options as an A/B test in their email tool.
For each email, give me two subject line options under 50 characters plus matching preview text, with a one-line note on the angle so we can pick or A/B test.
A fixed Day 1, Day 3, Day 5 drip sends the same email whether or not the user has acted. Behavior-triggered sequences respond to what the user actually did, and they outperform time-based drips. Juma rewrites the sequence as a set of triggers: send this when the user signs up but has not completed the key action in three days, send that when they hit the activation moment, hold the rest until they are ready. It also adds completion triggers, so a user who activates quickly graduates out of onboarding instead of getting the next scheduled email. The output is the trigger logic next to each email, ready to set up in the team's email or product-analytics tool.
Rewrite the sequence as behavior triggers instead of fixed days: tie each email to a user action or inaction, and add completion triggers so activated users graduate out of onboarding.
A 14-day free trial, a freemium signup, and a prospect who booked a demo are at different points and need different sequences. A trial sequence races to the activation moment before the clock runs out and adds an upgrade nudge near day 10. A freemium sequence has more room to educate and build the habit before prompting a paid plan. A demo-booked sequence warms the prospect for the call and reinforces value after it. Juma produces the variant for the motion the team names, reusing the research and adjusting the timing, goals, and upgrade asks to fit. Name two motions and Juma builds both side by side.
Adapt this sequence for a 14-day free trial and for a freemium signup. Adjust the timing, the per-email goal, and the upgrade ask for each motion, and show them side by side.
The activation messaging that works in email also works in the product and after the user goes quiet. Juma adapts the onboarding emails into in-app messages: shorter, tied to the moment the user hits a feature, so the email and the in-product nudge reinforce each other. It can also spin up a re-engagement series for users who signed up but never activated, reusing the same value props with a different opening that acknowledges the gap. One research pass feeds several channels, so the team is not rewriting the same value story three times. The re-engagement series is its own job worth running as a separate sequence.
Repurpose this onboarding sequence into in-app messages tied to each feature moment, and draft a short re-engagement series for users who signed up but never activated.
A Juma Project is a shared space where the team stores everything Juma needs to know about a client or product. Create one project per brand, add context as the team learns more, and Juma uses what is relevant every time the flow runs. For onboarding emails, this is what makes the sequence sound like the brand and target the right activation moment, instead of a generic best-practice draft.
Brand Voice & Tone Guide
How the brand sounds: warm or direct, playful or precise, the words it uses and avoids. With this in the project, every email comes out in the brand's voice. Without it, Juma infers a reasonable tone from the website and the team edits for voice afterward.
Product & Activation Map
What the product does, the activation moment, and the order features should be introduced. Juma builds the sequence around this. It is the difference between emails that drive the one action that matters and emails that list every feature in the first message.
ICP & Audience Segments
Who is signing up and how they differ: free trial vs. freemium, self-serve vs. sales-assisted, role and seniority. Juma uses this to pitch the copy at the right level and to build separate sequence variants per segment when the motions differ.
Existing Emails & ESP Templates
Past emails that performed, the design system, and the email tool the team uses. Juma matches the house style and formats the output to drop into the existing templates, so the sequence ships without a reformatting pass.
Add a short description to each knowledge item in the project's info field so Juma knows what each file contains and when to use it. For example:
A product name and URL, or a short description of what the product does. Juma researches the site for the real features and value props, then asks for anything it could not find, like the activation moment or the target segment. No integration or file upload is required to start.
If the team adds a brand voice guide and a product map to a Juma Project, the sequence comes out in the brand's voice and targets the right activation moment on the first pass. Without a project, Juma infers a reasonable tone from the website and the team adjusts for voice in review.
Five to seven emails over about two weeks is the proven range for onboarding, with one clear goal per email and the welcome arriving within seconds of signup. Juma proposes a count based on the product's complexity and the signup motion, then lets the team adjust before writing.
More is not better. A short, focused sequence that drives the activation moment beats a long one that tours every feature. Juma also adds completion triggers, so a user who activates early graduates out of onboarding instead of receiving the rest of the scheduled emails.
Yes. Ask Juma to key each email to a user action or inaction instead of a fixed day, for example "signed up but has not completed the key action in three days." Behavior-triggered sequences respond to what users actually do and recover a meaningful share of users who would otherwise go quiet.
Juma returns the trigger logic next to each email, ready to set up in the team's email platform or product-analytics tool. With a product-analytics integration connected, the triggers can map to real activation events the team already tracks, so the sequence fires on actual behavior rather than assumptions.
Juma asks how the team wants it: a styled HTML preview that renders all the emails visually, a clean PDF to share for review, or plain text ready to paste into the email tool. The copy is the same across formats; the choice is about how the team wants to review and hand it off.
Each email arrives complete: subject line options, preview text, and body copy, with the send timing or trigger and the goal labeled. The sequence is ready to load into Customer.io, HubSpot, Braze, Loops, or any email platform without a separate formatting pass.
A generic AI writes emails from the prompt alone. Juma researches the actual product first, designs the sequence architecture around the activation moment, and writes copy grounded in the real features, then delivers it in a ready-to-use format. The research and structure are the work that makes the difference, and they are the parts a blank prompt skips.
The flow handles the repeatable parts: research, structure, first-draft copy, and formatting. The decisions about positioning, which activation moment to bet on, and the final edit stay with the team. Strategy, taste, and judgment stay human; Juma gives the team a researched, structured draft to refine instead of a blank page.
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
Start typing a task and Juma will figure out the rest.
