The CRM Prospecting Workflow: Complete Guide (2026)

Walk into any sales floor in 2026 and you will hear the same complaint. The CRM is full of dead leads. Nobody trusts the data. Reps quietly maintain spreadsheets on the side because the official record is too polluted to act on. Marketing imports thousands of contacts a quarter, and inside ninety days half of them are stale, mis-routed, or duplicated three times across different owners. The pipeline numbers in the Monday meeting do not match what the closers actually believe is real. None of this is a tooling problem. It is a CRM prospecting workflow problem, and fixing it is the single highest-leverage thing a revenue team can do this year.

A CRM prospecting workflow is the end-to-end sequence that turns a name on a list into a closed-won deal without losing data, ownership, or context along the way. It begins long before the lead enters the system and only ends when the opportunity is closed and the record is archived. The teams that get this right are not the ones with the most expensive stack. They are the ones who treat list quality, deduplication, routing, and hygiene as deliberate stages rather than afterthoughts. This guide walks through every stage in detail, with examples from HubSpot, Pipedrive, Close, Salesforce, Attio, and Folk, and shows where MapsLeads fits as the cleanest top-of-funnel for local-business prospecting.

The 5 stages of a healthy CRM prospecting workflow

Almost every functional revenue motion can be broken down into the same five stages. The names vary by company, but the underlying steps do not. If any one of these stages is skipped or done casually, the downstream stages break.

Stage 1 — list build

The list-build stage is where you decide who you are going to talk to. Concretely, this means defining an ICP, choosing one or more sources, running queries, and producing a raw file of candidate accounts and contacts. For local-business outbound, this is typically a query-by-city motion. For mid-market and enterprise, it is firmographic and technographic filtering. The deliverable is a structured file, not a CRM record. Importing too early at this stage is the single most common mistake teams make, because anything you put in the CRM is something you will eventually have to clean.

Stage 2 — enrich and dedup before import

Once you have a list, you enrich it with the fields your sequences need (verified email, direct dial, role, company size, recent signals) and you deduplicate it against itself and against your existing CRM. Deduplication has to happen before the records cross into the CRM, because once they are in, the merge tools available in HubSpot, Pipedrive, and Salesforce are slow, partial, and dangerous. A clean list at this stage is the difference between a sales floor that trusts the data and one that does not.

Stage 3 — assign and route

When the list lands in the CRM it has to be routed. Round-robin by AE, territory by zip or country, ICP-tier by company size, vertical by industry — every team has its own rules, and the rules need to be encoded in the CRM, not held in a spreadsheet that one rev-ops person updates on Friday. Bad routing produces two equally bad outcomes: hot leads sit unassigned for days, or they get assigned to the wrong person and the right person never sees them.

Stage 4 — sequence and log activity

This is the stage most teams think of as "prospecting": the actual sending of emails, the dialing of phones, the LinkedIn touches. The crucial point is that all activity should be logged inside the CRM, not in a parallel sequencing tool whose data only syncs back partially. If you cannot answer the question "what was the last touch on this account, by whom, and when" by looking at the CRM, the workflow is broken.

Stage 5 — pipeline review and cleanup

Every week the manager reviews the pipeline. Every quarter the team runs a cleanup pass — disqualified records archived, stale opportunities closed-lost, decayed contact data refreshed or suppressed. Without this stage, the CRM accumulates entropy and the data trust problem from the opening of this article re-emerges within six months.

Choosing the right CRM for outbound

Choice of CRM has more inertia than any other tool decision a revenue team makes, so it is worth doing carefully. There is no universal winner. The right answer depends on team size, deal complexity, motion (inbound vs outbound vs hybrid), and whether you have a dedicated rev-ops function.

HubSpot is the default choice for marketing-led companies and for teams under fifty reps. Its Sequences product is mature, its workflow builder is the most accessible on the market, and the marketing-sales handoff is tight. The weakness is that for true outbound-heavy motions HubSpot Sequences feels lightweight compared to dedicated tools, and the Enterprise tiers get expensive fast once you need custom objects and advanced routing.

