Sequence Cadence Builder
divide the template by your own capacity
Most published cadences describe what happens to one prospect. Your infrastructure has to carry every prospect at once, and the person who entered on Monday is still consuming a send slot the week after. This does that division for you, then lays the calendar.
new prospects a day is what this sequence can absorb. With 2,000 prospects, 10 mailboxes and 1 LinkedIn seat over 60 days, email opens and LinkedIn escalates. The whole list takes 44 working days to run through and your window is 44. It fits, with nothing spare. Read the warnings before you launch it.
Motion: WideNET. High volume motion. Email opens across the full addressable market and LinkedIn escalates on signal, because email is the only channel here with the capacity to touch everyone inside the window.
The three numbers
| What | Number | Status | What it means |
|---|---|---|---|
| Coverage window | Email 8. LinkedIn 134 | Entry channel can open | Working days to make first contact with everyone, per channel. A channel may only open the sequence if it can cover the whole list inside the first 22 working days, which is half your window. |
| Intake ceiling | 83 a day | In use | Daily send capacity of 250 divided by the 3 email touches in this sequence. Everyone who entered on Monday is still consuming a send slot next week. |
| Campaign length | 44 against a window of 44 | Tight | 25 working days to get everybody in, plus 19 working days for the last cohort to finish the sequence. |
Four levers, with the numbers
The plan fits, but it is running against at least one of its own limits. These are the same four levers, sized for the state you are in.
| Lever | What it takes | What it costs you | |
|---|---|---|---|
| Extend the window | Already met. The campaign uses 44 of your 44 working days, leaving 0 spare. | Nothing structural. It is usually the right answer and the one people resist. It is also the only lever that buys margin for the week something goes wrong, and there is always a week. | |
| Raise sending capacity | Already met. 10 mailboxes at 25 sends a day is what this plan needs. | Infrastructure, warm up time, and a deliverability problem if rushed. Reckon on weeks rather than days before new mailboxes carry real volume. | |
| Cut the list | Already met. This window holds 2,075 and you are running 2,000. | Least popular, most often correct. Segment the list and run the rest in the next window, rather than sending harder into a market smaller than the plan assumed. | |
| Shorten the sequence | 3 angles gives an intake ceiling of 125 a day and room for 2,000 prospects | You lose an angle. Only do this if the angle you drop was weak, which is a question this tool cannot answer for you. |
The plan, per prospect
| Touch | Working day | Date, cohort 1 | Channel | Action | Who gets it | Personalization |
|---|---|---|---|---|---|---|
| 1 | D+0 | Mon 17 Aug | Opener, the offer stated plainly | Everyone | Segment level, not individual | |
| 2 | D+2 | Wed 19 Aug | Same thread bump | No reply yet | None, it is the same angle | |
| 3 | D+6 | Tue 25 Aug | Profile view, then connection request | Signal slice only, about 4 of each cohort | High. This is the escalation | |
| 4 | D+12 | Wed 2 Sept | First direct message | Accepted only, about 4 of each cohort | High | |
| 5 | D+19 | Fri 11 Sept | New thread, new angle | No reply yet | Medium |
D+n counts working days from the day that prospect enters. Every prospect gets this shape. The dates shown are for the first cohort only, which is the point most published sequence templates stop at.
The daily load calendar
What your infrastructure actually has to carry on each date once cohorts overlap. The plan above is one prospect. This is one prospect multiplied by however many entered on however many different days, all in flight at once.
| Date | Day | Entering | Emails | Requests | DMs | Views | Total | Email capacity used |
|---|---|---|---|---|---|---|---|---|
| Mon 17 Aug | 1 | 83 | 83 | 0 | 0 | 0 | 83 | 33% |
| Tue 18 Aug | 2 | 83 | 83 | 0 | 0 | 0 | 83 | 33% |
| Wed 19 Aug | 3 | 83 | 166 | 0 | 0 | 0 | 166 | 66% |
| Thu 20 Aug | 4 | 83 | 166 | 0 | 0 | 0 | 166 | 66% |
| Fri 21 Aug | 5 | 83 | 166 | 0 | 0 | 0 | 166 | 66% |
| Mon 24 Aug | 6 | 83 | 166 | 0 | 0 | 0 | 166 | 66% |
| Tue 25 Aug | 7 | 83 | 166 | 4 | 0 | 4 | 174 | 66% |
| Wed 26 Aug | 8 | 83 | 166 | 4 | 0 | 4 | 174 | 66% |
| Thu 27 Aug | 9 | 83 | 166 | 4 | 0 | 4 | 174 | 66% |
| Fri 28 Aug | 10 | 83 | 166 | 4 | 0 | 4 | 174 | 66% |
| Mon 31 Aug | 11 | 83 | 166 | 4 | 0 | 4 | 174 | 66% |
| Tue 1 Sept | 12 | 83 | 166 | 4 | 0 | 4 | 174 | 66% |
| Wed 2 Sept | 13 | 83 | 166 | 4 | 4 | 4 | 178 | 66% |
| Thu 3 Sept | 14 | 83 | 166 | 4 | 4 | 4 | 178 | 66% |
| Fri 4 Sept | 15 | 83 | 166 | 4 | 4 | 4 | 178 | 66% |
Day 20, Fri 11 Sept, is your peak at 261 actions. This is where the first cohort's late touches land on the same day as the newest cohort's touch one. If your cadence is going to break, it breaks here, and it breaks quietly, because no sending tool raises an alert for a cadence running four days behind its own design.
The escalation slice
At 5% signalling, you expect 100 people on this list to do something worth a LinkedIn touch. Your 1 seat have 38 working days of request capacity available from the escalation point onward, which covers 100 of them, or 100%.
Your seats can serve everyone you expect to signal. Spend the surplus on quality instead of reach.
This is the entire argument for sequencing rather than stacking. You spend the cheap, abundant channel finding out who is warm, and the expensive, scarce one on them.
Stop conditions for this sequence
Any reply on any channel stops every remaining touch on every channel. Not the next one. Every one.
Suppression is keyed to a canonical prospect record, not to an email address and not to a LinkedIn profile URL. Your email tool keys on the address, your LinkedIn tool keys on the profile, and the same human enters both as two people. Resolve the identifier before enrolment, not after.
Out of office is not a reply. Suppress to the stated return date, then resume from the touch that would have fired.
A referral is a stop plus an enrolment. Stop the original prospect, enrol the named colleague with the referral as context, and never drop them into the generic opener. This is one of the highest converting paths in outbound and most sequences treat it as an unsubscribe.
Not now, ask me in Q1 is a stop plus a diary entry. If your system cannot hold that state, you are losing the prospects who told you exactly when to come back.
Suppress at account level during a live conversation. Running a cold sequence into three colleagues while one of them is talking to you makes the company look like a target rather than a customer.
The architectures that make this work, with their real latencies, are set out in the write up on stopping every channel at once.
What to look at before you launch this
- High. Your LinkedIn seats would take 134 working days to send a request to everyone on this list, against a window of 44. LinkedIn is an escalation channel here, not an opener.
- Medium. The tightest gap in this plan sits on the 2 working day floor, which is our lower bound and not a comfortable spacing. 5 messages from a stranger with a two day gap inside them is a pattern the recipient can see.
- Medium. A daily manual sweep fails exactly when it matters, which is the day the person doing it is on a plane. Match your sweep frequency to your send frequency.
What produced this plan
| Value | Setting | What kind of number it is |
|---|---|---|
| Prospects | 2,000 | Your input |
| Window | 60 calendar days, 44 working days | Your input |
| Weekends | Skipped | Your input |
| Segment | Mid market | Your input, drives our spacing shape |
| Mailboxes | 10 | Your input |
| Sends per mailbox per day | 25 | Your assumption. Ships as a cautious placeholder, not a measured figure |
| LinkedIn seats | 1 | Your input |
| Requests per seat per day | 15 | Conservative assumption. This site does not research LinkedIn ceilings |
| Messages per seat per day | 25 | Conservative assumption, same reason |
| Angles | 4, giving 5 touches | Your input, plus our rule that a sequence runs to angles plus one |
| Signal rate | 5% | Your assumption |
| Attrition per touch | 0% | Your assumption |
| Acceptance rate on the DM touch | Held at 100% | Our choice. It overstates the message load, which is the safe direction, and it means this tool never invents an acceptance figure |
| Reply state | Manual. A human sweeps both inboxes | Your input |
| Minimum gap | 2 working days | Our design rule. Two touches inside a day on the same channel reads as a system, not a person |
| Maximum gap | 14 working days | Our design rule. Past roughly three weeks the touch is a fresh first contact |
| Who may open | Coverage inside 50% of the window | Our design rule. Otherwise the later touches have nowhere to go |
| Maximum touches | 7 | Our design rule. Not a performance finding, it is the point past which nobody holds a genuinely new angle |
Take this with you
The address bar holds your inputs, so that link reproduces exactly this plan for anyone you send it to. It carries integers and enums only. No list name, no company, no address, nothing about you, because there is no server here to store any of it. Printing gives you a PDF without handing over an email address.
Methodology and limitations
Which numbers here are which. Three kinds, and the table above labels every one. Your inputs are yours. Your assumptions are the sends per mailbox figure, the signal rate and the attrition rate, all of which are guesses until you replace them with your own measurements. Our design rules are the spacing shape, the gap limits, the half window rule for which channel may open, the one pairing limit and the thread break after touch two. They come from running email and LinkedIn as one coordinated sequence across a live client fleet since 2024, and they are operating preferences with reasons attached rather than measured optima, because we do not have measured optima and neither does anybody publishing a best day gap number.
The LinkedIn ceilings are not ours to set. They ship here as deliberately low planning defaults so a first pass understates LinkedIn reach rather than flattering it. The property that researches account safety and daily limits publishes the working behind them, and the honest move is to take the number from the account level calculator over there and put it in the field, because a per seat ceiling depends on the specific account rather than on an average.
What this tool does not model. Reply rates, acceptance rates, meeting conversion, revenue. It is a capacity and timing planner. It cannot tell you whether your offer is any good, and cadence is the third most important thing about a campaign after targeting and offer. If three genuinely different angles have produced close to nothing across a few thousand sends, no arrangement of days fixes that. This tool will happily draw you a beautiful calendar for a message the market does not want.
Where the arithmetic is wrong. Working days skip Saturdays and Sundays and nothing else, so a plan crossing a public holiday week is optimistic by however many days that market takes off. Volumes are rounded to whole people per day, so a long calendar accumulates small rounding differences against the exact division. Attrition defaults to zero, which overstates load. The acceptance rate on the direct message touch is held at 100%, which also overstates load. Both errors point the same way on purpose: this plan should be harder than reality, not easier.
What it cannot see. Your list quality, your domain reputation, whether your mailboxes are genuinely warmed, and whether the person operating the LinkedIn seat has time to do it well. It computes on what you typed. If the plan disagrees with what your sending tool is telling you, believe the sending tool.
Version. Calculation logic v1.0. The share URL carries a version marker, so links shared today keep working after any future change to the input set.
Quick answer
This builds a multichannel outreach cadence: the schedule that decides which channel touches a prospect on which day, and how many days sit between those touches. Put in how many prospects you have, how much sending capacity you genuinely have on each channel, and how long you want the campaign to run. It returns a day by day interleaved email and LinkedIn plan, a calendar of what your infrastructure has to carry on each date once cohorts start overlapping, and a straight answer about whether the whole thing fits in your window. It is free, it runs entirely in your browser, and there is no signup on the result.
Nothing you type is sent anywhere. There is no account, no server call, and no record of your list size on any machine we control. The share URL is the only place your inputs exist, and it exists only if you copy it.
How to use it
Start with the two numbers you already know: your prospect count and your window. Everything else ships with a default you can leave alone on the first pass, which exists so you see a working plan instead of an empty form rather than because the default is right for you.
Then correct the capacity fields, because the defaults are not yours. Mailbox count is how many are warmed and sending today, not how many you have bought. Sends per mailbox per day is your steady state figure after warm up. LinkedIn seats is how many accounts a real person can actually operate. Those three fields decide most of the output, and a plan built on somebody else's capacity is a plan for somebody else.
Set the angle count honestly. The tool asks how many genuinely different reasons you have to contact this person. It does not ask how many emails you would like to send. Write each touch's reason in one sentence, and if two of those sentences say the same thing, that is one angle rather than two. Four is a normal answer. Seven is almost always a fantasy.
Answer the reply sync question truthfully. If your email tool and your LinkedIn tool cannot see each other's replies, say so. The plan changes, the tail gets trimmed, and the warning moves above the calendar instead of below it. That is deliberate. Handing a beautiful two channel calendar to a team whose tools are blind to each other is helping them build the exact failure that costs meetings.
Read the verdict line before you read anything else. It says in one sentence which channel opens, how many new prospects a day the sequence can absorb, and whether the campaign fits your window. Most of the value is in that sentence. Then look at the daily load calendar rather than the touch plan. The touch plan is the pretty one. The load calendar is the one that tells you something you did not already know.
If the verdict is anything other than a clean fit, the tool shows four levers with the numbers attached: how many more mailboxes it would take, how many fewer prospects would fit, how much longer the window needs to be, and what dropping a touch does. Pull the one that is cheapest in your situation. They are quantified so the trade is a decision rather than an argument.
What the numbers mean
Coverage window
A coverage window is how many working days it takes to make first contact with every prospect on your list using one channel. It is your prospect count divided by that channel's daily ceiling. Email capacity scales with the number of mailboxes you run. LinkedIn capacity is capped per seat per day and does not move when you buy more software, which is why the two coverage windows for the same list are usually orders of magnitude apart.
The rule the tool applies to that number: a channel may only open the sequence if it can make first contact with the whole list inside the first half of your window. If it takes longer, the later touches have nowhere to go, and the channel becomes an escalation rather than an opener. That single division settles most of the argument about whether to send the email or the connection request first, and almost nobody publishes it because the answer is different for every list.
The LinkedIn ceilings themselves are not ours. Our sibling property researches LinkedIn limits and account safety as its main subject and maintains a safe sending ceiling calculator for exactly this figure. This tool ships deliberately low placeholders, labels them in the interface as conservative assumptions rather than as researched limits, and expects you to replace them with the number that comes out of there. The reasoning behind the ordering itself is written out longhand in the email first against LinkedIn first comparison.
Intake ceiling
An intake ceiling is the number of new prospects a day your sequence can absorb without the follow ups exceeding your send capacity. The formula is short: daily send capacity divided by the number of email touches in the sequence.
Worked at the tool's placeholder of 25 sends per mailbox per day, which is a cautious default and not a figure we have measured for you: ten mailboxes at that rate is 250 sends a day, so a sequence with three email touches has an intake ceiling of 83 prospects a day rather than 250. Put your own send rate in and every number here moves together, which is why the conclusion survives the substitution. What does not move is the reason: every prospect who entered on Monday is still consuming a send slot on Wednesday, next Tuesday and the Monday after that.
This is the number teams get wrong, and they get it wrong in a specific and predictable way. They set daily intake to their sending capacity, because that is the number the sending tool shows them. It works for about a week. Then the pipeline fills, the follow ups start stacking on top of the new entrants, and the tool begins silently delaying touches, or the sender starts pushing past its own throttle. Nobody notices, because there is no alert for a cadence that is now four days behind its own design.
The daily load calendar
The load calendar is the total number of actions your infrastructure has to place on each date, summed across every cohort currently in flight. A cadence is not one prospect's schedule. It is one prospect's schedule multiplied by however many prospects entered on however many different days, all overlapping.
The peak day is where the first cohort's last touch lands on the same date as the newest cohort's first touch. That is the day a cadence breaks, and it breaks quietly. The load calendar puts a date on it before you launch, which is the whole reason it is in the tool.
The escalation slice
The escalation slice is the share of your list that shows enough of a signal to be worth spending a scarce LinkedIn touch on. The tool asks you for the percentage because we do not have a measured figure to give you, and neither does anyone who publishes one. What it does instead is check whether your seats can actually serve the slice you expect, and tell you the shortfall in plain numbers.
On a list where a small share show any engagement signal, one seat can comfortably serve a list many times larger than its raw ceiling implies, because it never touches the majority. That is the entire argument for sequencing rather than stacking: you spend the cheap, abundant channel finding out who is warm, and you spend the expensive, scarce channel on them.
The three kinds of number in this tool
Every value in the interface is labelled as one of exactly three things, and the assumptions table at the bottom of a result repeats the label next to each one. Your inputs are yours. Your assumptions are the sends per mailbox figure, the signal rate and the attrition rate, all of which ship with placeholders. Our design rules are the spacing shape, the gap limits, the half window rule for which channel may open, the one same day pairing limit and the thread break after touch two, and each carries its reason in the interface. Nothing here is dressed up as a category it is not.
Methodology: where the rules came from
The spacing shape, the minimum and maximum gaps, the half window rule for which channel can open, the single same day pairing limit and the thread break after touch two are ours. They come from running email and LinkedIn as one coordinated sequence across a live client fleet since 2024. They are operating preferences with reasons attached, and the interface gives you the reason on every one of them. They are not measured optima, because we do not have measured optima and neither does anybody publishing a best day gap figure.
The spacing shape tightens early and widens late. The first follow up is catching the group who meant to reply and did not, and that group decays quickly, so a short gap works. Later touches are testing a different angle at a different moment in the quarter, so longer gaps perform better. The buying cycle you select adjusts how aggressively the gaps widen, which is a preference about how long a decision takes in your market rather than a measurement of it.
Working days means Saturdays and Sundays are skipped by default. Public holidays are not skipped, which means a plan crossing a holiday week is optimistic by however many days that market takes off. That is a known gap rather than an oversight, and it is the one most likely to move your real dates.
The connection acceptance rate on the direct message touch is held at 100%, which overstates the LinkedIn load on purpose. Overstating load is the safe direction for a capacity plan, and it means this tool never invents an acceptance figure that belongs to a property that actually researches them.
On the one measured claim behind this site: in the Outbound Pros fleet snapshot dated 2026-07-06, sequences tagged as a multichannel motion produced a 0.37% positive reply rate across 8,714 emails sent, 7.36x the fleet baseline for that snapshot, against 0.14% on 52,786 sends for the follower sourced motion in the same window. That is an observation from one fleet over one period rather than a controlled test, the segment is derived from sequence names rather than from channel logs, and the denominator structurally flatters multichannel because positive replies arriving on LinkedIn are still counted against emails sent. It is published with its full working, including the single sequence that beat that segment average, in our benchmark writing. It is not an input to this tool and this tool does not use it to predict anything.
Version. Calculation logic v1.0, last changed 2026-08-06. Links shared from v1 will keep working after any future change to the input set.
Limitations, stated plainly
This is a capacity and timing planner. Here is the complete list of what that means it cannot do for you.
- It does not predict reply rates, acceptance rates, meeting conversion or revenue, and it never will. Those depend on your offer and your market, and any tool that forecasts them is guessing with confidence.
- It cannot tell you whether your offer is any good. Cadence is the third most important thing about a campaign, behind targeting and offer. If three genuinely different angles have already produced close to nothing across a few thousand sends, this tool will cheerfully build a beautiful calendar for a message the market does not want.
- It does not model public holidays, so a plan crossing a holiday week runs later than it says.
- It defaults attrition through the sequence to zero, which overstates your daily load. That is the safe direction for a capacity plan, and you can set your own figure and the tool will label it as yours.
- It assumes your stated capacity is real. A mailbox that is bought but not warmed, or a LinkedIn seat nobody has time to operate, will produce a plan that works on paper and stalls in week two.
- It does not know your deliverability. Sends per mailbox per day is an input here, and it is an outcome of your domain history, warm up discipline and list hygiene, none of which this tool can see.
- It does not wire anything. The plan describes a schedule. Somebody still has to build the stop condition that makes a reply on either channel halt the touches on the other.
One more that is worth its own paragraph. The defaults are worth very little on their own. They exist so a first time visitor sees a working plan rather than an empty form. Every one of them is a placeholder, most obviously sends per mailbox per day, which varies enormously by infrastructure and warm up state. Replace them before you plan against the output.
The tool assumes you have already decided which tools carry each channel, which is its own question. Our head to head write ups on the LinkedIn execution layer and on the email engine underneath it cover the parts that decide whether your stop condition is an event or a habit.
If you would rather not run it yourself
The plan this produces is the plan we build for clients, minus the part where somebody has to provision the mailboxes, warm them, write the angles, place the touches, watch both inboxes and suppress across channels when a reply lands. That part is done for you by the group's agency, and the deliverability and infrastructure work underneath any cadence at volume lives over there too, because it is the parent's deepest specialty rather than ours. MultichannelPros is part of the Outbound Pros group, which is disclosed on every page here.
If your question is broader than the calendar, the parent runs a structured diagnostic across targeting, offer, channel and sequence.
We do not publish prices anywhere in this group. Scope varies enough between a small single geography test and a multi workspace programme that a figure without context would mislead, so it gets discussed on a call once the list size, the channels and the window are known. Book one through the scoping call link. If you would rather write the first draft of the messages yourself, the parent also keeps a free cold email generator. Embedding this tool on your own site is free, including commercial use.
Frequently asked questions
What does a fourteen day email plus LinkedIn sequence look like day by day?
On most real lists it does not exist, and that is the useful answer. A fourteen day window holds roughly ten working days, which is enough for four touches at minimum spacing and nothing else, and it only works if your entire list can receive touch one inside the first five days. For a 2,000 prospect list on ten mailboxes at the tool's placeholder 25 sends a day, that means an intake of 200 a day against an intake ceiling of 83, so the plan silently falls behind itself by the second week. Put your own send rate in and both numbers move together, which is why the conclusion survives the substitution. Set the window to your real constraint and let the tool tell you what fits. The fourteen day template is a content format, not a campaign.
How many prospects should be live in a sequence at one time?
Your daily send capacity divided by the number of email touches, multiplied by the length of the sequence in working days. At the tool's placeholder rate of 25 sends per mailbox per day, ten mailboxes with three email touches and a nineteen working day sequence gives you 83 entering a day and roughly 1,600 people in flight at steady state. Substitute your real send rate before you plan against those figures. Going above the ceiling does not send more, it delays touches, and delayed touches arrive with the wrong spacing on a schedule you designed carefully.
Do I need to sign up or give an email address to get the result?
No. The plan renders in full, every export works and the share link works, all without an address. Nothing you type reaches a server. If you want a PDF, use your browser's print to PDF and the page is styled for it.
Which sending tool does the export work with?
All of them and none of them. The exports describe a schedule rather than a platform specific import file, and we deliberately did not build one click import for any vendor. We run Salesforge on client accounts and we are an official Salesforge Expert Partner, which is exactly why the free tool stays neutral: a cadence planner that only exports cleanly to the tool its author sells is a cadence planner designed around that tool's constraints.
Where do the default numbers come from?
Three places, and the interface labels which is which. Your inputs are yours. Your assumptions are the sends per mailbox figure, the signal rate and the attrition rate, all placeholders. The design rules, meaning the spacing shape, the gap limits and the half window rule for which channel opens, are ours, and each carries its reason next to the field. The LinkedIn daily ceilings are imported from our sibling property, which researches limits and account safety as its main subject. No number in this tool is presented as a measured performance benchmark, because it is a capacity planner and it does not have one.