How to Design a 30-Day B2B Follow-Up Window

Who this playbook is for

This playbook is for B2B teams running controlled outreach to manufacturers, distributors, contractors, technical buyers, or business-service accounts. It is especially useful where a buying process may be slow but repeated, context-free reminders would harm credibility. The playbook begins after a company and contact are eligible for the current outreach scope. It does not choose the market, define the ICP, infer buying authority, or determine whether a message is lawful in every jurisdiction.

Contents

1 Define the window as a control boundary 2 Set the opening clock and expiry clock 3 Build an event-led action map 4 Separate waiting from permission to send 5 Route replies and human interaction 6 Apply stop states immediately 7 Decide what happens on day 30 8 Illustrative example 9 Common mistakes 10 What this does not mean 11 Common questions 12 Sources and methodology

1. Define the window as a control boundary

A follow-up window is a maximum period in which a company remains eligible for governed follow-up under a defined campaign, contact scope, and purpose. It should answer four operational questions: 1 When did the window open? 2 What evidence can justify another action? 3 What events pause, reroute, or terminate automation? 4 What decision is due when the window expires? SellersGPT uses 30 calendar days as its default configuration. An authorized administrator or account setting can instead select 30, 60, 90, 180, or 365 days. These are product choices, not claims that one duration is optimal for every industrial sale. A custom machine, a consumable component, and a compliance service can have very different buyer timing. The selected duration should reflect the decision being pursued, the offer's consideration cycle, available evidence, and the team's ability to respond. Do not confuse a window with a sequence. A sequence is a proposed set of actions. A window limits when eligible actions may occur. It can contain fewer actions than planned, because a reply, a stop request, invalid contact data, or insufficient relevance can alter the path.

2. Set the opening clock and expiry clock

Choose one reproducible opening event. Examples include the first delivered outreach in a round, an inbound form submission accepted for follow-up, or a human-approved reactivation event. Do not let different team members silently use list upload, research completion, first draft, and first send as competing start dates. Record at least: Field Required decision Window ID Stable identifier for the company and current round Opening event Exact event that starts the clock Opened at Timestamp and timezone Selected duration 30, 60, 90, 180, or 365 calendar days Expiry at Calculated timestamp Field Required decision Eligible purpose The business reason and offer in scope Contact pool Eligible contacts for this round Owner Person accountable for exceptions and expiry Stop-state source Shared record used before every action If opened_at is August 3 at 10:00 a.m. in the configured timezone and the selected duration is 30 calendar days, the team must use one documented date arithmetic rule and display the resulting expiry_at. Do not alternate between "day 30," "30 x 24 hours," and "the end of the thirtieth business day." The configured system result is the source of truth. A human reply does not necessarily restart the outbound clock. It usually changes the route. If the person asks for information or a later date, record the request and create a human-owned next action. Do not manufacture another full automated window unless the policy explicitly permits it and the purpose remains appropriate.

3. Build an event-led action map

Replace a rigid day-by-day send plan with event conditions. The following SellersGPT editorial tool is a planning aid, not a universal cadence: Evidence state Permitted planning decision Required check Delivered, no human interaction Consider a differentiated follow-up after the configured interval Relevance, deliverability, frequency, stop state Click or page visit only Observe or use context carefully; do not assume intent Signal validity, identity confidence, privacy boundary Direct reply Route by reply meaning Human review, request, sentiment, next owner Form submission Validate completeness, ICP fit, and requested response Qualification criteria, consent/purpose, response owner Wrong contact Stop this contact and evaluate replacement Exact evidence and replacement eligibility Hard bounce Stop the address immediately Bounce classification and shared suppression Unsubscribe Apply the requested channel/scope stop Exact request, jurisdiction, policy Active lead End or materially restrict prospecting automation Tenant or human owner and agreed next action A click is not a reply. A reply is not automatically a qualified lead. A qualified lead is not automatically an active lead. Keep each event and decision distinct so that timing rules do not inflate pipeline meaning.

4. Separate waiting from permission to send

Elapsed time is not evidence that another message is useful. Before each proposed follow-up, ask:

• Is the company and contact still eligible?

• Is the message materially different and relevant to the same decision scope?

• Has any channel, person, company, or campaign stop state appeared?

• Is the last delivery status known?

• Has a human interaction created a different owner or requested timing?

• Would this action duplicate another team member's contact?

• Is frequency consistent with applicable rules, provider requirements, and company policy? The FTC's CAN-SPAM compliance guide describes requirements for commercial email in the United States, including accurate header information, non-deceptive subjects, identification and opt-out handling. The CRTC's CASL FAQ explains Canadian anti-spam requirements and important distinctions around consent and commercial electronic messages. The UK Information Commissioner's Office direct-marketing guidance provides a separate jurisdiction-specific framework for direct-marketing and privacy obligations. None of these sources provides a universal B2B follow-up cadence. SellersGPT's window and action gates are operating controls that must sit inside the applicable requirements, not replace them. Mailbox providers also publish sender expectations. Google's email sender guidelines and Yahoo's sender best practices emphasize authentication, low complaint levels, and usable unsubscribe mechanisms for relevant sender categories. Deliverability rules can change, so the production team should review current provider documentation rather than freeze an old checklist into campaign logic.

5. Route replies and human interaction

Every reply needs a meaning, an owner, and a next allowed state. Use categories such as:

• positive request or question;

• timing request;

• referral to another person;

• wrong contact or role mismatch;

• not interested for the current scope;

• unsubscribe or broader stop request;

• out-of-office or automated response;

