CRM Workflow Example: 5 Real B2B Pipeline Setups

Why Most CRM Workflows Are a Lie

I've looked at the pipelines of hundreds of agencies and B2B sales teams. The pattern is almost always the same: six or seven stages that nobody defined, deals sitting in "Proposal" for 45 days, and a forecast that's pure fiction.

A CRM workflow is not a list of stages. It's a system with entry criteria, exit criteria, automated actions, and clear ownership at every step. Without those four things, your CRM is just a digital version of a napkin - and probably less reliable.

This article breaks down five real CRM workflow examples you can model, steal, or adapt. Each one is built around a specific sales motion: cold outbound, inbound demo, agency retainer, high-ticket coaching, and local service business. Pick the one closest to your situation and make it yours.

What a CRM Workflow Actually Is (and What It Isn't)

Before we get into examples, let's be clear on definitions - because there's a lot of confusion here.

A CRM workflow is a sequence of automated actions triggered by specific conditions in your CRM system. Think of it as "if this happens, then do that" logic applied to your sales process. When a lead fills out a form, the workflow might automatically create a contact record, assign it to a rep based on territory, send a confirmation email, and create a follow-up task - all without anyone touching the keyboard.

What it is NOT: a checklist you manually work through. Not a set of sticky notes on your monitor reminding you to follow up. Not a spreadsheet someone updates once a week if they remember.

The components of any real CRM workflow break down into three parts:

• Triggers: The event that starts the workflow. This could be user-initiated (a rep adds a new lead), customer-initiated (a prospect fills out a form or clicks a link), or time-based (no activity logged in 7 days, contract renewal approaching in 90 days). Triggers are the "if" in your "if-then" rule.
• Conditions: Rules that determine whether the workflow should continue or branch. A condition might check whether a lead's company has more than 50 employees before routing to a senior rep, or whether a deal value exceeds a threshold before flagging a manager. Good conditions are the difference between automation that feels relevant and automation that feels like spam.
• Actions: What actually happens after the trigger fires and conditions are met. Standard actions include sending an email, creating a follow-up task, assigning the record to a team member, updating a field, sending an internal notification, or moving a deal to the next stage. Most CRMs let you chain multiple actions together and add timing delays between them.

The sequence "send an email immediately, wait three days, then create a follow-up task if no reply" is a single workflow with two actions and a delay condition. That's the basic architecture. Now let's apply it to real sales situations.

The Core Structure Every CRM Workflow Needs

Before we get into the examples, let me lay down the architecture. Every stage in your CRM needs three things, or it doesn't belong in your pipeline:

• Entry criteria: The specific, observable thing that must be true before a deal moves INTO this stage. Not "had a good call." Something like: "Prospect confirmed budget range and agreed to receive proposal."
• Exit criteria: What has to happen before the deal moves OUT. This is the most important piece. Without exit criteria, deals drift and your forecast becomes guesswork. Exit criteria determine when deals can advance to the next stage, preventing reps from guessing, keeping pipelines accurate, and making forecasts reliable.
• Automated action: What your CRM does automatically when a deal hits this stage - send an email, create a task, alert a manager, start a sequence.

Most teams have stage names. Few have all three of those elements. That's the gap between a CRM that works and one that's ignored.

One more thing before the examples: a workflow should stop automatically when its goal is met. If a prospect replies, the follow-up sequence should pause immediately. Otherwise you're automating yourself into being annoying - which is worse than no automation at all. A single follow-up can double booked call rates, but only if it stops the moment the prospect engages.

CRM Workflow Example 1: Cold Outbound (Agency or B2B Service)

This is the workflow I've used and refined across multiple agencies. It's built for a sales cycle where you're sending cold emails, booking calls, and selling a service or retainer.

• Stage 1 - Prospect: Contact exists in CRM, not yet contacted. Entry: imported from lead list. Automated action: enroll in cold email sequence via Smartlead or Instantly. Exit: prospect replies or books a call.
• Stage 2 - Engaged: Prospect replied or opened 3+ times. Entry: reply or meeting booked. Automated action: assign task to rep to call within 24 hours. Exit: discovery call completed.
• Stage 3 - Discovery Done: Call happened, pain confirmed. Entry: rep logs call outcome. Automated action: create "send proposal" task due in 48 hours. Exit: proposal sent.
• Stage 4 - Proposal Sent: Written proposal delivered. Entry: proposal email logged in CRM. Automated action: follow-up task in 3 days if no response. Exit: verbal yes or explicit no.
• Stage 5 - Negotiation: Prospect is interested, discussing terms. Entry: positive response to proposal. Automated action: flag for manager review if deal is above threshold. Exit: contract sent.
• Stage 6 - Contract Out: Agreement sent, waiting on signature. Entry: contract sent via DocuSign or similar. Automated action: follow-up task every 2 days. Exit: signed or lost.

For building your prospect list in Stage 1, you need clean contact data before anything else. I use this B2B lead database to filter by job title, industry, company size, and location - then import those contacts directly into my CRM. No manual hunting.

You'll also want to validate emails before enrolling in sequences. Bounce rates above 3-4% tank your sending reputation fast. Run your list through ScraperCity's email validator before anything hits your outbox.

If you're also running cold calls alongside the email sequence - which you should be at Stage 2 - you need direct dials, not switchboard numbers. This mobile finder tool pulls direct phone numbers for your prospects so your reps aren't burning time trying to get past receptionists.

And track your metrics throughout. I have a cold email tracking sheet template you can grab for free - it'll show you where your pipeline is leaking at each stage.

CRM Workflow Example 2: Inbound Demo Request

This one's different. The prospect raised their hand - they submitted a form, booked a demo, or replied to an ad. The workflow is faster and the stakes are higher because speed-to-response directly impacts close rate. When a lead comes in, the first few minutes matter more than most people acknowledge. If your process relies on someone seeing an email notification, opening the CRM, assigning the record, and remembering the next step, you're already slower than you should be.

• Stage 1 - Demo Requested: Form submitted or meeting booked. Automated action: instant confirmation email, internal Slack alert to AE. Exit: AE confirms demo or reschedules.
• Stage 2 - Demo Completed: Product walkthrough done. Entry: AE logs outcome. Automated action: send recap email with next steps automatically within 2 hours. Exit: follow-up call scheduled or proposal requested.
• Stage 3 - Evaluation: Prospect is actively evaluating. Entry: confirmed interest post-demo. Automated action: send case study or reference customer intro. Exit: proposal sent or disqualified.
• Stage 4 - Proposal/Trial: Formal proposal out or trial underway. Entry: proposal sent or trial started. Automated action: check-in task every 4 business days. Exit: verbal commit or hard no.
• Stage 5 - Closed Won/Lost: Entry: decision made. Automated action on Won - trigger onboarding sequence, notify customer success. Automated action on Lost - log loss reason, move to nurture sequence.

The loss reason field matters more than most people realize. "Lost to competitor," "budget cut," "went dark" - these become your most valuable intelligence over time. Teams that skip this are operating blind on their close rate analysis. Make it a required field. You cannot improve what you don't measure.

One more thing on inbound: don't let lead routing be manual. If your process relies on someone seeing an email and then manually assigning the record to the right rep, you will lose deals to slower response time. Build the routing logic directly into your CRM so the assignment happens in seconds, not hours. Add an automation that re-routes if the lead isn't touched within a set window.

CRM Workflow Example 3: High-Ticket Coaching or Course Sale

Selling a high-ticket program is a different animal. There's more trust-building required, the sales cycle can span weeks, and the deal typically hinges on a single conversation with the decision-maker (often the buyer themselves, not a committee).

• Stage 1 - Lead: Downloaded a resource, watched a video, engaged with content. Entry: opt-in or engagement trigger. Automated action: email nurture sequence starts. Exit: books a call.
• Stage 2 - Call Booked: Strategy call or discovery call on calendar. Entry: booking confirmed. Automated action: pre-call email with questionnaire. Exit: call completed.
• Stage 3 - Call Completed: Conversation happened. Entry: rep logs outcome and notes. Automated action: send follow-up email within 1 hour of call end. Exit: verbal interest or explicit no.
• Stage 4 - Follow-Up: Prospect interested but hasn't committed. Entry: interest confirmed, no payment yet. Automated action: two-touch follow-up sequence over 5 days. Exit: payment made or final no.
• Stage 5 - Enrolled/Lost: Entry: payment processed or prospect declines. Automated action on Enrolled - trigger onboarding email, add to community, assign success manager task.

The nuance in this workflow is the pre-call questionnaire. It sounds minor, but it does two things: it filters out people who aren't serious (anyone who won't fill out a short form before a call is probably not a buyer), and it gives you the information you need to personalize the conversation before it starts. Both outcomes are valuable.