Pipedrive is the workhorse for outbound-heavy SMB sales teams. The pipeline view is the cleanest in the category, Smart Docs and Cadence cover most sequencing needs, and the price point is approachable for teams in the five-to-thirty rep range. The weakness is reporting depth and the limits of the workflow automation engine when you start needing complex branching.

Close is purpose-built for outbound. The built-in dialer and SMS, the native sequences, and the lean record model make it the fastest CRM for a rep to live in all day. It is the right choice for high-volume outbound shops, particularly in local-services and SMB-targeting motions. The weakness is that it is less suited to complex enterprise deals with many stakeholders.

Salesforce remains the standard for mid-market and enterprise. Nothing else handles complex territories, custom objects, deal-desk approvals, and the sheer volume of integrations. The weakness is well known: high cost, heavy admin overhead, and a steep learning curve. If you do not have a dedicated rev-ops admin, Salesforce will fight you.

Attio is the modern challenger, built around the idea that a CRM should feel like Notion or Linear. The data model is flexible, the UI is fast, and it suits product-led and modern B2B SaaS teams who find Salesforce and HubSpot heavy. The weakness is that the sequencing and dialer surfaces are still maturing, so most Attio teams pair it with an external sender.

Folk is the lightest of the group. It works very well for founder-led sales and small agencies who want a CRM that feels like a contact book with pipelines stapled on. The weakness is that once a team grows past ten reps, Folk runs out of room.

The pragmatic guidance: under twenty reps and inbound-heavy, HubSpot. Under thirty reps and outbound-heavy SMB, Pipedrive or Close. Modern B2B SaaS that wants a fast UI, Attio. Mid-market and up, Salesforce. Founder-led or agency, Folk. None of these choices fixes a broken workflow on its own.

The list-building stage (where most workflows fail)

If you remember one thing from this guide, remember this: the CRM is a downstream system. Whatever you put in it sets the upper bound on the quality of everything that happens afterwards. A dirty list does not get cleaner by being imported. It gets worse, because now it is mixed in with your existing records, sequenced against, and emailed to. By the time you discover the problem, you have burned domain reputation, annoyed real prospects, and added work for the rev-ops team that has to clean it up.

The most common failure modes at this stage are: scraping a list from a free tool with no verification, buying a list from a broker without sample-checking, and building a list manually in a spreadsheet that nobody dedupes. All three produce CRMs full of dead leads.

For local-business prospecting specifically — agencies selling websites, SEO, ads, software, equipment, supplies, or services to plumbers, restaurants, dentists, gyms, salons, contractors, retailers — the cleanest top-of-funnel is to source directly from Google Maps. Maps is the canonical record of which businesses actually exist in a given city, with a verified address, a current phone number, real reviews, and an active business owner. The data is fresher than any broker file and richer than any free scraper output.

This is exactly what MapsLeads is built for. You open Search, type a query like "plumbers Manchester" or "italian restaurants Lyon", apply filters by rating, by review count, by category, by whether the business has a website, and you get back a clean list of candidate accounts. You enable the Contact Pro module to add verified emails. You enable the Reputation module to bring in review counts and recent-review signals. You group the results, dedup against an existing CRM export, and export to CSV, Excel, or Google Sheets ready for import. The list is structured and predictable, the credit cost is transparent, and you never wonder whether a record is two years old.

The wider lesson is the same regardless of source: do the list-build stage outside the CRM, get it clean, and only then bring it across. The teams that follow this rule have CRMs that are easy to live in. The teams that do not, do not.

Enrich and dedup BEFORE the CRM (not after)

Deduplication inside a CRM is a damage-control activity. Deduplication before import is a quality activity. The two cost vastly different amounts of effort and produce vastly different results.

The first step is choosing match keys. The three useful ones in B2B are domain, primary email, and primary phone. Company name is too noisy to match on directly because of suffixes, formatting, and typos. Address is useful for local businesses but needs normalisation. A defensible default for local-business prospecting is: match on domain first, then on primary phone, then on normalised address.

The second step is choosing a merge rule. When two records match, which fields win? The simplest rule is "most recent wins for changeable fields, longest-string wins for descriptive fields, and the existing CRM record always wins for ownership and stage". Encode this rule explicitly. Otherwise different reps will merge differently and the data will drift.

