The 90-Day Blueprint to Build Your Contact-Based Marketing Engine

The Problem No One Wants to Say Out Loud

You've got pipeline reviews where the answer to "what happened?" is always some version of timing.

"They went dark." "The budget got frozen." "They're evaluating next quarter."

Meanwhile, your CRM is full of accounts that were "hot" six months ago. Your reps are working off personal spreadsheets. Marketing is running campaigns to a list no one trusts. And every board meeting ends with the same question:

Why didn't we see this pipeline sooner?

Here's what's actually happening: You're running outbound like it's 2019. Spray and pray with a better subject line. Maybe some intent data that goes into a report no one reads.

The companies pulling ahead - the ones hitting 140% of quota while you're explaining away a miss - aren't working harder. They built a system.

This is that system.

What You're Actually Building: A Contact-Based Marketing Engine

Contact-Based Marketing isn't a campaign. It's infrastructure.

Think of it this way:

ABM says: "Let's target these 50 accounts with a coordinated campaign."

CBM says: "Let's build a system that identifies which accounts are ready to buy, alerts the right rep at the right moment, and activates personalized outreach automatically."

ABM is episodic. CBM is continuous. If you're still treating account-based motions as campaign bursts, you're leaving pipeline on the table. The distinction between account-based go-to-market strategy and CBM is subtle but critical - ABM is a targeting philosophy, CBM is an operational system.

By Day 90 of this blueprint, you'll have:

• A living TAM that updates itself with signals and intent

• Awareness scoring that tells you exactly where each account sits in their buying journey

• Slack intelligence routing alerts to the right owner the moment something changes

• Automated triggers that launch the right sequence when an account turns warm

No more guessing. No more "we should have reached out sooner." A machine that converts intent into pipeline.

How the 90 Days Break Down

Each month builds on the last. Skip a step and the system breaks downstream.

Month 1: Data Intelligence (Days 1–30)

The Foundation That Makes Everything Else Work

Month 1 is unglamorous. It's the work your competitors skip because it doesn't feel like "doing outbound."

But here's what happens when you skip it: You build campaigns on bad data. You target the wrong accounts. You waste cycles on companies that were never going to buy.

Month 1 is where you decide who actually matters and why.

When we work with Series A and B startups on fixing a stalled B2B sales pipeline, roughly 60-70% of the time, the root cause traces back to weak ICP definition or incomplete TAM data. The pipeline wasn't stalled - it was built on sand.

Week 1-2: ICP Modeling & Strategic Positioning

The goal: Define exactly who you're targeting with enough specificity that a new rep could identify a qualified account in under 60 seconds.

What to document:

Firmographic Criteria

• Industries (be specific - "SaaS" is too broad; "vertical SaaS serving healthcare providers" is useful)

• Company size ranges (headcount, revenue proxies)

• Geographies

• Business model (B2B, B2B2C, marketplace, etc.)

• Maturity indicators (funding stage, team composition, tech complexity)

Pain Point Mapping

For each ICP segment, document:

• Operational bottlenecks they're experiencing

• Revenue gaps they're trying to close

• Team constraints limiting growth

• Compliance or regulatory pressure

• Strategic initiatives on their roadmap

This becomes your messaging foundation. Every email, every LinkedIn touch, every retargeting ad pulls from this.

From a founder's perspective: The ICP exercise isn't just for sales. It should inform product roadmap prioritization, partnership decisions, and even hiring. When a fintech startup we worked with tightened their ICP from "financial services companies" to "Series B+ embedded finance platforms with $5M-50M in transaction volume," their sales cycle compressed by approximately 35-45%.

Positioning Narrative

Build a clear story that answers:

• What problem are they stuck with?

• Why does it matter now?

• What outcome do we deliver?

• Why is our approach different from alternatives?

Validate this with your AEs, CSMs, and 2-3 existing customers. Don't assume—pressure test.

Deliverables:

• ICP Canvas (1-page visual)

• Positioning Canvas

• Persona-Value Alignment Sheet

• Pain Point → Messaging Map

Week 2-3: TAM Mapping & Account Enrichment

The goal: Build the complete universe of accounts that fit your ICP, enriched with every data point you'll need for scoring and personalization.

Understanding customer segmentation in a successful GTM isn't optional - it's the difference between spray-and-pray and precision targeting.

Where to source accounts:

Don't build a single-source TAM. Pull from multiple places and dedupe:

• LinkedIn Sales Navigator

• Apollo

• Clay

• Ocean.io

• Industry-specific directories

• Your existing CRM (often under-leveraged)

Enrichment fields (non-negotiable):

Segment into verticals:

Group accounts into clusters that share characteristics and pain points. Examples:

• Vertical SaaS (healthcare, fintech, logistics)

• Marketplaces

• E-commerce/DTC

• Enterprise software

Each vertical may need different messaging angles.

Deliverables:

• Master TAM spreadsheet (fully enriched)

• Vertical segmentation

• Data completeness audit

Week 3-4: Account Tiering & Contact Mapping

The goal: Prioritize accounts so reps know exactly where to spend time, and ensure every account has the right people mapped.

Account Tiering Model:

Scoring inputs to consider:

• Industry match (weighted heavily)

• Tech stack alignment

• Headcount in target range

• Geography

• Business model fit

• Recent hiring for relevant roles

Contact Mapping:

For each Tier 1 and Tier 2 account, map:

For each persona, document:

• Their specific KPIs

• Their daily frustrations

• Common objections they raise

• Messaging hooks that resonate

• Appropriate CTA (meeting vs. resource vs. intro)

Deliverables:

• Tiered account list (tagged in CRM)

• Scoring model documentation

• Contact database with persona tags

• Multi-threading coverage report (contacts per account)

Month 1 Checkpoint

By Day 30, you should have:

• ICP documented with specificity

• Complete TAM enriched with firmographic + technographic data

• Accounts tiered and tagged in CRM

• Key contacts mapped with persona classifications

• Messaging foundation built from pain points

If any of these are incomplete, do not move to Month 2. The signal engine you're about to build depends on this foundation.

Month 2: Signal Engine (Days 31–60)

Making Your Data Come Alive

Month 1 built a static snapshot. Month 2 turns it into a living system.

This is where accounts stop being rows in a spreadsheet and start behaving like entities with movement, intent, and timing signals that tell you when to engage.

Most teams skip this entirely. They have "intent data" that goes into a weekly report no one acts on. That's not a signal engine. That's a graveyard.

The rise of RevOps automation for startups has made signal tracking more accessible than ever. What used to require enterprise budgets and dedicated data engineers can now be built with mid-market tools and smart workflow design.

Week 5-6: Signal Tracking Infrastructure

The goal: Capture every meaningful signal that indicates an account is moving toward a buying decision.

Signal Categories to Track:

1. Technographic Signals

• New platform adoptions

• Integration changes

• Tech stack additions/removals

• API activity indicators

Why it matters: Tech changes often indicate budget allocation, strategic shifts, or pain points your solution addresses.

2. Intent Signals

• Website visits (especially pricing, case studies, comparison pages)

• Content engagement

• Search behavior (via intent data providers)

• Job postings for relevant roles

Why it matters: Direct indicators of active evaluation or problem awareness.

3. Business Event Signals

• Funding announcements

• Leadership changes

• Partnerships/acquisitions

• Product launches

• Expansion news

Why it matters: Business events create windows of opportunity - new budget, new priorities, new decision-makers.

4. Engagement Signals

• Email opens/clicks (with recency weighting)

• LinkedIn profile views

• Content downloads

• Webinar attendance

Why it matters: Shows warming interest and helps prioritize within tiers.

Build the Signal Table:

Deliverables:

• Master signal taxonomy

• Signal source integrations

• Routing rules (signal → action)

Week 6-7: Awareness Scoring System

The goal: Score every account based on how close they are to a buying decision, updated automatically as signals flow in.

Awareness Stage Definitions:

Scoring Logic:

Build point values for each signal type. Example:

Set thresholds:

• 0-10 points: Stage 1

• 11-25 points: Stage 2

• 26-50 points: Stage 3

• 51-75 points: Stage 4

• 76+: Stage 5

Decay logic: Points should decay over time. A pricing page visit 90 days ago isn't as meaningful as one yesterday. Build in 30/60/90 day decay rates.

Understanding how to measure GTM execution success for B2B startups becomes critical here - your awareness scores should correlate with conversion rates. If Stage 4 accounts aren't converting at 20-30%+ to meetings, your scoring model needs recalibration.

Deliverables:

• Awareness scoring model

• CRM field + automation setup

• Stage-based reporting dashboard

Week 7-8: Slack Intelligence System

The goal: Make Slack your real-time CBM command center, not your inbox.

Why Slack, not email:

• Faster response times

• Easier routing to the right owner

• Creates visible accountability

• Enables team-wide signal awareness

Channel Architecture:

#signal-alerts → High-priority signals requiring action

#awareness-updates  → Stage changes across accounts

#tier1-digest → Daily/weekly rollup for top accounts

#outreach-replies → Positive/negative reply notifications

#meetings-booked → Celebration + visibility channel

Alert Format (standardize this):

SIGNAL ALERT

Account: [Company Name]

Tier: [1/2/3]

Signal: [Description]

Awareness Stage: [Current] → [New]