For this kind of workflow, Close CRM handles it well because you can trigger entire follow-up sequences automatically when a deal changes stages, and the workflow pauses the moment a prospect replies or books - so you're not spamming someone who's already engaged.

I cover the full sales process for high-ticket offers inside Galadon Gold if you want to go deeper on this motion.

CRM Workflow Example 4: Agency Retainer Renewal

Most agencies ignore the back half of their CRM. They win the deal, hand it to delivery, and forget the client exists until there's a crisis. That's backward. Your best pipeline for new revenue is your existing clients.

• Stage 1 - At Risk: Client hasn't seen results in 60+ days, or usage is declining. Entry: automated trigger from account health score. Action: CSM or account manager task to schedule check-in call.
• Stage 2 - Renewal Discussion: Renewal date within 90 days. Entry: date-based trigger. Automated action: send renewal deck or proposal draft. Exit: renewal confirmed or cancellation initiated.
• Stage 3 - Upsell Opportunity: Client hitting capacity or hitting results ceiling. Entry: rep flags manually after QBR. Automated action: create upsell proposal task. Exit: upgraded or passed.
• Stage 4 - Churned: Contract ended. Entry: cancellation confirmed. Automated action: log churn reason, add to win-back nurture sequence 90 days out.

The win-back sequence matters. I've seen agencies recover 15-20% of churned clients within 6 months simply by having a structured nurture in place. Most agencies have no such thing - they just hope the client comes back.