The third step is choosing a keep-or-drop rule for near-matches. Two records with the same domain but different phones almost always represent multi-location businesses and should be kept separate, linked by a parent-child relationship. Two records with the same phone but different domains usually represent one business with a stale website and should be merged.

MapsLeads has dedup built into the Search and group workflow. Before you export, you can dedup the working set against itself and against an uploaded CRM export. The dedup runs on the canonical Maps identifiers, which are far more reliable than name-matching. The output is a clean, non-overlapping list ready for CRM import.

The savings here compound. Every duplicate prevented at the import stage is a duplicate that does not get sequenced twice, does not waste a credit on a sender, does not produce two conflicting deal records, and does not require a quarterly cleanup pass to find. The math is overwhelming once you run it for a quarter.

Field mapping and lead routing

Field mapping is unglamorous and load-bearing. The list you import has columns. The CRM has fields. Every column has to map to a field, and every required CRM field has to receive a value, or the import will either fail or silently drop data.

A defensible default mapping for local-business prospecting:

• Business name to Company Name
• Website domain to Company Domain
• Primary phone to Company Phone
• Address, city, postcode, country to the relevant Company address fields
• Category to Industry
• Verified email (from Contact Pro) to Primary Contact Email on a new Contact record linked to the Company
• Review count and average rating (from Reputation) to custom Company fields
• Source to a custom field set to "MapsLeads" so you can attribute pipeline back to the channel

Lead routing then runs on top of the mapped fields. The three common routing models:

Round-robin assigns each new lead to the next AE in a rotation. This works well for inbound marketing leads where every AE has the same ICP. It works badly for outbound where reps own territories.

Territory routing assigns leads by geography (country, region, zip range) or by named-account list. This is the standard for mid-market and enterprise. The discipline required is keeping the territory definitions current — a quarterly review is the minimum.

ICP-tier routing assigns leads by fit score. Tier 1 accounts go to senior AEs, Tier 2 to mid AEs, Tier 3 to BDR-led motion. This is the most common model for outbound-heavy SaaS.

In practice most teams combine two of these. A reasonable composite rule for a local-business outbound team: route by city or zip range first, then by fit tier (rating, review count, category match) within that territory. Encode the rule in the CRM workflow builder so that a lead lands on the right rep within minutes of import, not days.

Sequencing from inside the CRM

Once leads are routed, they get sequenced. The choice here is between native CRM sequencing and a connected outbound tool.

HubSpot Sequences are native to HubSpot Sales Hub, support email and task steps, and log activity directly to the contact and company records. They are the right choice for HubSpot teams up to mid-market, particularly when the marketing-sales handoff matters and you want one tool of record.

Pipedrive Cadence and Smart Docs cover the same ground for Pipedrive teams. The cadence builder is straightforward and the activity logging is clean. For SMB outbound this is more than enough.

Close has a built-in power dialer, SMS, and email sequencing in one product. For high-volume outbound shops where reps live in the dialer, this is the most efficient setup on the market. There is no separate tool to sync.

Outreach and Salesloft are the dedicated outbound platforms that pair with Salesforce and HubSpot. They offer deeper sequence logic, better deliverability tooling, and more sophisticated reporting. The cost is the integration: keeping activity, ownership, and stage in sync between Outreach and Salesforce is a project, not a checkbox.

Apollo embedded combines a database, sequencing, and dialer in one product. It is popular with venture-backed B2B SaaS teams that want one bill and one UI. The trade-off is that you are now coupled to one vendor for both data and execution.

The principle that ties all of these together: every send, every dial, every reply must end up logged on the CRM record. If a rep can answer "what was the last touch" only by checking a sequencing tool that the manager does not have open, the workflow has a hole in it.

How to do this end-to-end with MapsLeads

Here is the complete loop for a local-business outbound team using MapsLeads as the top-of-funnel.

Open Search and type a query. Take "plumbers Manchester" as the running example. MapsLeads pulls the candidate set from Google Maps and presents it in a results table. Apply filters: rating greater than or equal to 4.2, review count greater than 25, category exactly Plumber, has-website true. The working set narrows to the businesses that match the ICP.

