IIIOrganization & Project ManagementGuide

Visualize Your Sales Process: The Whole Sales Workflow on One Page

As long as the sales process exists only in people's heads, everyone sells differently. A single page is enough to make it visible and open to discussion.

Notebook, reading glasses, fountain pen and small items on dark wood
Photo: Mick Haupt / Unsplash

Key takeaways

  • A sales process that is not written down anywhere can be neither improved nor handed over.
  • The one page needs six entries per stage: stage, trigger, owner, result, deadline, and handoff.
  • You draw the workflow as it really ran in recent cases, but only in as much detail as the improvement requires.
  • Only the finished map shows which software you need and which you do not.

Why should you map your sales process?

Ask three people in your company what happens after a new inquiry comes in. You will probably get three different answers. Each one is correct for the person giving it. That is exactly the problem: the workflow exists in several versions, and none of them has been agreed on.

As long as that is the case, three things are hard to do. You cannot say where inquiries get lost. You cannot train anyone without sitting next to them for weeks. And you cannot choose software, because nobody knows which workflow it is supposed to represent. The article on process before tool explains why this order matters: workflow first, tool second.

Visualizing a sales process means drawing the steps from the first inquiry to the order in such a way that everyone involved sees the same picture. You need no modeling language and no drawing program for that. One page is enough. The central question, then: how do you get your sales process onto one page so that everyone shares the same picture and works with it? To answer it, we first clarify what belongs on the page, then map the workflow in 60 minutes, compare the common formats, and finally turn to typical mistakes and the use of the map in daily work.

Whatever is not on one page gets sold differently in every head.

The same company, once without and once with a mapped sales process

Process in people's heads

  • Every salesperson follows their own sequence
  • Nobody knows how many quotes are currently open
  • Onboarding happens by watching and asking
  • Discussions revolve around individual cases

Process on one page

  • Everyone uses the same stages and the same terms
  • Every sales opportunity can be assigned to a stage
  • New colleagues receive the map on day one
  • Discussions revolve around the stage where things get stuck

What belongs on the one page?

Most process drawings fail because of too much detail. If you draw every exception, you end up with a poster nobody reads. For sales in a small or mid-sized company, five to seven stages and six entries per stage are sufficient. This grid is called the six-column map here.

  • Stage: a name everyone in the company uses the same way, such as “need clarified.”
  • Trigger: the event that starts the stage, such as “inquiry arrives.”
  • Owner: exactly one person or role, not a department.
  • Result: how you can tell that the stage is complete.
  • Deadline: the maximum time the stage may take.
  • Handoff: what is passed on to whom, and in what form.
Template: six-column map of an example company with a quote-based business
StageTriggerOwnerResultDeadlineHandoff
Inquiry recordedCall, form, or emailOfficeContact and request notedsame dayAppointment in the sales calendar
Need clarifiedFirst-meeting appointmentSalesScope, budget range, and decision-maker known3 business daysMeeting notes to costing
Quote sentComplete meeting notesCostingQuote is with the customer3 business daysFollow-up date to sales
Quote followed upFollow-up date reachedSalesYes, no, or next appointment5 business days after sendingDecision entered in the list
Order handed overWritten confirmationSalesOrder created with all details1 business dayHandover sheet to fulfillment

Worked example

How do you map the sales process in 60 minutes?

The most important principle: you draw the workflow of the most recent real cases. If you start with the ideal workflow, you draw a declaration of intent. Improvement comes afterwards, and it is a separate step. The current-state map does not have to be complete for that. One hour is enough, because it only provides the basis for the future workflow.

  1. Select cases

    Take five sales opportunities from recent weeks, including won, lost, and still open ones. Real cases keep everyone from describing the ideal scenario.

  2. Get everyone to the table

    Bring in everyone who handled one of these cases: office, sales, costing, fulfillment. One person alone only knows their own section.

  3. Name the stages

    Go through the cases one by one and write each step on a card. Then merge them until five to seven stages remain.

  4. Fill in the six columns

    Enter trigger, owner, result, deadline, and handoff for each stage. Wherever the group cannot agree, mark the field.

  5. Assign the cases

    Finally, assign all open sales opportunities to a stage. Anything that cannot be assigned points to a gap in the map.

