Sales sequence

How a sales sequence works

A sales sequence turns a follow-up plan into software. The rep or manager writes the steps once, sets the delay between them and enrolls contacts. The tool then sends automated emails on schedule and creates tasks for the steps that need a person, such as a call or a personal note.

HubSpot's sequences tool is a typical example 1. It sends a series of personalized, timed sales emails and follow-up tasks to contacts over time 1. Steps can be automated emails, manual email tasks, call tasks, general tasks and social tasks such as connection requests 1. Each email step has a delay, and HubSpot allows a delay of up to 90 business days 1.

Most sequences follow the same shape.

• An opening email that explains why this person and why now.
• One or more follow-up emails, each with a new reason to reply.
• A call or social step for contacts who open but do not answer.
• A final message that closes the loop politely.

The stop rule matters as much as the steps. In HubSpot, contacts are automatically unenrolled when they reply to any email in the sequence or book a meeting through a meeting link in a sequence step 1. That rule keeps a buyer who already answered from receiving a scripted follow-up the next morning. Teams can also edit the unenrollment triggers and use workflows to enroll or unenroll contacts automatically 1.

A sequence only performs as well as the list it runs on. Each contact needs the right role, a current company and a working address. A buyer persona decides who belongs in the sequence, and the copy should speak to that persona's problem rather than the product's features.

What decides whether a sequence works

Four variables decide most of the outcome, and only one of them is the wording.

The list comes first. A sequence multiplies whatever it is given. A list built from stale records sends every step to people who changed jobs, which is why data decay shows up as bounces and silence. Each address should be checked before enrollment, and a catch-all email domain needs a policy decision, because it can accept mail for people who do not exist.

The sending rules come second. Google requires senders to Gmail accounts to keep spam rates reported in Postmaster Tools below 0.3% 4. Senders of more than 5,000 messages a day to Gmail must also support one-click unsubscribe on marketing messages 4. A sequence that sends four emails to a weak list produces four chances to be reported, so the bounce rate and complaint rate of one campaign can affect the domain reputation of every rep on that domain.

Timing comes third. Gaps that are too short read as pressure, and gaps that are too long lose the thread. The right spacing depends on the deal size and the buyer's pace, so teams test it rather than copy a template.

The exit rule comes fourth. Replies, meetings, bounces and opt-outs should all end the sequence for that contact. A contact who says no thanks and still receives step three is a complaint waiting to happen. The tool handles replies and meetings, and the team has to make sure bounces and unsubscribes are wired in too.

Example of a sales sequence build

An SDR manager wants a sequence for a list of named target companies. The list comes from a company employee search, which RichAPI bills at 0.1 credits per result, including results that a later title filter discards 3.

Build a sequence-ready list
  linkedin_company_employees_search   page until elements is empty
  title filter in your own code       keep the roles the sequence speaks to
  email_finder on survivors           misses return billed false
  email_verifier on hits              route on the verdict
  write a CSV                         import into the sequencer
  enroll                              stop on reply, meeting, bounce or opt-out

The playbook's worked example uses stated counts. Forty companies with 60 employees each return 2,400 results, which bill 240 credits 3. After the title filter, 520 people survive 3. The email_finder step at 5 credits per call finds 310 addresses for 1,550 credits, because the 210 misses return billed false 3. Verifying the 310 hits at 2 credits each adds 620 credits 3.

The verification step is the gate. RichAPI's verify-before-push playbook bills email_verifier at 2 credits per call and treats invalid and catch-all verdicts as results that bill 2. Rows that come back with no verdict are re-queued for a later run instead of being pushed as unverified 2. The push job should select rows marked valid, because a job that only excludes invalid rows also pushes rows that were never checked 2.

RichAPI has no sending or sequencing product, so the run ends at a file 3. The team imports that file into its own sequencer, where the steps, delays and exit rules live. Each row carries its verdict and the date it was checked, so a bounce can be traced back to the run that approved it.

Sales sequence vs sales cadence

The two terms are often used as synonyms. In practice, cadence usually means the rhythm of touches, and the sequence is the built object in a tool that delivers that rhythm.