Sequence spec
The second stage picked for Q4: sales follow-up on accounts showing a commercial trigger. What fires it, who gets it, what they get, and the guardrails.
Who enters
Only accounts that pass the trigger rule. A LinkedIn click that lands on the site is a Weak signal and never enters, however many times it happens. It goes to retargeting or nurture instead.
The two signals that feed this sequence most often:
- A hit on the Datadog migration page (
/product-comparison/migrate-from-datadog) - Approaching the paid-plan ceiling
Which pages mean what
| Page family | What it tells you | What to do |
|---|---|---|
/product-comparison/migrate-from-datadog | Decision made, executing | Sales, now |
/product-comparison/signoz-vs-X | Evaluating, SigNoz shortlisted | Sales |
/comparisons/X-vs-Y | In market, SigNoz not shortlisted | Retarget into consideration |
/guides/[competitor task] | Using a competitor, in friction, unaware of SigNoz | Nurture |
The page also tells you who's reading. Docs and guides mark the champion. Pricing and comparison pages mark the person who signs.
Who gets the email
The deanonymised visitor if we have them. If not, the most senior infrastructure title at the account. One contact per account.
The sequence
| Day | Step | Detail |
|---|---|---|
| 0 | Founder-sent. Names the signal in the first line. Carries the cost card. | |
| 3 | Wait | |
| 3 | Condition | Replied? |
| Yes | Stop. HubSpot deal created, owner assigned. | |
| No | LinkedIn invitation on day 6, LinkedIn message on day 8. Both native Lemlist steps. |
The day-0 email
Subject: your Datadog bill at {{serviceCount}} services
{{firstName}}, someone at {{companyName}} hit our Datadog
migration docs twice this week.
Ran your numbers at {{serviceCount}} services / {{ingestGb}} GB
a day. Attached is what that costs on both.
Estimate, not a quote. Happy to be wrong on the ingest volume.
Worth 20 minutes?
The cost card
One image per account, generated, never hand-made. Their logo, estimated monthly cost on Datadog, the same workload on SigNoz Cloud, the difference, and the basis for the estimate. "Estimate only" printed on the card.
How it's made: Clay estimates scale from headcount, Datadog job posts, and repo count. An HTML template renders to PNG. The public URL goes into the costCard column. Lemlist pulls it at send time as an image variable. Zero effort from the sender, which is the only reason things like this get used.
One thing to get right: Datadog prices per host and per GB. SigNoz prices per GB. The card needs both host count and volume, or it has to say which one it's using.
Why a number and not a screenshot: SigNoz's edge against Datadog is the bill, not the UI. Lead with what you're actually better at.
A wrong number to an SRE ends the thread. A labelled estimate that invites correction starts one, and the correction tells you their real ingest volume.
Guardrails
| Rule | Value |
|---|---|
| Response SLA | 24 hours from signal to first touch |
| Weekly cap | 25 accounts |
| Suppressed | Open opportunity. Touched in the last 30 days. |
| Contacts per account | One |
Routing to Slack
Signals push to a Slack channel. Three sort orders, set by signal type in HubSpot, not chosen by the rep each morning:
- Frustration signals (ceiling hit, migration-doc error): newest first. They go stale in a week.
- Deadline signals (renewal, migration in progress): nearest deadline first. They get more urgent.
- Everything else (multiplayer, integration connected): oldest first, so nothing sits.
The cap needs a floor per queue, or the newest-first lane eats all the attention and the oldest-first lane never gets touched.
Queue depth per rep tells you who's idle and who's saturated without asking anyone.
The experiment
Same signal, same email text, half the accounts get the card and half get a plain sentence with the number. Measure reply rate, and whether the replies correct the number. At 25 accounts a week the first read takes a month.
Mock
A mock of the Lemlist campaign screen with this sequence built out is in the working files as signoz_lemlist_mock.html. Custom media, image variables, and Liquid syntax are documented Lemlist features. LinkedIn invitation and message are native steps.
Source: signoz_assignment_progress.md, Q4 sections from 5 and 6 Sep 2026. Page ladder from Q3 section, URL corrected 6 Sep.