Supply Chain Consulting Scoping

Every successful project starts with a scope that’s sharp, shared, and strategic.

Scoping is the highest-leverage activity in a consulting engagement. It determines all downstream outcomes: proposal quality, team composition, delivery timeline, and whether the client gets what they actually need.

Two-Stage Scoping Process

Stage 1: RFP Development (Client Side)

The eight components of a well-structured consulting RFP or project brief:

A. Strategic Intent Ground the project in business context. What industry trends, internal shifts, or prior decisions necessitate this engagement? This prevents the consultant from treating it as a generic project.

B. Problem Framing Move beyond symptoms to root causes. Example:

• Weak: “Reduce costs”
• Strong: “Margin pressure in EMEA operations due to legacy contracts, requiring vendor consolidation assessment in 3 categories by Q3”

The more precisely the problem is framed, the better consultants can diagnose whether they’re the right fit.

C. Objectives — Business Level and Project Level Define what success looks like at two levels:

• Business-level: What decision will this work enable? What financial or operational outcome does it drive?
• Project-level: What must the project produce to achieve the business objective?

D. Scope Definition — In AND Out Explicitly state what is included AND excluded. The out-of-scope list is as important as the in-scope list.

Include	Exclude
Geographies and functions involved	What’s handled by other teams or projects
Required analyses and depth of analysis	Potential Phase 2 opportunities (name them, but exclude)
What data and systems will be accessed	Topics where internal resources will self-perform

E. Deliverables, Timelines, Milestones Provide a project skeleton with indicative milestones by phase rather than rigid Gantt charts. This gives consultants flexibility to propose the right methodology while still anchoring on dates that matter.

F. Internal Roles and Support Clarify: Who is the executive sponsor? Who is the day-to-day project manager? What data and system access will be provided? What internal capability gaps need the consultant to fill?

G. Open but Guided Create RFPs that provide structure while explicitly inviting consultant innovation. “We’re open to alternative approaches based on your experience with similar situations” produces better proposals than over-prescribed requirements.

H. Pre-RFP Help If internal stakeholders lack alignment or project feasibility is uncertain: commission a scoping workshop before issuing the RFP. Better to spend one day getting aligned than to issue an RFP that generates proposals for three different projects.

Stage 2: Scoping Negotiation (Consultant Side)

Once consultants respond, four categories of negotiation levers:

A. Optimize Staffing

• Right-size teams: Partners for problem framing, Managers for coordination, Associates for execution
• Phase the project: Logical phases with go/no-go gates reduce commitment risk
• Ramp intelligently: Stagger onboarding; reduce team size in later phases

B. Scope to Strict Necessity

• Separate must-haves from nice-to-haves
• Eliminate redundancy with internal resources or prior projects
• “Design to Cost” approach: Fix the budget, then co-develop the scope that fits. A tech firm reduced consulting costs 38% using this approach.

C. Optimize Delivery Model

• Evaluate make-or-buy: Can internal resources do parts of this?
• Consider non-traditional models: freelancers, expert platforms, boutique specialists alongside or instead of large firms

D. Volume and Unbundling

• Volume pooling: Group similar projects across business units for better pricing
• Activities unbundling: Use specialized firms for distinct components rather than forcing one-stop-shop coverage

SOW vs. Scope of Work

These are different documents:

Document	What it covers
Scope of Work (SOW)	Usually one section inside the full agreement — defines what is included and excluded
Statement of Work (SOW)	The full delivery document: outcomes, deliverables, timeline, roles, governance, and commercial terms

A well-structured Statement of Work has:

1. Project objectives and success criteria
2. Deliverables with acceptance criteria (objective, verifiable)
3. Timeline and milestones
4. Team structure (consultant and client) with named roles
5. Effort and pricing (by phase or sub-deliverable)
6. Governance: meeting cadence, decision rights, issue escalation, change control
7. Assumptions and dependencies
8. Out-of-scope exclusions

Acceptance criteria principle: Each deliverable must have acceptance criteria that can be checked without debate. “Final report delivered” is not an acceptance criterion. “Final report delivered, reviewed by steering committee, and approved or returned with written feedback within 5 business days” is.

Common Scoping Pitfalls

Pitfall	What happens	Prevention
Over-scoping	Conflicting objectives dilute focus; costs inflate	Prioritize objectives ruthlessly before issuing RFP
Under-scoping	Vague requirements generate misaligned proposals; negotiation friction	Use the 8-component RFP structure
Skipping internal alignment	Misaligned sponsors create moving targets	Scoping workshop before RFP
Static scope document	Scope creep without control	Scheduled review checkpoints; change control protocol
Ignoring consultant perspective	Proposals converge on the wrong approach	Signal openness to alternative approaches

Supply Chain Specific Scoping Considerations

For supply chain engagements specifically:

• Data availability is a scope driver. If the client cannot provide SKU-level order history for 12+ months, network design and slotting analyses will be limited. State data requirements explicitly in the RFP.
• Benchmark access affects quality. Specify whether the client expects the consultant to supply industry benchmarks or whether internal data is sufficient.
• Phase 1 diagnostic → Phase 2 implementation is the standard structure. Explicitly define what triggers Phase 2 and whether Phase 2 is already awarded or will be re-competed.
• System access timing. Extracts from WMS/ERP/TMS systems can take weeks in large organizations. Build system access into the project plan as a dependency, not an assumption.

---

Qualification Frameworks for Complex Deals (3.2)

