Speed to Lead

1---
2name: launch-speed-to-lead
3description: >
4  Reply to every new lead within minutes and follow up automatically until the lead books,
5  replies or opts out. Use this skill when the user mentions lead follow-up, speed to lead,
6  auto-reply, instant response, missed leads, nurture sequence, drip emails after an enquiry,
7  owner alerts for new leads, or review requests after a job. Built for Next.js with Resend
8  and Trigger.dev, and the ideas apply to any stack.
9---
10
11# Speed to Lead: Reply in Minutes, Follow Up Without Thinking About It
12
13**RULE: The first reply goes out within 5 minutes, any hour. Every later message checks
14first whether the lead has replied, booked or opted out, and stops if so.**
15
16A lead who has to wait calls the next business on the list. Research on web leads (Harvard
17Business Review, "The Short Life of Online Sales Leads", 2011) found that firms that replied
18within an hour were about 7 times as likely to qualify the lead as firms that replied an
19hour later. Most small businesses reply the next day, or never. Automation closes that gap.
20
21## The sequence
22
23| When | To | Message | Goal |
24|---|---|---|---|
25| Instant | Owner | New lead alert with name, need, and one-tap call and email links | The owner can call while the lead is still on the site |
26| Instant | Lead | Personal confirmation: what happens next, when, who; booking link; phone number | The lead stops shopping around |
27| +1 business day, if no reply or booking (and consent where needed, see "Email rules") | Lead | Short check-in "in case you have more questions", with the answer to the most common one for their request. It reads right whether or not the owner has replied in person. | Restart the conversation |
28| +3 business days | Lead | Proof: a relevant project, review or before-and-after | Build trust |
29| +7 business days | Lead | "Close the loop": should we keep your request open? | A clear yes or no |
30| 1 day after the owner marks the job `won` | Customer | Thank-you and review request (see "Review request after a won job") | Reviews |
31
32Keep each message short, plain and from a person ("Sam at Harbor Plumbing"), with a reply
33address that a person reads. Write in the business's voice. Never pretend a message is
34hand-typed if it is not.
35
36## Stop conditions
37
38Check all of these before **every** follow-up, not only at the start. The confirmation ("we
39got your request") answers the customer's own request, so it needs no marketing consent and
40goes out even after a reply. It still stops for spam, an unsubscribe, a test lead and a lead
41marked `possibleSpam`.
42
43- The lead replied (`repliedAt` is set).
44- The status is not `new` or `contacted`: they booked (see `launch-booking-payments`), their
45  booking was cancelled, or the owner marked the lead won, lost or spam. The owner's own
46  reply (status `contacted`) does not stop the sequence; the customer's answer does.
47- The lead unsubscribed (`unsubscribedAt` is set).
48- The lead is marked `possibleSpam` and the owner has not tapped "Not spam" yet.
49- The lead is marked `isTest` (for example a launch test entry, marked after it was sent).
50- A follow-up needs marketing consent here and `marketingConsent` is false (see "Email rules").
51- The send would land outside business hours for a follow-up (instant replies are fine at
52  any hour; follow-ups wait for the morning in the business's time zone).
53
54## Implementation (Trigger.dev + Resend)
55
56This uses the shared lead model and the `lead-intake` orchestrator from
57`launch-lead-capture`. `lead-intake` starts this task once per lead with a global
58idempotency key. Do not start it from anywhere else.
59
60```ts