3 B2B Automation Workflows You Can Ship This Week

Walk the floor of a 20-person B2B company and you will find the same scene: a rep copy-pasting a company name from the CRM into a data enrichment tool, copying the results back into custom fields, then manually picking which leads to call. They do this 40 times a day. The process works. It is also burning hours every week that no revenue leader has line-of-sight into.

According to the Salesforce State of Sales report (2025), sales reps spend only 28% of their time actually selling. The rest goes to data entry, internal coordination, and tasks that automation can handle faster and more reliably. The question is not whether automation matters — it is which workflows deliver the fastest payback with the least setup friction.

Workflow 1: CRM Auto-Enrichment

Here is the manual version: a lead lands in the CRM with a company name and domain. The SDR opens a second tab, searches the company on a data provider, copies the employee count, industry, revenue range, and tech stack into custom CRM fields. Multiply by 40 leads per day across 3 SDRs. That is 120 manual data entry sessions, conservatively 2 minutes each, or 4 hours per day absorbed by copy-paste.

The automated version: a webhook fires on new lead creation. A middleware layer (Zapier, Make, or n8n running in your cloud environment) queries your enrichment provider's API, maps the response to your CRM fields, and writes the data back. The lead is enriched before the SDR sees it.

The enrichment workflow has three stages that should run sequentially:

1. Firmographic enrichment. Pull company size, industry classification, revenue band, and HQ location from your enrichment provider. Map these to standard CRM fields. This gives segmentation and routing engines the data they need to operate.
2. Technographic enrichment. Detect the company's existing stack — which CRM they use, which marketing automation platform, which analytics tools. Required for account qualification and for triggering context-aware sequences.
3. Contact enrichment. Match the lead's email domain and name to enrich title, department, seniority, and LinkedIn profile. This data feeds territory routing and personalization logic.

Implementation time: 2–3 days for a functional version. Day 1 is API connectivity and field mapping. Day 2 is error handling — what happens when the enrichment API returns no match or partial data. Day 3 is testing on a sample batch before deploying to the live pipeline.

Workflow 2: Lead Routing Automation

Manual lead routing sounds fine at small scale: new lead appears, manager or ops person assigns it to a rep based on territory or availability. At 20 leads per day, it works. At 100 leads per day, it breaks. First-response time stretches from minutes to hours. High-intent leads sit unmatched while low-intent leads get priority because they arrived at a quieter moment.

Automated routing replaces human assignment with a rules engine. When a lead is created and enriched, a routing job fires. It evaluates: territory match, segment priority, rep availability and capacity, round-robin position. The lead is assigned and the rep receives a notification before the data entry step would have finished in the manual version.

The routing logic should operate on explicit tiers:

• Tier 1 — Hot inbound or high-intent signal. Immediate assignment to the first available qualified rep. Bypass round-robin. First-response target: under 5 minutes.
• Tier 2 — Standard inbound or qualified outbound response. Round-robin within territory. First-response target: under 30 minutes during business hours.
• Tier 3 — Event-triggered or content-download leads. Queue for next-available rep with a 4-hour response SLA. These leads still benefit from speed but the cost of immediate assignment exceeds the value.

Overflow handling is the part most routing implementations skip. What happens when all territory reps are at capacity? The lead enters a queue with a response SLA. If the SLA expires, the lead escalates to a manager or a backup rep outside the territory. Without this escalation path, overflow leads become invisible — sitting in an inbox without an owner.

Implementation time: 2–4 days. Day 1 defines the routing rules and tiers. Day 2 builds the assignment logic. Day 3 adds overflow and escalation. Day 4 tests across edge cases: duplicate leads, reassigned territories, reps on leave.

Workflow 3: Follow-Up Trigger Sequences

Every B2B pipeline leaks at the follow-up step. A lead reaches "proposal sent" or "demo completed" status. The rep intends to follow up. The calendar fills. The follow-up slips to tomorrow, then next week, then never. The revenue cost of these lost follow-ups is invisible — it shows up as "no response" rather than "we dropped the ball."

Follow-up trigger sequences solve this with automation that monitors CRM status changes and fires the next action automatically. When a lead enters "proposal sent," the system schedules a follow-up task with a 48-hour deadline. If the task is not completed, it escalates: a reminder to the rep at 72 hours, then a notification to the manager at 120 hours with the lead's details and deal value.

The triggers that matter most:

1. Demo completed, no next step scheduled. Within 24 hours, send the rep a prompt with the lead context and suggested follow-up cadence. If no next step exists after 72 hours, flag for manager review.
2. Proposal sent, no response after 48 hours. Trigger a personalized follow-up email template that the rep can review and send with one click. At 96 hours without response, add the lead to a re-engagement nurture sequence.
3. Deal stalled — no status change in 14 days. Surface the deal in a daily "stalled deals" digest sent to the rep and their manager. Include deal age, value, and last activity date.
4. Decision-maker went dark. If a key contact has not responded to any channel in 10 days, trigger a multi-channel re-engagement attempt: email, then a LinkedIn touch 3 days later, then a manager-level outreach at day 15.

The key design decision: automated tasks should suggest, not command. The rep still owns the relationship and the judgment. The automation provides the safety net, ensuring that no deal slips through a crack in attention. When the rep sees "follow up on proposal sent to Acme Corp — 72 hours since send," they can execute the follow-up or override the reminder with a reason note.

Implementation time: 3–4 days. Day 1 maps your pipeline stages to trigger points. Day 2 builds the trigger logic and task creation. Day 3 adds escalation paths. Day 4 adds manager notifications and the daily digest.

How to Pick Your First Workflow

Ship one workflow before you design three. Pick based on where the pain is measurable, not where the automation feels most interesting. Three questions to decide:

• What manual task consumes the most rep hours? If it is data entry, start with auto-enrichment. If it is lead distribution, start with routing. If it is follow-up discipline, start with trigger sequences.
• Which workflow requires the fewest cross-team dependencies? Auto-enrichment touches CRM config and one external API. Routing requires sales ops input on territory rules. Follow-up triggers require pipeline stage definitions. Ship the workflow that requires the least coordination first.
• Where is the failure visible to leadership? If the CEO asks "why did we lose the Acme deal" and the answer traces to a missed follow-up, start with trigger sequences. Visible failures create alignment for automation investment.

Measuring ROI Across the Three Workflows

The ROI of these workflows shows up in three places. Track all three from the week before implementation to establish a baseline:

Track these metrics for 90 days. The first 30 days will show process improvement — fewer manual tasks, faster responses. The second 30 days will show pipeline improvement — more qualified conversations, fewer dropped deals. The third 30 days will show revenue impact — higher conversion rates and shorter sales cycles.

Key Takeaways

1. Start with one workflow. Auto-enrichment gives you clean data. Automated routing gives you fast assignment. Follow-up triggers give you pipeline discipline. Pick the one that solves the most visible problem for your team.
2. Build on your existing stack. These workflows work with the CRM you already have. They do not require a platform migration, a procurement cycle, or a 6-month implementation. The automation layer connects what you already use.
3. Measure from day zero. Establish baselines before you ship. Without a before-and-after comparison, automation ROI is a story, not a number. The numbers are what justify the next automation investment.
4. Automate the safety net, not the judgment. Follow-up triggers should surface actions the rep should take, not take those actions without review. Automation protects the pipeline from human forgetfulness; it does not replace human judgment about which leads deserve attention.