The scoping conversation is inseparable from the qualification conversation. Two frameworks apply at different deal sizes:

BANT (Budget, Authority, Need, Timeline) — appropriate for transactions under $50K with sales cycles under 45 days. For complex SC consulting above $150K, BANT tells you whether a project exists but not whether you can win it, who will actually decide, or whether internal dynamics will kill it before contract execution.

MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) — the correct framework for deals above $150K with multiple stakeholders and long cycles:

Element	SC Consulting Application
Metrics	What KPIs or financial outcomes define success? Cost per order, inventory turns, on-time delivery?
Economic Buyer	Who writes the check? Have you met them? A verbal yes from a Director whose CFO has not been briefed is not a qualified deal.
Decision Criteria	Formal rubric used to evaluate proposals? Published weights?
Decision Process	Full approval chain: who approves what, in what sequence, with what timeline?
Identify Pain	Quantified operational or financial problem driving the project — not “we want to improve” but “our CPO is $22 vs. $10–$15 industry median”
Champion	Internal sponsor actively selling on your behalf when you’re not in the room

MEDDPICC adds Paper Process (contract, legal, purchasing approvals) and Competition — both critical for integrator deals where legal review adds six weeks to closure.

Discovery Call Structure

A 45-minute discovery call should follow this structure:

• Min 0–5: Set the agenda. “I want to make sure this is a good use of your time. I’d like to understand your situation, share how we approach these engagements, and be direct about whether we’re the right fit.”
• Min 5–15: Their situation. Open questions only. No pitch. This is where you learn what’s actually happening — not the polished RFP version.
• Min 15–30: Dig into the problem. MEDDIC questions. What data do they have? Who else is involved? What happens if nothing changes? The most important question: “What does success look like for you personally in 12 months?” — not the company, them. Career stakes drive project reality more reliably than organizational strategy.
• Min 30–40: Two to three minutes on your approach and relevant reference examples, connected to what they said in the first 30 minutes.
• Min 40–45: Specific next steps. “I’d like to propose a site visit in the next two weeks. I’ll need 12–24 months of order history and your item master before we arrive. Can we set that up today?”

Site Visit Protocol

What to request before arriving:

• 12–24 months of outbound order data (order header and detail, with timestamps)
• Item master with dimensions, weights, velocity class, hazmat flags
• Labor schedule by shift and day of week
• Layout drawing (CAD or PDF)
• Slot assignment file if slotting software exists
• Current throughput metrics: orders/hour, lines/hour, UPH by function
• Equipment inventory (conveyor, pick vehicles, sortation)

Walk sequence: (1) Receiving and inbound docks, (2) Reserve storage, (3) Forward/active pick faces, (4) Replenishment process, (5) Pack and ship, (6) Returns and reverse logistics, (7) Supporting areas (charging rooms, staging)

What clients don’t tell you:

• Actual labor utilization vs. what they report
• Damage levels — correlates with operational discipline more reliably than any KPI report
• Workarounds — manual processes signaling systemic WMS problems the software isn’t solving
• Culture — operator engagement and supervisor-floor dynamic; a facility with bad culture will resist every recommendation you make

Always get written permission to photograph before the visit begins. Many DCs have visitor NDA requirements.

Red Flags That Should Kill Deals Early

Red flag	What it usually means
”We just need a quick study”	Wants to validate a decision already made; limited budget; will not act on findings. Ask: “Who is this study going to?” A study going to the board has teeth.
No data or clearly wrong data	If they can’t provide 12 months of clean order history at the order-line level, the project is not ready. Bad data → confident wrong answers. Make clean data a pre-condition.
Unclear decision-maker	You’ve qualified the Director; the VP needs to approve; the CEO hasn’t been briefed. Map the full approval chain before writing the proposal.
”Automation didn’t work before”	Ask why. Technical failure = solvable. Organizational failure (no champion, operator resistance, poor change management) = fundamentally harder problem. Know what you’re walking into.
RFP issued late Q3/Q4 with December close	Manufactured urgency. Real projects with December requirements are in the budget. November RFPs wanting December awards are often compliance bids or slipped projects.
Politically driven scope	”Evaluate the feasibility of a 600,000-bin AutoStore installation in Building C.” Ask directly: “Has your team been through a vendor demonstration process already?”

Scoping Fees: Bottom-Up vs. Value-Based

Bottom-up by hours — right when scope is well-defined. Build a staffing plan week by week, task by task. Apply loaded billing rates. Add contingency (15% for well-defined; 20–25% for client-dependency-heavy work). Never start with a target number and rationalize backward.

Example: 400 hours at blended $225/hr = $90,000. Add 20% contingency = $108,000. Don’t round down to $100K to win the deal — you’ll regret it by week six.

Value-based pricing — right when the output drives a decision worth 100× the consulting fee. A concept study for a $5B retailer evaluating a $20M automation investment should be priced differently than the same study for a $200M distributor. But you need the relationship and the evidence to defend it.

Current market benchmarks — boutique/mid-tier rates, not Big 4:

Engagement type	Range
Concept study / single-site feasibility	$30K–$100K
DC operations assessment	$75K–$200K
Network design study	$150K–$600K
WMS/technology selection	$100K–$400K
Multi-site transformation program	$400K–$2M+

Day rates: senior consultants $2,000–$3,500/day; principal/SME $4,000–$8,000/day depending on firm tier and engagement complexity.