The date-based trigger for renewals is the piece most agencies set up wrong. Don't trigger it at 30 days out - that's too late to have a real conversation. Trigger it at 90 days. That gives you enough runway to address problems, demonstrate value, and close the renewal before anyone starts shopping alternatives. Handoffs between teams are where deals stall and context gets lost, so document client goals and make sure your account team has full pipeline visibility from day one.

CRM Workflow Example 5: Local Service Business (Contractor, Agency Selling to SMBs)

If you're selling to local businesses - contractors, restaurants, professional services - your workflow looks different. Shorter cycles, higher contact frequency, more phone-driven.

• Stage 1 - Lead: Contact sourced from local directory or referral. Entry: added to CRM. Automated action: assign to rep for same-day call. Exit: conversation completed.
• Stage 2 - Quoted: Price or scope discussed verbally or via email. Entry: quote sent. Automated action: follow-up call task in 2 days. Exit: accepted, negotiating, or lost.
• Stage 3 - Verbal Yes: Prospect said yes on the phone. Entry: rep marks stage. Automated action: send agreement immediately, follow up if not signed within 24 hours. Exit: signed.
• Stage 4 - Active Client: Signed and onboarded. Entry: signature received. Automated action: kickoff email, intro task for delivery team. Exit: project complete or renewed.

For this motion, your list-building starts at the local level. ScraperCity's Maps scraper pulls local business data from Google Maps - names, categories, phone numbers, websites - so you can build targeted prospect lists by city and niche without any manual searching.

If you're selling to home services contractors specifically - HVAC, plumbing, roofing - you can also pull data from Angi's contractor database to find prospects who are already paying for lead gen and might be open to switching or supplementing with your service. Same principle, different source.

For local businesses, the most important automation is Stage 1: assign the lead to a rep for a same-day call. One missed lead assignment can mean a lost sale. One forgotten reminder can turn into a no-show. Build the rule into your CRM so it's not dependent on anyone's memory.

How to Build a CRM Workflow From Scratch (Step-by-Step)

If you're looking at the examples above and thinking "okay, but how do I actually build this" - here's the practical sequence. You don't need to be technical. You need to be clear on your process before you touch the software.

