"Reconnaissance" or "scouting" is the absolute best analogy for the Pre-Discovery phase. If you just wander into the process forest without scouting it first, the business stakeholders will drag you deep into the weeds, and you will spend three weeks mapping how they order office supplies instead of fixing their quoting engine.
Before you interview a single sales rep, you sit with leadership to map out the high-level business capabilities. You are flying over the forest in a helicopter, identifying the boundaries of the forest, the major rivers, and the mountains. You are not mapping how they do it; you are just listing what they do to define the project perimeter.
Now that you have the map, you land the helicopter and walk the specific trails you outlined during the recce. This is where you document the "As-Is" pain points by mapping the literal steps and actors for each specific process.
You take the broken As-Is processes and redraw them to leverage the new technology (like Salesforce Revenue Cloud), ensuring the system handles the heavy lifting.
The Architect's Shield: The most powerful thing you can do as a consultant is control the scope. When a sales rep brings up a totally unrelated complaint during Discovery (e.g., "Our lead routing is broken!"), you pull out your Phase 1 map and say: "I hear you, but Lead Routing is outside our perimeter for this phase. Let's put it in the backlog."
We break down the business operations into three clear levels. Unlike traditional mapping that starts with a massive, generic "Quote-to-Cash" umbrella, we start directly with the strategic priorities finalized during the Executive Vision phase. This ensures every operational process we map is tethered to a top-level business goal.
| Hierarchy | What It Is | Example (From Vision Rubric) |
|---|---|---|
| Level 1 (L1) | Value Stream (The Priority): An executive priority translated into a measurable flow of business value. This comes directly from the finalized Vision Rubric. | Standardize Recurring Revenue Handoffs |
| Level 2 (L2) | Process Area: The major functional buckets required to deliver that L1 Value Stream. At this 10,000-foot view, the platform doesn't matter. | Order Management, Billing & Invoicing |
| Level 3 (L3) | Specific Process: The actual tasks to be accomplished. Knowing you are moving to Revenue Cloud changes your scouting here, as you target processes suited for native platform capabilities. | Subscription Proration, Asset Generation |
| L1: Value Stream (Vision Priority) | L2: Process Area | L3: Specific Process (The Recce Targets) |
|---|---|---|
| 1. Accelerate New Business Quoting | 1.0 Quoting & Configuration |
1.1 Opportunity to Quote Creation 1.2 Guided Selling / Needs Analysis 1.3 Product Selection & Configuration |
| 2.0 Pricing Strategy & Logic |
2.1 Base List Pricing Setup 2.2 Discount Matrices & Promotions |
|
| 2. Protect Commercial Margins | 3.0 Deal Desk & Governance |
3.1 Manual Discount Entry 3.2 Margin / Commercial Approval Routing 3.3 Cost-Plus / Margin Floor Calculations |
| 3. Standardize Recurring Revenue | 4.0 Order & Asset Management |
4.1 Quote-to-Order Conversion 4.2 Asset Creation & Registration 4.3 Subscription Proration & Co-Terming 4.4 Renewals & Amendments |
Human psychology is funny: if you ask a room full of department heads to draw their business processes on a whiteboard, you get blank faces and awkward silence. But if you put a slightly incorrect process map on the screen, they will immediately jump out of their chairs to tell you exactly why you are wrong and how they actually do it. This is the "Straw Man" approach.
You do not start with technology. You start by playing back the L1 priorities their executives mandated in the Vision Phase.
Project your pre-populated L2/L3 Process Breakdown on the screen and force binary decisions.
For every In-Scope L3 process, demand a name for your upcoming detailed interviews.
The Outcome: You walk out of this meeting with a locked scope, a clear Discovery Schedule, and business leads who feel confident because they simply had to edit your draft rather than stare at a blank page.
If you want to pre-fill your Process Breakdown before the Day 0 Workshop, you can attempt to harvest existing documentation. The golden rule is to never start with a blank page.
If you choose to ask the client for documents beforehand, use this template. It positions you as a partner trying to save them time, rather than a consultant assigning homework.