• ambiguous and requires human review. Do not let sentiment analysis alone decide. A polite "not my area" is operationally different from "remove our company from all outreach." Preserve the original text, source, channel, timestamp, and human interpretation. If the reply creates a genuine tenant or human action, the lead may become an active lead under the rules described in PP-25. That transition should stop ordinary prospecting automation from competing with the human conversation.

6. Apply stop states immediately

The window must check shared stop controls before every action. Minimum categories include hard bounce, unsubscribe, wrong contact, contact no longer at the company, retired contact, company stop, existing customer, suppression, active lead, and campaign or account pause. An unsubscribe mechanism must be operational, not decorative. RFC 8058 defines one-click unsubscribe signaling used in email ecosystems; provider requirements determine where it applies. Technical support for one-click unsubscribe does not narrow a person's plain-language request. Preserve the exact request and apply at least its clear scope. Contact-left and retired states require particular care in SellersGPT: those people must not re-enter a new outreach round. Their status may support finding an appropriate current contact, but it does not erase the prior record or make the old address eligible again.

7. Decide what happens on day 30

Expiry is a decision gate, not an automatic resend. Evaluate: Gate Question Possible output Human interaction Did a real person create an active conversation or action? Active lead or human-owned follow-up Stop state Did any contact/company/channel control end eligibility? Close or suppress at the correct scope Fit Does the company still meet the current ICP and application? Retain or close Contact evidence Is the pool valid, exhausted, or materially mismatched? Reuse, replace eligible contacts, or stop Round policy Is another round allowed and useful? Open next round or close Learning What changed about account, role, timing, or message? Record before any next round Under the SellersGPT product rule, a company can enter a next round only when it has no active lead and no human interaction that should govern the path. The default is three rounds, although authorized configuration may allow from 1 to 100. Another round is not mandatory merely because the maximum permits it.

8. Illustrative example

Illustrative example - fictional. Northline Components is testing a preventive-maintenance offer with a fictional company, Alder Works. Its configured window is 30 calendar days and the opening event is the first confirmed delivery on September 2. The team proposes four decision checkpoints, not four guaranteed sends. At checkpoint one, delivery is confirmed and no stop state exists. At checkpoint two, the original contact's role is found to be unrelated; the address remains valid, but the person replies with a referral to a maintenance planner. Northline records the reply, stops messaging the first contact for this purpose, verifies the referral, and assigns a human owner. At checkpoint three, the planner requests a specification sheet. That requested action makes the record human-owned and eligible for active-lead review. Automated follow-up ends. The day-30 expiry job records the outcome but sends nothing. For operational QA, the team measures decision completeness: completed required controls / applicable required controls = 9 / 10 = 90% The missing control is a documented timezone for expiry. The 90% does not justify execution because timing is required. The owner adds the timezone and recalculates the expiry. This percentage measures configuration completeness only. It is not a reply probability, lead score, or sales forecast.

9. Common mistakes

• Treating 30 days as a recommendation to send frequently.

• Restarting the clock after every open, click, or automated reply.

• Using business days in one workflow and calendar days in another.

• Allowing a click to override a stop request or missing fit evidence.

• Keeping prospecting automation active after a human-owned action begins.

• Starting another round without recording what the prior round taught.

• Interpreting the 1-100 allowed range as encouragement to run many rounds.

• Forgetting that a longer window can increase monitoring obligations without increasing permission.

10. What this does not mean

A 30-day window is not a legal safe harbor, deliverability guarantee, industry benchmark, or prediction of buyer timing. It does not require equal spacing or a fixed number of touches. It does not make a company eligible if the ICP, contact purpose, data quality, or applicable communication basis is missing. It also does not replace a person's explicit timing request. When a buyer says to return in a particular month, the team should record and honor that instruction rather than keep sending inside the original window.

11. Common questions

Why is the SellersGPT default 30 days? It provides a finite operating boundary that is short enough to force an expiry decision and long enough to observe several common response paths. It is a product default, not evidence that 30 days performs best across industries. Should a click extend the window? Not automatically. A click may be noisy, misattributed, or insufficient to show intent. Keep the event, confidence, and context separate; extend or reroute only under a declared policy. Can an administrator choose 60, 90, 180, or 365 days? Yes. SellersGPT supports those configured durations in addition to 30 days. The team should document why the longer monitoring period fits the purchase situation and how stop checks remain current. What if a contact asks for follow-up after the window expires? The contact's explicit request should become a human-owned scheduled action with its own scope and evidence. Do not silently stretch the old automated window.

12. Sources and methodology

Official sources below establish communication and sender constraints, not a universal follow-up duration. The 30-day default, selectable durations, window register, event map, expiry gate, and completeness calculation are SellersGPT product rules or editorial tools as labeled. 1 U.S. Federal Trade Commission, CAN-SPAM Act: A Compliance Guide for Business. https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business. Accessed August 25, 2026. 2 Canadian Radio-television and Telecommunications Commission, Frequently Asked Questions about Canada's Anti-Spam Legislation. https://crtc.gc.ca/eng/com500/faq500.htm. Accessed August 25, 2026. 3 UK Information Commissioner's Office, Direct marketing guidance. https://ico.org.uk/for-organisation s/direct-marketing-and-privacy-and-electronic-communications/direct-marketing-guidance/. Accessed August 25, 2026. 4 Google, Email sender guidelines. https://support.google.com/a/answer/81126. Accessed August 25, 2026. 5 Yahoo, Sender Best Practices. https://senders.yahooinc.com/best-practices/. Accessed August 25, 2026. 6 Internet Engineering Task Force, RFC 8058: Signaling One-Click Functionality for List Email Headers. https://www.rfc-editor.org/rfc/rfc8058. Accessed August 25, 2026.