Owner: @[rep-name]

Context: [Brief summary of why this matters]

Suggested Action: [Specific next step]

[Link to CRM record]

Digest Cadence:

• Daily: Tier 1 accounts with any signal activity

• Weekly: Full Tier 1 + Tier 2 summary with stage movements

• Real-time: High-intent signals (pricing page, demo request, positive reply)

Deliverables:

• Slack channel structure

• Alert templates

• Routing rules (CRM owner → Slack ID)

• Digest automation workflows

Week 8: QA & Reply Routing

QA Layer:

Every week, validate:

• CRM property sync is working

• Slack routing is accurate

• Awareness scores are calculating correctly

• No signal sources have broken

Build a simple checklist and assign ownership.

Outreach Reply Routing:

Centralize all sequence reply notifications in Slack:

• Positive replies → #outreach-replies + owner DM

• Meeting booked → #meetings-booked

• Negative replies → #outreach-replies (for coaching/learning)

• Daily summary → #team-digest

Deliverables:

• Weekly QA checklist

• Reply notification automation

• Error logging system

Month 2 Checkpoint

By Day 60, you should have:

• Signal tracking live across all categories

• Awareness scoring updating automatically in CRM

• Slack acting as the intelligence hub 

• Zero manual tracking - everything flows through the system

• Reps receiving alerts within minutes of high-intent signals

If signals are being captured but not acted on, the system isn't done. Go back and fix routing before moving to activation.

Month 3: Activation (Days 61–90)

Where Intelligence Becomes Pipeline

Month 3 separates operators from amateurs.

Most teams collect signals but never operationalize them. They have dashboards that show intent but no automated response. They know an account is warming but still rely on a rep remembering to follow up.

You're going to build the system that removes that gap.

Week 9-10: Multichannel Campaign Launch

The goal: Activate Tier 1 and Tier 2 accounts with segmented, coordinated outbound across channels.

Channels to activate:

The 9-step cold outreach framework we've refined across hundreds of campaigns provides a proven sequence structure. But the magic of CBM is layering that framework with signal context - the same sequence, personalized by what triggered enrolment.

Segmentation Matrix:

Don't run one campaign. Segment by:

• Vertical: Different pain points, different proof points

• Persona: Decision-maker vs. champion vs. user

• Awareness stage: Cold vs. warming vs. engaged

• Signal type: Tech signal vs. hiring signal vs. funding signal

• Tier: Tier 1 gets higher touch

Example campaign structure:

Campaign: Fintech_VP-Sales_Stage-2_Tech-Signal

  → 5-touch email sequence

  → LinkedIn connection + 2 follow-ups

  → Retargeting pixel active

  → Trigger: Awareness score 25+

Deliverables:

• Campaign segmentation matrix

• Sequence copy (by segment)

• Channel activation tracker

• Audience sync to ad platforms

Week 10-11: Signal-Driven Triggers

The goal: Build automated triggers that launch the right outreach the moment an account signals intent.

Example Trigger Workflows:

Build the logic:

Signal detected →

Check account tier →

Check current awareness stage →

Route to appropriate sequence →

Alert owner in Slack →

Log in CRM

The emergence of AI SDRs and intelligent automation has made trigger-based outreach significantly more sophisticated. Where you once needed a human to craft every response, AI can now handle initial personalization at scale—but only if your signal engine feeds it quality data.

Deliverables:

• Trigger logic documentation

• Automation workflows (in your automation tool)

• Slack alerts for trigger events

• Sequence enrollment rules

Week 11-12: Sales Enablement & Playbooks

The goal: Give sales everything they need to act fast and act right.

Playbook Components:

1. Signal Response Playbooks

For each signal type, document:

• What the signal means

• Why it matters

• Recommended response (timing + channel + message)

• Common objections and responses

• Success metrics

2. Persona Messaging Guides

For each persona:

• Opening hooks that resonate

• Pain points to lead with

• Proof points to reference

• Objections to anticipate

• CTAs that convert

3. Sequencing Templates

Pre-built sequences for:

• Cold outreach (by vertical)

• Signal-triggered (by signal type)

• Warm follow-up (post-meeting)

• Re-engagement (gone dark)

4. System Training

Short Loom videos explaining:

• How to read Slack alerts

• How to interpret awareness scores

• How to use signal context in outreach

• How to update CRM correctly

If you're building a team alongside this system, understanding how to build a high-performing SDR system becomes essential. The CBM engine amplifies good reps - but it can't fix fundamental hiring or enablement gaps.

Deliverables:

• Signal playbook library

• Persona messaging guides

• Sequence template library

• System training videos (< 5 min each)

Week 12: Reporting & Optimization Loop

