GTM Automation: 7 Workflows Every B2B Company Should Build First

I have built over two hundred GTM automation workflows across more than forty B2B companies. Some of those workflows were brilliant ideas that produced nothing. Others were simple implementations that generated millions in pipeline. The difference was not complexity or cleverness—it was prioritization. Building the right workflows in the right order is what separates a productive GTM engineering effort from one that creates impressive technology and disappointing results.

After years of trial and error, I have distilled my approach down to seven foundational workflows that every B2B company should build before they do anything else. They are ordered by ROI and dependency—build Workflow 1 before Workflow 2, because each one feeds the next. If you build all seven in the right order, you will have a functioning automated pipeline system within thirty days.

Workflow 1: Waterfall Enrichment Pipeline

Every other workflow depends on data quality, so this comes first. The waterfall enrichment pipeline takes raw prospect data—typically a company name and domain—and outputs a fully enriched contact record with verified email, phone number, company attributes, and ICP score.

The Build: In Clay, create a table with columns for your waterfall providers (ZoomInfo, Apollo, Clearbit, and a fallback). Add formula logic to select the best email and phone from across providers. Add a verification step. Add enrichment columns for company revenue, employee count, industry, technologies, and recent news. Finally, add an ICP scoring formula that weights each attribute and outputs a 0-100 score.

Trigger: Manual upload of new prospect lists, or automated feed from Workflow 3 (intent signals).

Output: Enriched, verified, scored prospect records ready for outbound. Pushed to HubSpot via API or Clay's native integration.

Time to Build: 4-6 hours.

Expected Impact: Increases email find rate from 75-82% (single provider) to 90-94% (waterfall). This means 10-20% more prospects receive your outreach, which directly translates to more meetings.

Workflow 2: Automated Outbound Sequencing

Once prospects are enriched and scored, they need to enter an outbound sequence automatically. This workflow eliminates the manual step of an SDR reviewing leads and manually enrolling them in sequences.

The Build: In HubSpot, create workflow triggers based on ICP score thresholds. Score 80-100 triggers enrollment in your high-touch sequence in Salesloft. Score 60-79 triggers enrollment in your medium-touch sequence. Score 40-59 triggers a lightweight automated sequence. Below 40 enters a nurture track or is excluded.

Each sequence should include personalized email content generated by Claude AI during the enrichment step (Workflow 1). The personalization—a custom first paragraph referencing specific company attributes—is generated in Clay and stored as a contact property in HubSpot, then pulled into the Salesloft sequence template as a merge field.

Trigger: New enriched contact created in HubSpot with ICP score above threshold.

Output: Prospect automatically enrolled in the appropriate multi-step outbound sequence with personalized messaging.

Time to Build: 3-4 hours (assuming sequences and templates already exist).

Expected Impact: Eliminates 2-3 hours of daily manual work per SDR. Reduces time from enrichment to first outreach from 24-48 hours to under 30 minutes. Ensures no qualified prospect falls through the cracks.

Workflow 3: Intent Signal Detection and Routing

This is the workflow that transforms your outbound from spray-and-pray to signal-driven. Instead of working through static lists, you are identifying companies showing buying behavior right now and engaging them within minutes.

The Build: In N8N, create a workflow with multiple trigger nodes that monitor different signal sources: website visitor identification from RB2B or Clearbit Reveal (captures companies visiting your site), job posting monitoring via LinkedIn or Indeed APIs (identifies companies hiring for roles your product serves), funding announcements via Crunchbase API (targets companies that just raised capital), and technology adoption signals via BuiltWith or similar services (identifies companies adding or removing relevant tools).

Each signal is normalized into a standard format, deduplicated against existing CRM records, and routed to the Workflow 1 enrichment pipeline. Companies that pass the ICP score threshold are automatically processed through Workflow 2 and enter outbound sequences.

Trigger: Continuous monitoring on scheduled intervals (every 30-60 minutes for website visitors, every 6-12 hours for job postings and funding).

Output: Intent-qualified prospects automatically enriched and enrolled in signal-specific outbound sequences.

Time to Build: 6-8 hours.

Expected Impact: Intent-signal-triggered outbound converts to meetings at 2-3x the rate of static list-based outbound. This single workflow typically generates 30-40% of total meetings within 60 days of deployment.

Workflow 4: Meeting Booking and Qualification

When a prospect responds positively to outreach, the handoff from automation to human conversation needs to be seamless. This workflow automates meeting booking, pre-populates the AE with context, and ensures qualification happens before the AE's time is spent.

The Build: Integrate a scheduling tool (Calendly, Chili Piper, or HubSpot Meetings) with your sequences. When a prospect responds with buying intent—detected by keyword analysis or Claude AI sentiment classification—the system automatically sends a meeting link with the right AE based on territory, segment, or round-robin rules.

When a meeting is booked, HubSpot automatically creates a deal, attaches all enrichment data and interaction history, generates a pre-meeting brief using Claude AI that summarizes the prospect's company, their likely pain points based on ICP data, the signal that triggered outreach, and recommended talk tracks. This brief is delivered to the AE via Slack or email thirty minutes before the call.

