Back to Outbound Prospecting & Cold Outreach Cadences

Launch Plan

What FullSpec will build for you, what happens at each stage, and what your automation looks like once live.

4 pagesPDF · Operations
FS-DOC-01Operations

Launch Plan

Outbound Prospecting & Cold Outreach Cadences

[YourCompany.com] · Sales Department · Prepared by FullSpec · [Today's Date]

This Launch Plan is your single reference for how the Outbound Prospecting and Cold Outreach Cadences automation gets built, tested, and handed back to your team. It covers what is being built, how FullSpec structures the work across four clear stages, what you need to provide, and what your role looks like once the system is live. FullSpec handles all technical design, build, and testing. Your team's input is limited to granting tool access and reviewing one AI-generated output before each outreach sequence fires.

01What you're launching

Right now, your Sales Development Reps spend roughly 10 hours per week managing every step of the outbound cadence by hand: building prospect lists in Apollo.io, enriching contact data in Clearbit, writing personalised opening lines one by one, loading contacts into HubSpot sequences, firing follow-up emails through Gmail, and logging every touch back to the CRM. Steps get skipped when reps are busy, cadences stall, and warm prospects go cold not because they said no but because nobody followed up. This automation replaces nine of those eleven manual steps with three purpose-built agents, leaving reps with one retained review task and full visibility through Slack alerts.

Process
Outbound Prospecting & Cold Outreach Cadences
Trigger
A contact is created or updated in HubSpot with status set to 'To Contact'
Final output
A completed, fully-logged multi-touch cadence in HubSpot, with every send and engagement event recorded automatically and the rep alerted in Slack when a reply or booking arrives
Agents being built
3 agents: Prospect Enrichment Agent, Personalisation Drafting Agent, Cadence Execution and Logging Agent
Tools involved
HubSpot, Apollo.io, Clearbit, Gmail, Slack, Google Sheets
Volume
Approximately 120 prospects per month, triggered daily as new contacts are added
Launch PlanPage 1 of 4
FS-DOC-01Operations

02How the build works

The build is organised into four sequential stages: Connect, Build, Test, and Launch. FullSpec leads all technical work across every stage. Your involvement is focused and brief at each gate: confirming access, reviewing a pilot run, and approving go-live. The estimated total delivery window is five business weeks from the close of the Connect stage, broken across the four stages below.

Complexity level: Moderate. Estimated delivery window: 5 weeks (25 business days). The delivery clock starts at the close of Connect, not payment. FullSpec cannot begin the Build stage until all tool credentials and the configuration decision in Section 03 are confirmed.
1
Connect
Estimated time: Days 1 to 3
Who
Actions
FullSpec
Reviews your current prospecting workflow and existing cadence templates. Audits HubSpot seat level, Gmail sending limits, and API access availability for Apollo.io and Clearbit. Documents enrichment field requirements and personalisation patterns. Confirms the automation platform configuration needed for this stack.
You
Grant API access for HubSpot, Apollo.io, Clearbit, Gmail, and Slack (see Section 03 for the full credential list). Confirm your HubSpot subscription tier. Provide two or three examples of existing cadence email templates and a sample of past personalised opening lines so FullSpec can configure the AI prompt accurately.
2
Build
Estimated time: Days 4 to 18
Who
Actions
FullSpec
Builds all three agents in sequence. Week 2: Prospect Enrichment Agent, connecting Clearbit and Apollo.io APIs to HubSpot and testing with a sample list of 20 contacts. Week 3: Personalisation Drafting Agent, configuring the AI prompt template with your tone and offer context and wiring the rep-review task creation logic. Week 4: Cadence Execution and Logging Agent, connecting the approval trigger to HubSpot sequence enrolment, configuring Gmail sending, setting up activity logging for every touch event, and building the Slack alert for replies and bookings.
You
Remain available to answer brief questions about cadence templates or offer context during the build. No technical involvement is required. FullSpec will flag if anything is needed via email to your nominated contact.
3
Test
Estimated time: Days 19 to 22
Who
Actions
FullSpec
Runs a live pilot with 15 real prospects through the full automated flow. Verifies enrichment field accuracy, personalisation draft quality, sequence enrolment timing, Gmail send delivery, CRM activity log completeness, and Slack alert firing. Fixes any issues identified before handing over to your team for review.
You
Review the 15 pilot contact records in HubSpot and confirm that enrichment data looks accurate, that AI-drafted opening lines are on-brand and usable, and that Slack alerts arrived as expected. Provide a simple thumbs-up or written confirmation to FullSpec to proceed to Launch.
4
Launch
Estimated time: Days 23 to 25
Who
Actions
FullSpec
Opens the automation to your full prospect volume. Delivers the SOP and runbook briefing the rep team on the new review-and-approve workflow. Monitors the first 48 hours of live traffic to confirm all agents are running cleanly and error rates are within acceptable thresholds.
You
Brief your SDR team using the FullSpec-delivered SOP. Confirm that the first live batch of contacts looks correct in HubSpot. The reps' only ongoing task is reviewing and approving the AI-drafted opening line before each touch one is sent, a step that takes under five minutes per prospect.
Launch PlanPage 2 of 4
FS-DOC-01Operations

03What FullSpec needs from you

FullSpec needs only access to your existing tools. No technical knowledge is required from your side. The table below lists every credential needed and when it must be provided. All items should be ready before Connect closes so the build can begin without delay.

Tool
What we need
When
HubSpot
A Private App token with scopes covering contacts (read/write), sequences (enrol/manage), deal stages (update), tasks (create), and email activity (read). Confirm Sales Hub Professional or Enterprise seat level.
Before Connect closes
Apollo.io
An API key from your Apollo.io account settings with access to the Contacts and People endpoints. Confirm your plan tier to ensure enrichment API calls are included.
Before Connect closes
Clearbit
Your Clearbit Secret Key from the API settings page. FullSpec will use this for the Enrichment and Prospector APIs. Confirm your monthly lookup quota.
Before Connect closes
Gmail
OAuth 2.0 authorisation via the connected Gmail account used for outreach. The rep authorises access during the Connect call. FullSpec will also need to know the daily send limit on this account.
Before Connect closes
Slack
A Slack bot token with permission to post messages to the designated rep-alert channel. The channel name should be confirmed during Connect.
Before Connect closes
Google Sheets
View access to the prospect import sheet (if contacts are loaded via sheet rather than directly in HubSpot) so FullSpec can configure the alternate trigger path.
Before Connect closes
Configuration decision required before Connect closes: You must confirm your HubSpot subscription tier before build begins. HubSpot Sequences is only available on Sales Hub Professional or Enterprise. If your team is on the Starter tier, FullSpec will build the cadence execution logic inside the automation platform itself, which changes the build approach for the Cadence Execution and Logging Agent. This is the one decision that cannot be made mid-build without adding time to the delivery window.

04Your role once live

Once the automation is live, the day-to-day workload for your team shifts dramatically. The table below sets out what each party is responsible for on an ongoing basis.

Role
Ongoing responsibilities
What you no longer touch
You (business owner / SDR team)
Review and approve the AI-drafted personalisation line in HubSpot for each new prospect before touch one fires (under 5 minutes per contact). Respond to live conversations surfaced via Slack alerts. Periodically review cadence template copy and update messaging if the offer or positioning changes.
Manual contact enrichment in Clearbit and Apollo.io. Writing personalised opening lines from scratch. Loading contacts into HubSpot sequences. Setting follow-up reminders and calendar tasks. Executing touches 2 to 7 one by one. Manually logging email activity to the CRM. Marking unresponsive contacts in a spreadsheet.
FullSpec
Monitors the automation platform for errors and agent failures. Responds to any issues flagged to support@gofullspec.com. Applies fixes or adjustments if API changes at HubSpot, Apollo.io, Clearbit, Gmail, or Slack affect the integration. Provides ongoing SOP updates if the process scope changes.
Not applicable. FullSpec does not manage prospect conversations, cadence copy decisions, or CRM stage strategy. Those remain entirely within your team's control.
Launch PlanPage 3 of 4
FS-DOC-01Operations

05What success looks like

The table below sets out realistic expectations for the first three months after go-live, based on a team processing approximately 120 prospects per month through a 6 to 8 touch cadence.

Timeframe
What to expect
Sign of success
Week 1
The first batch of live prospects flows through the full automated pipeline. Reps are spending a few minutes each day reviewing and approving AI-drafted opening lines in HubSpot rather than writing them. Slack alerts are firing when engagement signals arrive. Some minor prompt tuning may be needed to match your exact voice.
Every new contact added with status 'To Contact' triggers enrichment within minutes. The rep approval task appears in HubSpot reliably. At least one Slack alert fires correctly for a reply or engagement event. No manual CRM logging is required by the rep team.
Month 1
The team has processed a full month of approximately 120 prospects through the automated cadence. Follow-up completion rates have moved sharply upward from the previous manual baseline of around 55%. CRM activity logs are being written automatically after every touch without rep intervention. Reps are reporting fewer missed follow-up notifications.
Cadence completion rate reaches or approaches 90% or higher. CRM activity log accuracy is at or near 100% for all contacts in the automated flow. Reps are spending 1 hour or less per week on prospecting admin tasks versus the previous 10 hours. No prospects have been reported as having received incorrect or duplicate touches.
Month 3
The automation is running at full steady-state volume. The team has reclaimed the majority of the 500 annual hours previously lost to manual prospecting tasks. The pipeline is receiving more consistent follow-up than at any point previously, and no cadences are stalling due to rep capacity. The ROI has moved well toward the projected 4-month payback point.
Annualised time savings are on track to hit 500 hours per year, equivalent to $24,000 in recovered staff cost at the assumed SDR rate. Cadence completion is consistently at or above 97%. The rep team has not needed to touch a spreadsheet for outreach tracking since go-live. Any issue raised with FullSpec via support@gofullspec.com has been resolved within the agreed support window.

Next step: To get started, contact the FullSpec team at support@gofullspec.com and reference this Launch Plan. FullSpec will schedule the Connect session, send the credential collection checklist, and confirm your HubSpot tier before the build clock starts. Everything in this document is fixed and agreed. The only thing needed now is your tool access and the HubSpot tier confirmation in Section 03.

Launch PlanPage 4 of 4

More documents for this process

Every document generated for Outbound Prospecting & Cold Outreach Cadences.

ROI and Business Case
Finance · Owner
View
Process Runbook / SOP
Operations · Owner
View
Developer Handover Pack
Technical · Developer
View
Integration and API Spec
Technical · Developer
View
Test and QA Plan
Quality · Developer
View