The goal: Tie all activity to pipeline and build the feedback loop for continuous improvement.

Dashboard Requirements:

Monthly Optimization Cycle:

1. Review: What worked? What didn't?

2. Adjust ICP: Any segments over/underperforming?

3. Refine tiering: Are tiers predicting conversion?

4. Improve signals: Any signals not correlating with pipeline?

5. Update messaging: What hooks are landing?

6. Evolve triggers: Any new trigger opportunities?

Deliverables:

• CBM dashboard

• Monthly review template

• Optimization backlog

Month 3 Checkpoint

By Day 90, you should have:

•  Multichannel campaigns live across Tier 1 and 2 accounts

• Signal-driven triggers automatically enrolling accounts

• Sales enablement library complete

• Attribution reporting connecting signals to pipeline

• Monthly optimization process documented and scheduled

What Exists on Day 91

If you executed this blueprint as written, here's the system you now operate:

Strategic Foundation

• ICP with enough specificity to train a new rep in one read

• Enriched TAM that's a living database, not a static export

• Tiered accounts with scores that actually predict conversion

Intelligence Layer

• Signal engine capturing tech, intent, business, and engagement signals

• Awareness scoring that updates in real-time

• Slack intelligence routing alerts to owners in minutes, not days

Activation Layer

• Multichannel campaigns segmented by vertical, persona, stage, and signal

• Automated triggers that start outreach at the right moment

• Personalization at scale (not 1:1 for every touch, but contextual)

Operational Layer

• Playbooks so reps know exactly how to respond

• Reporting that ties signals to pipeline

• Monthly optimization cycle that compounds improvement

This is the difference between "doing outbound" and "running a revenue system."

The companies scaling GTM with AI instead of headcount are building exactly this infrastructure. They're not replacing humans—they're amplifying them with systems that surface the right accounts at the right time.

Common Questions About Contact-Based Marketing

What is contact-based marketing?

Contact-based marketing (CBM) is a go-to-market system that starts with a defined ICP and enriched TAM, maps the right contacts at each target account, tracks signals indicating buying intent, and triggers personalized multichannel outreach when accounts show movement. Unlike campaign-based approaches, CBM operates continuously - identifying, scoring, and activating accounts in real-time.

How is CBM different from ABM?

Account-based marketing (ABM) is typically campaign-led - you select accounts, run a coordinated campaign, measure results, repeat. CBM is system-led. It builds infrastructure for continuous signal capture, automated awareness scoring, and trigger-based activation. ABM asks "which accounts should we target this quarter?" CBM asks "which accounts are showing intent right now?"

How long does it take to build a CBM engine?

A functional CBM engine can be built in 90 days following this blueprint: Month 1 for data intelligence (ICP, TAM, tiering), Month 2 for signal engine (tracking, scoring, Slack routing), Month 3 for activation (campaigns, triggers, playbooks). Cutting corners on early months creates downstream problems.

What makes a CBM engine predictable?

Predictability comes from: (1) ICP clarity that ensures you're targeting accounts likely to buy, (2) a complete TAM so you're not missing opportunities, (3) account and persona scoring that focuses effort on the right places, (4) a signal engine that surfaces intent as it happens, (5) awareness stages that show where accounts sit in their journey, and (6) automated triggers that ensure timely response regardless of rep attention.

What tools do I need for CBM?

Core stack typically includes: CRM (HubSpot or Salesforce), enrichment tools (Clay, Apollo, or similar), signal tracking (combination of website analytics, technographic providers, and intent data), automation platform (for triggers and sequences), and Slack (for real-time routing). The specific tools matter less than the system design.

Can a small team run CBM?

Yes. CBM is actually more valuable for small teams because it multiplies effectiveness. A 2-person outbound team with a working CBM engine will outperform a 6-person team doing manual spray-and-pray. The automation handles the monitoring; humans handle the conversations.

With a logistics tech startup we advised, a 3-person GTM team using this exact blueprint generated approximately 25-35% more qualified pipeline than their previous 5-person team running traditional outbound. The system did the signal detection; the humans focused on high-value conversations.

Ready to Build Your CBM Engine?

If you want this running in your org in 90 days, Phi Consulting builds CBM engines end-to-end for B2B startups and scaleups through our outbound GTM pods.

We handle: ICP and positioning, TAM enrichment, signal infrastructure, awareness scoring, Slack intelligence routing, and multichannel activation that converts signals into qualified meetings.

To start the conversation, reply with:

1. Your current ICP (or best guess)

2. Your CRM (HubSpot/Salesforce/other)

3. Channels you use today (email, LinkedIn, paid, etc.)

4. Biggest pipeline challenge right now

We'll map a practical 90-day rollout tailored to your team, stack, and revenue targets.