Run a single-thread cadence
One decision maker gets the whole cadence: 4 to 6 email and LinkedIn touches over three weeks, each adding something new. Any reply stops it.
single-thread-cadence/SKILL.mdDownload- name
single-thread-cadence- description
- Use this skill when you start outreach to an account. It takes the one decision maker picked for the account, then plans and drafts 4 to 6 touches over about three weeks across email and LinkedIn, each adding something new. Other people at the account wait for a later, separate retry. Any reply stops the cadence.
- license
- CC-BY-4.0
Run a single-thread cadence
This skill plans and drafts an outreach cadence for one person per account. The chosen decision maker gets every touch, by email and LinkedIn, over about three weeks; nobody else at the account hears from you until a later, separate retry. Spreading the first touches across several people dilutes the sequence and blurs who owns the conversation.
Inputs
- The account and why now: one dated signal with its source.
- The person and the alternates: the pick from the find-the-decision-maker skill, with its reason, the ordered alternates, a work email (verified or not) and a LinkedIn profile. No pick yet: run that skill first.
- What you sell, in one sentence, and any proof you can use.
- Channels: the sending address, and whether the sender has LinkedIn Premium.
- Start date, time zone and voice guide (see the write-in-my-voice skill).
- CRM access (read). Without it, ask the user to confirm the account is not a client, not in an open deal and not in another cadence.
Steps
Check the account first. Not a client, not in a colleague's open deal, nobody already in a cadence. If anyone there opted out, flag it and ask before going on.
Use the pick, do not choose again. The person find-the-decision-maker picked owns the whole cadence; copy its reason into the plan. Its alternates become the retry list, in order. If the pick has no verified email and no LinkedIn profile, go back to that skill.
Plan the touches. Default, six touches over 19 days:
Touch Day Channel What it adds 1 1 Email The signal, its date, one question 2 3 LinkedIn connection request A short note, or none 3 8 Email, same thread A new fact: a public record, a number, a short example 4 11 LinkedIn message, only if connected Something useful with no ask 5 16 Email, same thread A different angle on the problem 6 19 Email, same thread A clear close: "Should I stop here?" For smaller deals, keep touches 1, 2, 3 and 6. Move weekend or holiday touches to the next business day.
Draft every touch. Email under 90 words, follow-ups shorter, replying in the same thread. Each touch adds something new; "just bumping this" is not a touch.
Respect the platforms' rules. LinkedIn Help says a connection note can be up to 200 characters, and that you can add notes to up to three requests a month unless you have Premium; without it, send touch 2 with no note. For US email, the FTC says CAN-SPAM makes no exception for business-to-business email: include a valid postal address and a clear opt-out, and honor opt-outs within 10 business days.
Set the stop rules. Any reply ends the cadence and goes to triage, whoever at the account sends it. So do a booked meeting, an unsubscribe and a bounce. An out-of-office stops it too; re-plan the rest from the return date, with approval.
Plan the retry, separately. No sooner than 30 days after the last touch, and only if nobody replied. The next person on the retry list, a fresh reason (a newer signal if there is one) and a message that stands on its own. No cc, no forwarded thread.
Load only after approval. After a yes on the plan and drafts, create the sequence or dated CRM tasks for this one contact.
Output
Account: Summit Ag Supply
Why now: announced a second distribution center in Fresno on 2026-11-18 [source link]
Thread owner: [Name], VP Operations · email verified 2026-11-20 · LinkedIn: not connected
Why this person (from find-the-decision-maker): runs the new site, named in the announcement
Retry list (not contacted now): 1. [Name], CFO · 2. [Name], Director of Logistics
Earliest retry: Monday 2027-01-18, one person, new reason
| # | Date | Channel | What's new |
| 1 | Mon 2026-11-30 | Email | The new site, one question |
| 2 | Wed 2026-12-02 | LinkedIn request | No note (no Premium) |
| 3 | Mon 2026-12-07 | Email, same thread | Permit filing for the site, dated |
| 4 | Thu 2026-12-10 | LinkedIn, if connected | A two-line example, no ask |
| 5 | Tue 2026-12-15 | Email, same thread | The receiving bottleneck angle |
| 6 | Fri 2026-12-18 | Email, same thread | "Should I stop here?" |
Stops on: any reply · meeting booked · unsubscribe · bounce · out of office (re-plan)
Touch 1 · Subject: the Fresno site · 68 words · [draft]
...
Approve to create the sequence for [Name] only.Guardrails
- Reads: the CRM record for the account, the signal's source, the voice guide.
- Writes: after approval only, one sequence or one set of dated tasks for the chosen person.
- Asks before: loading the sequence, adding anyone from the retry list, re-planning after an out-of-office.
- MUST run the whole cadence to one person per account.
- MUST make every touch add something new, and name it in the plan.
- MUST stop on any reply, unsubscribe or bounce.
- NEVER cc, copy or add a second person at the account during the cadence.
- NEVER start the retry within 30 days of the last touch.
- NEVER send a touch the user has not approved.
Sources
- Personalize invitations to connect, LinkedIn Help (read 2026-11-20).
- CAN-SPAM Act: A Compliance Guide for Business, Federal Trade Commission (read 2026-11-20).
- How can a founder sell without a sales team?, ALTARA Insights: one decision maker per account.
- Find the person who decides, ALTARA AI Store: the skill that picks who gets the cadence.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/store
Use it with
-
Runs in ALTARAPlaybook Run the cadenceFounder-led outbound in 30 minutes a day, with ALTARAThirty minutes a day with ALTARA: a weekly list with dated reasons, contacts and sequences you approve, replies logged in the CRM. 30 minutes a dayRun it →
-
Runs in ALTARAPlaybook Find who to talk toTurn hiring signals into booked calls with ALTARAJob posts that reveal a plan, checked on the company's own site, then one decision-maker and an approved sequence per account. 30 minutes twice a weekRun it →
-
Runs in ALTARAPlaybook Find who to talk toBuild a federal contractor pipeline with ALTARACompanies that just won federal work, the person who runs delivery and an approved sequence, all from a text to ALTARA. 20 minutes a weekRun it →
-
find-the-decision-maker/SKILL.mdSkill Enrich every leadFind the person who decidesMaps the buying committee from public sources, confirms each person is current, and picks one person to start with and says why. Public dataInstall → -
signal-first-message/SKILL.mdSkill Write in your voiceWrite a first message from a buying signalA first email under 90 words and a LinkedIn note under 200 characters, built on one dated signal, with one idea and one ask. Public dataInstall → -
reply-triage/SKILL.mdSkill Run the cadenceSort replies and draft the answersSorts outreach replies into seven categories, drafts each answer in your voice and proposes the CRM update. Unsubscribes stop at once. Install → -
Connection Run the cadenceGmail, Google Calendar and DriveALTARA sends the sequences your team approved from a separate, warmed inbox. Your own AI reads your Gmail, Calendar and Drive to prepare the calls. Sending inbox for sequencesSee how →
-
Connection Run the cadenceOutlook, Teams and SharePointYour team texts ALTARA in Microsoft Teams, and it sends approved sequences from a warmed inbox. Your own AI reads your Outlook, Teams and files. Sending inbox for sequencesSee how →
-
Connection Keep the CRM currentHubSpotALTARA reads one HubSpot pipeline, read-only, and sends each change with a link to the deal. Your own AI reads the same records through HubSpot's MCP. Reads (rolling out)See how →
-
Connection Keep the CRM currentPipedriveALTARA keeps your Pipedrive pipeline current from the chat, after your yes. Your own AI reads the same deals through Pipedrive's MCP server. Reads and writesSee how →
-
Connection Keep the CRM currentSalesforceThe ALTARA team connects Salesforce on request, read access first. Your own AI reads the same records through Salesforce's hosted MCP servers. Connected on requestSee how →