Enable the Contact Pro module on the working set. This adds verified emails to each record at a cost of one additional credit per lead. Enable the Reputation module to bring in review counts and recent-review keyword signals at a cost of one additional credit per lead. If you want photos for the outbound personalisation, enable the Photos module at a cost of two additional credits per lead. The credits callout: one credit per Base lead, plus one for Contact Pro, plus one for Reputation, plus two for Photos. Credits are drawn from your wallet and visible on the billing page.

Save the working set as a group. Groups are the unit of organisation inside MapsLeads, and they are what you export, dedup, and re-run. Upload your existing CRM export as a comparison set, run dedup against the group, and the overlap is removed. The remaining records are net-new accounts you have never touched.

Export the group to CSV, Excel, or Google Sheets. The export includes every field you enabled — base firmographics, verified email from Contact Pro, review signals from Reputation, photos from Photos — in a column structure that matches a standard CRM import. Import into HubSpot, Pipedrive, Close, Salesforce, Attio, or Folk using the prebuilt field mapping above. The records land routed, owned, and ready to sequence.

The whole loop is short by design. Open Search → export → import → sequence.

CRM data hygiene rituals

A clean CRM does not stay clean by accident. It stays clean because the team runs deliberate rituals on a deliberate cadence.

Quarterly cleanup is the foundation. Every quarter, run a pass on the CRM that does four things: archive contacts with no activity in the last twelve months, close-lost opportunities with no activity in the last sixty days, refresh contact data on the top tier of accounts, and rotate ownership on accounts whose owner has left or changed roles.

Decay handling is continuous. Email addresses go stale at roughly thirty percent per year for B2B contacts. Phone numbers decay slower. Domains move slower still. Build a rule that flags any contact record that has not been touched in six months as needing re-verification before it is sequenced again.

Suppression hygiene is non-negotiable. Anyone who has unsubscribed, anyone who has bounced hard, anyone who has marked a previous send as spam, anyone who has explicitly asked not to be contacted — these go on a suppression list, and the suppression list is checked at import time and at sequence-launch time. The cost of getting this wrong is domain reputation, which takes months to recover.

Owner-rotation rules close the loop. When a rep leaves, accounts must be reassigned within seven days. When a rep changes territory, their old book must be split between the new owners on a documented schedule. Without an explicit rule, accounts get orphaned and silently rot.

These rituals are boring. They are also the difference between a CRM that the team trusts and a CRM that the team works around with spreadsheets.

KPIs to track at every stage

Measurement is what tells you which stage of the workflow is leaking. The minimum set of metrics:

| Stage | Metric | Sensible target | | --- | --- | --- | | List build | Records sourced per period | Set by capacity | | Enrich and dedup | Duplicate rate at import | Under 2 percent | | Routing | Time to first touch from import | Under 24 hours | | Sequencing | Lead to MQL conversion | 8 to 15 percent | | Sequencing | MQL to SQL conversion | 25 to 40 percent | | Sequencing | SQL to Opportunity conversion | 40 to 60 percent | | Pipeline | Opportunity to Closed-Won conversion | 20 to 35 percent | | Pipeline | Cost per booked meeting | Track quarterly | | Pipeline | Pipeline velocity (days from create to close) | Track quarterly |

The numbers in the right column are not universal. They are sensible starting targets for B2B SMB outbound. Your business may run higher or lower. The point is to measure each stage separately so that when total pipeline misses, you know which stage to fix.

The two metrics that matter most for sales leadership are cost per booked meeting and pipeline velocity. Cost per booked meeting tells you whether the top-of-funnel is economic. Pipeline velocity tells you whether the middle of the funnel is healthy. Both are downstream of list quality.

CRM prospecting workflow checklist

Use this as a quarterly self-audit. Every item should be answerable with a yes.