Trigger: Positive reply detected in Salesloft or HubSpot.

Output: Meeting scheduled, deal created, AE briefed with full context—all without manual intervention.

Time to Build: 4-5 hours.

Expected Impact: Reduces time from positive reply to scheduled meeting by 60-70%. Increases AE meeting preparation quality. Improves meeting-to-opportunity conversion rate by 15-25% because AEs enter conversations better prepared.

Workflow 5: Lead Scoring and Re-Engagement

Not every prospect converts on the first sequence. This workflow ensures that prospects who showed interest but did not book get re-engaged at the right time with the right message.

The Build: In HubSpot, build a behavioral scoring model that tracks engagement signals: email opens (1 point each), link clicks (5 points each), website visits (10 points each), content downloads (15 points each), and LinkedIn profile views (3 points each). Set a threshold—typically 25-30 points—that triggers re-engagement.

When a prospect exceeds the threshold, the workflow checks if they are in an active sequence. If not, it routes them back to Clay for data refresh (Workflow 1), generates new personalized messaging using Claude that references their engagement history—"I noticed you checked out our case study on [topic]"—and enrolls them in a re-engagement sequence in Salesloft.

Trigger: Prospect engagement score exceeds threshold and prospect is not in active sequence.

Output: Re-engaged prospects enter a fresh sequence with messaging that acknowledges their previous interest.

Time to Build: 3-4 hours.

Expected Impact: Recovers 10-15% of prospects who did not convert on initial outreach. These re-engaged prospects typically convert at higher rates because they have already shown interest.

Workflow 6: CRM Hygiene and Data Decay Prevention

Data decays at roughly 30% per year in B2B. People change jobs, companies get acquired, email addresses expire. This workflow prevents your CRM from becoming a graveyard of stale data.

The Build: Create a scheduled N8N workflow that runs monthly. It pulls all contacts from HubSpot that have not been enriched or verified in the last 90 days. It runs them through a lightweight enrichment check via Clay—just email verification and job title validation, not the full waterfall—to identify which records have decayed.

Contacts with bounced emails get flagged for re-enrichment through the full waterfall. Contacts who have changed companies get updated with new company information and are re-scored against the ICP. Contacts who now match ICP criteria better than before (for example, someone who moved from a non-target to a target company) are flagged as new prospects and routed to Workflow 2.

Trigger: Scheduled monthly (first Monday of each month).

Output: Clean, current CRM data. Recovered prospects from job changes. Prevented bounces from stale emails.

Time to Build: 3-4 hours.

Expected Impact: Prevents 5-8% monthly degradation in email deliverability. Recovers 2-5 new qualified prospects per month from job changers. Maintains CRM data quality that all other workflows depend on.

Workflow 7: Performance Reporting and Optimization Alerts

The final foundational workflow ensures you always know how your pipeline system is performing and are alerted when something needs attention.

The Build: In N8N, create a workflow that runs daily and pulls performance metrics from HubSpot, Salesloft, and Clay. It calculates key metrics: meetings booked (daily, weekly, monthly), reply rate by sequence, cost per meeting, enrichment success rate, bounce rate, and pipeline value created. It formats these into a daily Slack summary sent to the revenue channel.

Additionally, set up alert thresholds: if reply rate drops below 5%, if bounce rate exceeds 3%, if enrichment find rate drops below 88%, or if daily meeting volume falls below the trailing 7-day average by more than 40%—an alert triggers immediately in Slack with the specific metric, the deviation from target, and a suggested diagnosis.

Trigger: Scheduled daily at 8:00 AM local time. Alerts trigger in real-time when thresholds are breached.

Output: Daily performance dashboard in Slack. Real-time alerts for performance degradation.

Time to Build: 4-5 hours.

Expected Impact: Reduces time to identify and fix performance issues from days to hours. Provides leadership with consistent, automated pipeline visibility. Enables data-driven optimization decisions.

Building Order and Timeline

Here is the recommended build order and timeline:

• Week 1: Workflow 1 (Enrichment) + Workflow 2 (Sequencing) — Foundation
• Week 2: Workflow 3 (Intent Signals) + Workflow 4 (Meeting Booking) — Scale
• Week 3: Workflow 5 (Re-engagement) + Workflow 6 (Data Hygiene) — Optimization
• Week 4: Workflow 7 (Reporting) + Testing and Refinement — Measurement

By the end of Week 4, you have a complete automated pipeline system that identifies prospects, enriches their data, scores them against your ICP, engages them with personalized multi-channel outreach, handles positive responses, re-engages warm prospects, maintains data quality, and reports on performance—all with minimal manual intervention.

This is the stack I deploy for every fractional BDM engagement, and it consistently delivers 40-70 qualified meetings per month within 60-90 days of deployment. If you want help implementing these workflows, book a call and I will walk you through exactly how they map to your specific sales process, ICP, and tech stack. For companies interested in broader AI automation consulting, these seven workflows are typically just the starting point. For the AI layer that supercharges these workflows, read about agentic automation for GTM engineers. To measure what these workflows actually produce, check my GTM engineering ROI framework.