1. Map your current process on paper first. Before you open your CRM, write down every step a deal goes through from first contact to close. Don't build automation around a broken process - fix the process, then automate it. A workflow that does one thing well is more valuable than an elaborate system that nobody trusts.
2. Define the trigger for each stage. What specific event moves a deal into this stage? "Had a call" is not a trigger. "Rep logged call outcome as positive and created proposal task" is a trigger. Be specific enough that two different reps would make the same call.
3. Set your conditions. Not every deal should behave the same way. Large deals might need manager approval before a proposal goes out. Deals from certain lead sources might go into a different nurture sequence. Conditions are what make your automation smart instead of mechanical.
4. Assign the action. For each stage transition, decide: what does the CRM do automatically? Send an email? Create a task? Fire a Slack notification? Update a field? Keep it to one or two actions per trigger at first. You can add complexity later once you see how the simple version performs.
5. Set your goal. This is the event that stops the workflow. If you're running a follow-up sequence after a proposal, the goal should be "prospect replies" or "meeting booked." The moment that goal is met, the sequence stops. This prevents you from following up with someone who's already in active conversation with your rep.
6. Test before going live. Run a test deal through the workflow manually. Make sure the triggers fire correctly, the actions execute in the right order, and the goal stops the sequence when it should. Most problems are caught here if you actually test.
7. Document it. Write down what triggers each workflow, what conditions it checks, and what actions it takes. If the person who built it leaves, someone else needs to be able to maintain it. This sounds boring, but it saves enormous headaches six months from now.

Start with basic automations that address your biggest pain points. Get them working reliably. Then add complexity gradually as you understand how the system behaves in practice. Building automation without a clear plan is how teams end up with 40 workflows that overlap, contradict each other, and fire at the wrong moments.

CRM Workflow Types: Real-Time vs. Background

One thing most articles skip over: not all CRM workflows operate the same way. Understanding the difference helps you choose the right type for each use case.

Real-time workflows fire instantly when a trigger event occurs. A prospect submits a demo request form - immediately, a Slack notification fires, a task is created, and a confirmation email goes out. These are best for time-sensitive events where speed directly affects outcomes. Lead routing, demo confirmations, and contract follow-ups should all be real-time.

Background (time-based) workflows run on a schedule or after a delay. A deal has been sitting in "Proposal Sent" for 7 days with no activity - the CRM checks this condition on a schedule and fires a follow-up task if the condition is met. These are best for monitoring and nudging without overwhelming your team with immediate alerts.

Branch workflows use conditional logic to send deals down different paths based on criteria. If deal value is above $10,000, send to the enterprise sales track. Below that, route to SMB. Branch workflows are the most powerful and the most complex - build them after you've got simple workflows running cleanly.

Most CRM platforms handle all three types. The key is knowing which type fits each use case rather than defaulting to one pattern for everything.

The Automation Logic That Ties It All Together

Regardless of which workflow example you model, the automation logic follows the same pattern inside most modern CRMs:

1. Trigger: Something happens (deal moves to a stage, date passes, prospect replies, form submitted).
2. Action: CRM does something automatically (sends email, creates task, alerts rep, moves deal, starts sequence).
3. Goal: If the desired outcome happens (reply, meeting booked, status change), the automated sequence pauses so you're not over-communicating with someone already in conversation.

This trigger-action-goal architecture is exactly how Close structures its workflow engine - and it's the right mental model regardless of what tool you're using. You can replicate this logic in HubSpot, Monday CRM, or most other modern CRMs.

The key is that a workflow should stop automatically when its goal is met. Otherwise you're automating yourself into being annoying. Better workflows reach people where they respond - that may mean email for a proposal, SMS for an appointment reminder, and a direct call for a lead who stopped replying.

Lead Sourcing: Where Your Workflow Data Comes From

A CRM workflow is only as good as the data going into it. Garbage contacts produce garbage pipeline - no matter how well your automation is configured. Here's how I source data for each of the five workflows above.

Cold outbound (Workflow 1): I start with ScraperCity's B2B database to filter prospects by job title, seniority, industry, and company size. I then run the list through email validation before importing into the CRM and enrolling in sequences. This two-step process - build, then validate - keeps bounce rates low and sender reputation intact.

Inbound demo (Workflow 2): Data comes in through your website forms and ad platforms. The work here is making sure your CRM form fields map correctly to your deal records so routing conditions can read the right data. If a lead's company size field is blank, your routing condition can't fire correctly.

