How to Map Your Existing Sales Process Before HubSpot Implementation

Key Takeaways

• Map your sales process before HubSpot implementation, since each pipeline, stage and required property you configure encodes a version of it.

• Document the process as it really runs by reviewing recent deals and interviewing reps, rather than copying the version in the sales deck.

• Define each stage by an observable entry and exit criterion, ideally a buyer action, so two reps would place a deal identically.

• Name an owner for each stage and handoff, since handoffs are where we see deals stall in the pipelines we audit.

• Check the finished map by replaying a sample of recently closed deals through it before anyone configures a pipeline in HubSpot.

 A HubSpot pipeline built from the official version of your sales process looks tidy at launch and then drifts away from what reps actually do. Mapping the real process first keeps the configuration honest.

Why should you map your sales process before HubSpot implementation?

You should map it first because HubSpot will record whatever process you configure, whether or not your team follows it. Pipelines, deal stages, required properties and ownership rules are a written description of how you sell. If that description is wrong, reps work around it, and the CRM fills with deals parked in stages that no longer mean anything.

In the implementations we run, the documented process and the real one differ in predictable places. Steps get added informally, such as a pricing approval or a security review. Stages listed in the deck get skipped. Handoffs happen in email or chat, where no system records them. None of this shows up until someone asks reps to walk through their last few deals.

A map also gives the implementation a reference point. When a stakeholder asks for a new stage or field, the team can check it against the agreed map instead of adding it because someone asked loudly.

What this means for you: treat the process map as the first deliverable of the implementation, finished and signed off before anyone opens the pipeline settings.

How do you map your sales process as it really runs?

You map it from evidence of recent deals rather than from memory of the intended process. Three sources give a reliable picture when used together.

Recent deals: pull a sample of deals closed in the last two quarters, both won and lost, and trace what happened from first contact to the final decision. Emails, call notes and calendar invites show which steps took place and in what order.

Rep interviews: ask each rep to describe their last two deals step by step. Ask what they did, not what the process says they should do, and note each step they mention that the documented process leaves out.

Handoff owners: speak to the people on the receiving end of each handoff, such as presales, legal, finance and onboarding. They know where deals arrive incomplete.

A before and after record shows what this evidence changes. Before mapping, a deal might read: stage Proposal, close date this month. Traced through emails and the rep's account, the same deal reads: pricing approval pending with finance, security questionnaire sent and unanswered. Neither step exists in the current CRM, so the forecast counts the deal as further along than it is.

Questions to ask: Which steps in our last ten deals did not appear in the documented process? Where did a deal wait for someone outside sales, and who was it waiting for?

What should a sales process map include before HubSpot implementation?

The map should include five elements for each stage: its name, an entry criterion, an exit criterion, an owner and the record that proves the criterion was met. The last element is what turns the map into a configuration brief.

Write entry and exit criteria as observable events. "Buyer confirmed budget holder in writing" is observable. "Deal feels qualified" is not. Where possible, make the criterion something the buyer did, because buyer actions are harder to inflate than seller opinions.

Map variants separately. New business, renewals and partner-sourced deals tend to follow different steps with different owners. Forcing them into one sequence produces stages that many deals skip.

At a glance: a process map template for a B2B sales team, with an example property for each stage. Custom properties are marked as such.

In the pipelines we audit, stages without an observable exit criterion collect deals that have stopped moving, which makes the forecast look healthier than the pipeline really is.

What this means for you: fill in this template with your own stages, and leave no cell vague. Where nobody can name the property that records a criterion, decide whether the criterion matters enough to track.

How do you turn a sales process map into a HubSpot setup?

You translate it element by element. Stages in the map become deal stages in a pipeline. Variants that follow different steps become separate pipelines, so renewals do not share stages with new business. Entry and exit criteria become properties, and owners become the deal owner or a property naming the handoff recipient.

HubSpot lets admins ask for specific properties when a deal moves into a stage, which is how an exit criterion becomes something the system asks for rather than something a manager chases. Use this for the criteria that matter most, since asking for too much at each stage slows reps down and invites placeholder values. Check how your own portal and subscription handle stage requirements before you design around them.