A case study from Sweden describes how such a mapping exercise unfolds in a small company. For two and a half years, Aggestam and Gudfinnsson (2024) accompanied a manufacturer of screening equipment with around 25 employees that builds every machine to order and to the customer's specification. They conducted nine in-depth interviews and held eight workshops. It began with a session of about two hours in which the management team sketched the workflow on a whiteboard. The participants were surprised themselves, because by their own account earlier attempts had always gotten stuck. The most important insight of that session: the customer of the sales process is the company's own production. If a detail is missing from the inquiry, it costs hours on the shop floor later.

There, the map turned into fixed rules. The salespeople classify every inquiry by a traffic-light principle, green for the familiar and red for special cases with open questions, and go through a checklist before the daily meeting. The process picture hangs in the meeting room together with the agenda. Production counted how often details were missing before and after the change. According to the authors, that number dropped markedly, though they give no exact figures. Two of their lessons concern you directly. Management has to introduce the project itself and treat it as its own problem. And the current state is examined only as far as the future workflow requires. In the case company, a version that the company itself called good enough was sufficient. It remains a single case accompanied by researchers, and it cannot be generalized.

Which format fits: list, swimlanes, or funnel?

There are several common ways to draw a workflow. None is better in principle. They answer different questions, and for a start the simplest one is usually the right one.

Four ways of depicting the sales process compared
FormatMainly showsSuitable whenEffort
Table with six columnsRules per stageyou are mapping for the first timelow
Swimlane diagramHandoffs between peoplemany roles are involvedmedium
FunnelVolumes per stageyou want to see where inquiries get lostlow once numbers are available
Value stream mapWorking time and idle timelead time is the problemhigher, requires measurement

The value stream map comes from lean management, a school of thought that aims to free workflows of waste. A case study from Finland describes how it is used in order processing: Kääriä and Shamsuzzoha (2024) analyzed the workflow from order to incoming payment at a company in the energy and environment sector in a workshop using such a map. It became visible that a great deal of manual work was connected to incomplete or incorrect data in pricing and invoicing, which led to canceled invoices.

Small companies use such aids less often than large ones. A survey of managers from 433 manufacturing enterprises in the Czech Republic (Pech and Jelínková, 2025) concludes that large enterprises have an advantage when it comes to systematically applying more demanding principles such as standardization and visualization. The respondents rated 26 principles for this purpose. Across all company sizes, the ones applied most often were respect for employees, customer orientation, personal responsibility, and workplace safety. At the same time, the authors point to simplified toolkits for smaller companies, which include making workflows visible and mapping them precisely because that is feasible on a small scale. For you this means: start with the table. It is the format that works without training.

What does the map show that you did not see before?

Once every open sales opportunity is assigned to a stage, you can count. The map turns into a funnel, and the funnel shows at which stage most cases get stuck. The article on sales metrics for small and mid-sized companies explains which numbers can be derived from that.

The map becomes a funnel: cases per stage in one quarter
  1. 120Inquiries recorded
  2. 85Need clarified71% of previous stage
  3. 70Quote sent82% of previous stage
  4. 30Quote followed up43% of previous stage
  5. 18Order60% of previous stage

Worked example: between quotes sent and quotes followed up, 40 of 70 cases are lost. This stage also has the least clear ownership on the map.

The second analysis concerns time. For the five cases you examined, compare the agreed deadline per stage with the actual duration. The deviation shows where a rule exists only on paper.

Agreed deadline versus actual duration: overrun per stage
  • Inquiry recorded0 days
  • Need clarified2 days
  • Quote sent4 days
  • Quote followed up9 days
  • Order handed over1 days

Worked example: the numbers show by how many days the agreed deadline was exceeded on average across the five cases.

In the example, both pictures point to the same spot. That is often the case: where volume collapses, time usually runs away as well. The bottleneck analysis for sales describes how to proceed systematically from there.

Which mistakes happen most often when visualizing?

  • The ideal workflow gets drawn. The map looks good but describes a company that does not exist.
  • Stages describe activities instead of results. “Making calls” is an activity. “Need clarified” is a state you can verify.
  • The map ends at the quote. Following up and the handoff to fulfillment belong on it, otherwise the two stages where most is lost are missing.
  • The customer's view is missing. Every stage comes with the question of what the customer experiences during this time and what they are waiting for.
  • The map is filed away after the workshop. It belongs in the weekly sales meeting, not in a folder.
  • Mapping the current state becomes an end in itself. If you spend weeks refining today's picture, you never arrive at the future workflow. Aggestam and Gudfinnsson (2024) advise turning to the target state early.

For the fourth point, the literature offers a fitting aid: the customer journey map, a map of touchpoints from the customer's perspective. Dubnytskyi and colleagues (2025) propose such a model for an online wholesaler in a conceptual paper, with the aim of improving the sales funnel. You do not have to draw a second map for that. An additional row below your table with the heading “What does the customer experience?” serves the same purpose.