High-ticket coaching (Workflow 3): Leads come from content, YouTube, and opt-in pages. The CRM needs to capture UTM source data so you can see which content is generating your most qualified calls. Add UTM fields to every contact record and populate them automatically when leads opt in.

Retainer renewal (Workflow 4): Data is already in your CRM - you just need to make sure contract end dates are populated for every client record. Without that field, your date-based trigger can't fire. Audit your existing client records and fill in missing contract dates before you build the automation.

Local service (Workflow 5): For local prospecting, I use the Maps scraper to pull targeted business lists by city and category. If I'm prospecting real estate professionals, I'll layer in data from Zillow's agent database to find licensed agents with active listings. Niche-specific sources produce better prospect quality than generic B2B databases.

In every case, the rule is the same: clean data before the workflow starts. Automated systems amplify bad data. If CRM records are outdated or duplicated, enrichment pipelines and outbound sequences propagate errors at scale. Fix the data first, then build the automation.

How to Audit Your Current CRM Workflow

If you already have a CRM set up, here's a fast audit to run this week:

• Pull every deal that's been in the same stage for more than 30 days. Those are stalled - either advance them or mark them lost. Letting them sit inflates your pipeline and destroys forecast accuracy.
• Check whether every stage has a defined exit criterion. If you can't write it in one sentence, it doesn't have one.
• Look at your loss reasons. If you have none logged, you're flying blind. Add a required "loss reason" field to your Closed Lost stage today.
• Check stage conversion rates. If you're losing 60% of deals between Proposal and Decision, that's not a closing problem - it's a qualification problem upstream.
• Review your automated actions. Are they actually firing? Go look at your workflow run logs. Most teams set up automation and never check whether it's executing correctly. A workflow that silently fails is worse than no workflow at all.
• Check for overlapping workflows. If you have a deal that qualifies for three different follow-up sequences simultaneously, the prospect is getting hammered with messages from multiple automations. Map out which workflows can run concurrently and add exclusion logic where needed.

For tracking all of this without building a custom dashboard from scratch, I have a free Sales KPIs Tracker that covers stage conversion, deal velocity, pipeline coverage, and close rate in one sheet.

Common CRM Workflow Mistakes (And How to Fix Them)

I've audited enough pipelines to see the same mistakes repeat across teams of every size. Here are the ones that kill the most deals:

Mistake 1: No exit criteria on any stage. This is the most common. Deals drift because nobody defined what "done" looks like at each stage. Fix: write one sentence for each stage describing exactly what must be true for a deal to move forward. If two reps would disagree on whether a deal qualifies, your exit criteria isn't specific enough.

Mistake 2: Automations that never stop. A follow-up sequence that keeps running after a prospect has already replied and booked a call is one of the fastest ways to kill a warm deal. Every automated sequence needs a goal event that stops it. Build this into every workflow before it goes live.

Mistake 3: Too many stages. Eight-stage pipelines where stages 4 and 5 are nearly identical kill rep adoption. If your reps aren't sure which stage a deal belongs in, they'll pick randomly - or stop updating the CRM entirely. Keep it to five or six stages with clear, distinct definitions.

Mistake 4: Workflows built around the exception, not the rule. Don't build elaborate branch logic for edge cases that happen twice a year. Build clean workflows for your main motion, then handle exceptions manually. Complex workflows are harder to maintain, harder to troubleshoot, and more likely to have unintended consequences. Start simple, add complexity gradually.

Mistake 5: Data that doesn't match workflow conditions. Your routing condition says "if industry = SaaS, route to enterprise rep" - but half your leads have a blank industry field. The condition never fires. Audit your required fields and make sure the data your conditions depend on is actually populated before you trust the automation.

Mistake 6: No one owns the workflow. Automation doesn't manage itself. Workflows break when integrations update, field names change, or team members get reassigned. Someone needs to own each workflow, review it periodically, and catch problems before they silently kill pipeline.

What Tool Should You Use?

For most B2B outbound teams and agencies, I recommend Close CRM. It has built-in calling, email, and SMS - meaning you're not duct-taping five tools together just to log a conversation. The workflow automation is solid for the price, and the learning curve is shorter than HubSpot or Salesforce.

