Onboarding Sequencer

Send behavior-triggered onboarding emails that adapt to user actions, hand off cold accounts to sales, and stop spamming activated ones.

Send behavior-triggered onboarding emails that adapt to user actions, hand off cold accounts to sales, and stop spamming activated ones. Most onboarding sequences treat all users the same. This branches by behavior and stops the moment they activate.

This is the whole blueprint, nothing held back: the model, the tools, the exact prompt, the source on disk, and the setup. Everything you need to run Onboarding Sequencer yourself is on this page, and it deploys in an afternoon.

What it does

Onboarding Sequencer handles the work end to end:

  • Record entry point and goal at signup to personalize the sequence
  • Listen for activation events and stop emailing users who already activated
  • Send the next email based on actual behavior, not a fixed cadence
  • Hand off PQL accounts to sales after 7-day activation stall

The anatomy

An agent is a composition, not a prompt: a model, the tools it is allowed to call, the integrations that give those tools reach, and the rules that keep it honest. Here is Onboarding Sequencer on one card.

Onboarding Sequencerblueprint
Model
claude-sonnet-4-6
Tools
ingest_userdetect_actionsend_next_emailhand_off_to_sales
Integrations
ResendZod
Guardrails
stop sending the moment a user activates. never email an active user a "have you tried…" prompt.; sales handoff requires both pql signal and 7-day stall

The instructions

Every run is governed by this prompt. It is short on purpose: enough to make Onboarding Sequencer reliable, not so much that it can misread itself. Copy it as a starting point for any agent you build.

Onboarding Sequencer
You are an onboarding strategist. You guide new users from signup to activation without being annoying. WORKFLOW: 1. Call ingest_user on signup to record the entry point and goal. 2. Call detect_action to listen for activation events (first deploy, first invite, first export). 3. Call send_next_email based on what they have and have not done yet. 4. Call hand_off_to_sales when an account hits PQL criteria but stalls before activation. RULES: - Stop sending the moment a user activates. Never email an active user a "have you tried…" prompt. - Sales handoff requires both PQL signal and 7-day stall. - Subject lines max 6 words, no exclamation marks. - Every email must offer one action; never two CTAs.

The source, on disk

Three files carry the whole agent: the definition with its tools, the environment it expects, and the setup. Walk them.

onboarding-sequencer/onboarding-sequencer.ts1.2 KB
1import { agent, tool } from "@agent-sdk"
2import { z } from "zod"
3
4const userInput = z.object({
5 userId: z.string(),
6 signupSource: z.string(),
7 goal: z.string().optional(),
8})
9
10export default agent({
11 model: "claude-sonnet-4-6",
12 permissionMode: "bypassPermissions",
13 maxTurns: 30,
14 systemPrompt: `...`, // see System Prompt section above
15 tools: {
16 ingest_user: tool({
17 description: "Record entry point and stated goal at signup",
18 inputSchema: userInput,
19 execute: async ({ userId, signupSource, goal }) => { /* persist */ },
20 }),
21 detect_action: tool({
22 description: "Listen for activation events",
23 inputSchema: z.object({ userId: z.string() }),
24 execute: async ({ userId }) => { /* events[] */ },
25 }),
26 send_next_email: tool({
27 description: "Send the right next email based on user state",
28 inputSchema: z.object({ userId: z.string() }),
29 execute: async ({ userId }) => { /* via Resend */ },
30 }),
31 hand_off_to_sales: tool({
32 description: "Notify sales for stalled PQL accounts",
33 inputSchema: z.object({ userId: z.string() }),
34 execute: async ({ userId }) => { /* webhook */ },
35 }),
36 },
37})

The business case

If you run an agency, Onboarding Sequencer is also a product. It sells into b2b saas, plg products, growth teams, and the numbers work at very small scale.

$2,400

setup you can charge

$400/mo

monthly retainer

4

jobs off your plate

Ship it

The whole install is a handful of commands and the keys from the env file. Run the list, then point Onboarding Sequencer at real work.

Deploy checklist

0 of 4

That is the entire blueprint: one model, 4 tools, and a prompt. Built by hand it costs you an afternoon. Inside Ultron it costs you a sentence, because you can build this exact agent in the workforce and watch it run before you commit to anything.

Build Onboarding Sequencer in Ultron

1
Describe what you want

Start from this blueprint or your own words. Ultron reads the intent and picks the tools.

2
It builds the agent

The model, the tools, the prompt, the console. Assembled in front of you, nothing to wire.

3
Watch it run

Test it live in the chat, then put it to work. You review what it does, it does the rest.

Keep reading