Handoffs deserve their own design. A handoff from account executive to presales or onboarding can create a task, notify the recipient or change a property, but the map decides which. If the map does not say who receives the deal and what they need, the configuration cannot say it either. Teams deciding whether to run this translation in house can compare the options in our guide to DIY versus partner-led HubSpot implementation.

What this means for you: keep a column in the map that records the HubSpot element each line becomes, so the configuration can be traced back to an agreed decision.

How do you check your sales process map before HubSpot implementation?

Check it by replaying real deals through it. A practical starting point is to take 20 recently closed deals and place each one in the mapped stages, using the entry and exit criteria as written.

Three results tell you whether the map is ready. Each deal should fit the stages without a step left over. Two people placing the same deal should put it in the same stage at the same point. Each handoff should have a named recipient for every deal in the sample. Where several deals fail the same test, revise the map rather than forcing the deals to fit.

Finish with sign-off from the sales leader and at least two reps who did not help write the map. Their agreement is the measure that matters, since they are the people who will use the pipeline each day.

Questions to ask: Did any deal in the sample need a step the map does not include? Would two of our reps place each sample deal in the same stage?

The Bottom Line

A pipeline can only be as accurate as the process description behind it. The description worth configuring comes from recent deals and rep interviews, with each stage defined by something the buyer did and each handoff given a named recipient. Replaying real deals through the map before setup finds its gaps while they are still cheap to fix.

The Markivis Approach

The sales leader and our consultant trace a set of recent won and lost deals together, before any pipeline exists. Rep interviews and conversations with the teams who receive handoffs follow, and the work ends with a map the sales leader signs off. The configuration brief comes from the map, line by line, as part of our HubSpot implementation services.

• Each pipeline stage traces back to an entry and exit criterion in the signed map.

• Stage requirements are limited to the criteria the sales leader names as essential.

• Variants such as renewals or partner deals get their own stages when the map shows they differ.

Demo conversions doubled during our work with Slimstock, as the Slimstock case study records. The engagement spanned HubSpot, CRM, lifecycle and demand generation, so the result belongs to the whole program rather than to any one mapping decision.

FAQ

Q: How do you map a sales process before HubSpot implementation?

A: Review a sample of recent won and lost deals, interview reps about their last deals, and speak to handoff owners. Then document each stage with entry and exit criteria, an owner and a recording property.

Q: How long does sales process mapping take?

A: For a single motion with one sales team, we would plan two to three weeks of deal reviews, interviews and revision. Each additional motion, such as renewals or partner deals, adds about a week.

Q: Who should be involved in mapping the sales process?

A: Include the sales leader, several reps with different tenure, and the people who receive handoffs, such as presales and onboarding. Marketing should join for the stages where leads become opportunities.

Q: Should we fix the sales process while we map it?

A: Document the current process first, then decide which changes to make. Mixing the two hides what reps do today, and that knowledge is what makes the new configuration fit.

Q: Do we need separate pipelines for different sales motions?

A: Use separate pipelines when motions follow different stages or owners, such as new business and renewals. If the stages match and only the deal source differs, a property is enough.

 

Q: What if reps disagree about how the process works?

A: Disagreement is useful evidence. Settle it with deal records rather than opinion, and where the variation is real, decide whether it is a separate motion or a step to standardize.

Q: Can we map the process inside HubSpot instead of on paper?

A: You can sketch stages in a test pipeline, but agree the map outside HubSpot first. A document is easier to review and sign off, and configuration changes are harder to unwind.

Ready to Map Your Sales Process?

A pipeline built on the real process gives your forecasts something solid to stand on. A pipeline built on the intended process gives reps a reason to work around the CRM.

We would take two of your recently closed deals and walk them stage by stage against your current CRM, marking each step the system did not record. The result is the first few rows of a process map before any configuration is discussed.

Book a Free Sales Process Mapping Call.

Last Updated: October 13, 2026