If you're running a larger team with more complex RevOps needs, Monday CRM gives you more visual flexibility and no-code automation that non-technical managers can configure without IT help. You can set up rules like "when deal stage changes to X, notify Y and create action item Z" in minutes, not days of IT work.

HubSpot is worth considering if you're running a hybrid marketing-and-sales motion where you want lead nurturing, email campaigns, and pipeline management under one roof. The free CRM tier is genuinely functional for small teams, though you'll need a paid tier to unlock meaningful automation.

Pipedrive is a solid mid-market option if your team is under 15 reps and you want something simpler than Salesforce without sacrificing automation capability.

If you're running prospecting alongside your CRM workflow and need to enrich records with technographic data - for example, flagging leads based on what software stack they use - you can pull that data with a BuiltWith scraper and use it as a segmentation condition inside your CRM workflows.

The tool matters less than the structure. A well-built workflow in a basic CRM will outperform a poorly configured workflow in an enterprise platform every single time.

Connecting Your CRM to the Rest of Your Stack

A CRM workflow doesn't live in isolation. It plugs into your email sequencer, your calendar tool, your contract software, and your reporting layer. The connections between tools are where most workflows break down.

Here's how I wire the cold outbound workflow (Example 1) across the stack:

• Lead sourcing: Pull contacts from a B2B database or scraper. Validate emails. Export as CSV.
• CRM import: Import contacts into Close or your CRM of choice. Map fields correctly - first name, last name, company, title, email, phone.
• Sequence enrollment: CRM triggers enrollment in Smartlead or Instantly via integration or Zapier webhook. The sequence runs outside the CRM, but reply events sync back in.
• Reply detection: When a prospect replies, the sequence tool marks the contact as replied and updates the CRM record via integration. Deal moves to "Engaged" stage automatically.
• Call task creation: Stage change triggers a task for the rep to call within 24 hours. Rep logs call outcome directly in CRM.
• Proposal workflow: Call logged as positive triggers proposal task. Proposal sent and logged. Follow-up workflow starts. Stops when prospect responds.
• Contract: Verbal yes triggers contract creation task. DocuSign link sent. Signed contract triggers closed-won status and onboarding sequence.

Every handoff between tools is a potential failure point. Automation works well only when tools share the same customer data. When a buyer books time through a scheduler, the meeting should appear in the CRM without manual steps. Without tight links, you end up with slow updates and confused routing. Test every integration before you rely on it.

For data enrichment mid-workflow - when you want to find a direct email for a prospect who only has a LinkedIn profile, for example - find their email here and add it to the record manually or via an enrichment tool before the next step fires.

How to Audit Your Current CRM Workflow

If you already have a CRM set up, here's a fast audit to run this week:

• Pull every deal that's been in the same stage for more than 30 days. Those are stalled - either advance them or mark them lost. Letting them sit inflates your pipeline and destroys forecast accuracy.
• Check whether every stage has a defined exit criterion. If you can't write it in one sentence, it doesn't have one.
• Look at your loss reasons. If you have none logged, you're flying blind. Add a required "loss reason" field to your Closed Lost stage today.
• Check stage conversion rates. If you're losing 60% of deals between Proposal and Decision, that's not a closing problem - it's a qualification problem upstream.

For tracking all of this without building a custom dashboard from scratch, I have a free Sales KPIs Tracker that covers stage conversion, deal velocity, pipeline coverage, and close rate in one sheet.

Final Thought: Your CRM Should Do Work, Not Just Store It

A CRM workflow is only valuable when it's moving deals forward automatically, surfacing problems before they kill revenue, and giving you visibility into exactly where your funnel is breaking. If your CRM is just a contact database, you're using it wrong.

The goal of CRM workflow automation isn't automation for its own sake. It's enabling your team to be more effective, your data to be more reliable, and your customer interactions to be more timely and relevant. Keep that goal in focus, and the tactical decisions about what to automate and how become much clearer.

Pick one of the five workflow examples above. Add exit criteria to every stage. Set up at least one automated action per stage. Run the audit. You'll see your pipeline clarity improve within days.

Need the full cold email tech stack that plugs into your CRM? Grab the Cold Email Tech Stack guide - it covers every tool from list building to sequencing to CRM integration.