How does the map become a tool for everyday work?

A map changes nothing as long as it only hangs on the wall. It takes effect once open sales opportunities are discussed every week by stage. At first, a shared list with one column for the stage and one for the next date is enough. The article on pipeline management in small and mid-sized companies explains how to turn that into a reliable revenue forecast.

Only once the list has held up for a few weeks is it worth asking about software. The stages on your map then become the stages in the system, and the “owner” and “deadline” columns become mandatory fields. The guide to introducing a CRM covers the steps involved. The interface at the start of the map, meaning the question of when an inquiry moves from marketing to sales, is the subject of the article on the lead handoff from marketing to sales.

An example from research shows that workflows can be made visible with lean means. In a small Italian company that maintains industrial valves, the flow of work was recorded over two weeks using radio tags (Castruccio Castracani and colleagues, 2026). From this, the sequence of steps and the throughput times could be reconstructed. The authors see this as evidence that lightweight process mapping is feasible in small companies too. For sales you need no radio tags. The data usually already sits in the inbox and the calendar.

The next step

  1. Pick out five sales opportunities from recent weeks: won, lost, and open.
  2. Invite everyone involved for 60 minutes and bring a blank sheet with six columns.
  3. Draw the workflow as it was in these five cases and mark every field you cannot agree on.
  4. Assign all open sales opportunities to a stage and count how many sit at each stage.
  5. Settle one marked field bindingly and discuss the map for ten minutes every week from now on.

After this hour you will not have a finished solution, but you will have a shared picture. Everything else, from optimizing the sales process to choosing a system, builds on it.

The question posed at the start can be answered as follows: the sales process gets onto one page when the people involved jointly map the workflow of the last real cases, not the desired one, and mark every disputed point. The map becomes a tool only when all open sales opportunities are assigned to a stage and the team reviews it briefly every week. The drawing itself is quickly done, and it gains its value through regular use.

Frequently asked questions

What does it mean to visualize a sales process?

It means drawing the stages from inquiry to order so that everyone involved has the same picture. Each stage comes with a trigger, an owner, a result, a deadline, and a handoff. One page is enough for that.

How many stages should a sales process have?

For small and mid-sized companies, five to seven stages are a good guideline. Fewer stages hide where things get stuck. More stages are not maintained properly in day-to-day work.

Which program do I need to map the sales process?

None for the first version. A sheet of paper, a whiteboard, or a simple spreadsheet will do. A drawing program is only worthwhile once the content of the map is settled and you want to pass it on in a clean form.

What is the difference between a sales process and a sales funnel?

The sales process describes the stages and rules, meaning who does what by when. The sales funnel shows the volumes per stage. The funnel emerges as soon as you assign cases to the stages of the process and count them.

How often should the process map be revised?

Discuss it briefly every week using the open cases, and revise it as soon as a stage regularly does not fit. A fixed date every three to six months keeps the map from going out of date.

Sources

  1. Aggestam, L.; Gudfinnsson, K. (2024): The Practice of Business Process Modeling: A Story from the Field. Complex Systems Informatics and Modeling Quarterly, no. 41, pp. 1-21.
  2. Kääriä, E.; Shamsuzzoha, A. (2024): Improvement of an order-to-cash business process by deploying lean six sigma tools: a case study. International Journal of Productivity and Performance Management, 73(11), pp. 161-189.
  3. Pech, M.; Jelínková, E. (2025): Adoption of Lean Management Principles in Small, Medium-Sized and Large Manufacturing Enterprises. Quality Innovation Prosperity, 29(3), pp. 1-17.
  4. Dubnytskyi, V.; Polous, O.; Radchenko, H. et al. (2025): Comprehensive Characteristics of the Sales Funnel Levels Transformation under the Influence of Digital Trends in the Marketing Sphere. Management Theory & Studies for Rural Business & Infrastructure Development.
  5. Castruccio Castracani, A. V.; Chiacchio, F.; D'Urso, D. et al. (2026): Process Discovery in Industrial Valve Maintenance Using NFC Technology: A Scalable Business Process Mapping Approach for SMEs. Procedia Computer Science, 277, pp. 366-375.

All sources in the knowledge base

Reading room of a historic library with galleries, walls of books, and a skylight

Found a mistake or a topic that’s missing?

Feedback, corrections, and topic ideas go straight to the editorial team. We correct openly and with a date.