• The ICP is documented in writing and the document was reviewed in the last six months.
• Every list source we use has a named owner and a defined refresh cadence.
• We dedup every list against the existing CRM before import, not after.
• Field mapping is documented and the same for every importer on the team.
• Lead routing rules are encoded in the CRM workflow builder, not in a spreadsheet.
• Time from import to first touch is under twenty-four hours for at least 90 percent of leads.
• Every send, dial, and reply is logged on the CRM record.
• Suppression list is checked at import and at sequence-launch.
• Bounce rate on outbound email sends is under three percent.
• Quarterly cleanup pass is scheduled on the calendar, with a named owner.
• Owner-rotation rule is documented and triggered automatically when reps leave.
• Lead-to-MQL, MQL-to-SQL, and SQL-to-Opp conversion rates are tracked weekly.
• Cost per booked meeting is tracked monthly, by source.
• Pipeline velocity is tracked monthly, by stage.
• The CRM is the source of truth and no rep maintains a side spreadsheet for active accounts.

FAQ

What is the best CRM for outbound prospecting?

There is no single best CRM. For outbound-heavy SMB teams under thirty reps, Close and Pipedrive are the strongest choices because they put the dialer and the cadence in the same UI. For mixed inbound and outbound under fifty reps, HubSpot is the safest pick because the marketing-sales handoff is tightest. For mid-market and enterprise with complex territories, Salesforce remains the standard. Modern B2B SaaS teams that prioritise UI speed often pick Attio. Founder-led teams and small agencies do well on Folk. The CRM does not fix a broken workflow — pick the one that fits your motion and team size, then invest in the workflow.

How do I import Google Maps leads into HubSpot?

Source the leads cleanly first. In MapsLeads, open Search, run your query, apply rating and review filters, enable the Contact Pro module for verified emails, save the working set as a group, dedup against an existing HubSpot export, and export to CSV. In HubSpot, use the import wizard to map your CSV columns to Company and Contact fields. Map business name to Company Name, website to Domain, phone to Company Phone, verified email to Contact Email, and set a custom Source field to "MapsLeads" for attribution. Import as a draft list first, sample-check ten records, then commit the import.

Should I dedupe before or after CRM import?

Before, always. Deduplication inside a CRM is slow, partial, and risky — merges can lose ownership history, conflate stages, and overwrite recent activity. Deduplication on the source list before import is fast, reversible, and runs on canonical match keys (domain, primary phone, normalised address). MapsLeads has dedup built into the group workflow precisely so you can do this step before the records cross into the CRM.

How often should I clean my CRM?

Run a major cleanup quarterly and continuous decay handling on a rolling basis. The quarterly pass archives stale contacts, closes inactive opportunities, refreshes top-tier account data, and rotates ownership where reps have moved or left. Continuous decay handling flags contacts that have not been touched in six months for re-verification before they are sequenced again. Suppression hygiene runs at every import and every sequence launch. Skipping these rituals is the most common cause of the "nobody trusts the CRM" problem.

Is it legal to import Google Maps leads into a CRM?

For B2B outbound to publicly listed business contact details, in most jurisdictions, yes — but the rules vary by country and by use case. The fields published on Google Maps for business listings (name, address, phone, website) are public business information. Verified emails added through enrichment are subject to the email-marketing rules of the recipient's country, including GDPR in the EU and CAN-SPAM in the US. Always check suppression and unsubscribe handling, and document the legitimate-interest basis for B2B sends in markets that require it.

How do I avoid CRM bloat from outbound prospecting?

Three rules. First, never import a record you are not going to sequence in the next sixty days — staging records "just in case" is how CRMs accumulate dead weight. Second, archive any record that completes a full sequence with no reply within ninety days, rather than leaving it in the active pool. Third, track records-per-active-rep as a health metric; when it climbs faster than headcount, you have a bloat problem and need to tighten the ICP at the list-build stage.

Next steps

A working CRM prospecting workflow is not built in a day, but it is also not complicated. Pick the right CRM for your motion. Build clean lists outside the CRM. Dedup before import. Route deliberately. Sequence from inside the CRM. Run hygiene rituals quarterly. Measure every stage.

For the related deep-dives in this cluster, read the Google Maps leads to CRM workflow guide for the import-side mechanics, the build sales pipeline from Google Maps leads guide for the pipeline-construction side, and the how to clean and deduplicate lead lists guide for the dedup tactics in detail.

If you want to try the cleanest top-of-funnel for local-business prospecting, see pricing for the credit packs and plans, or get started and run your first city query in under five minutes. Open Search, export, import, sequence — and watch what a clean CRM feels like.