Consulting sales is not advertising a service, sending a quotation and closing a deal. A firm such as PwC must connect market intelligence, brand and thought leadership, executive relationships, discovery, solution engineering, independence and risk controls, commercial modelling, contracting, delivery, benefits realisation and long-term account growth.

PwC UK describes consulting as combining strategy, technology and delivery, with an emphasis on outcomes rather than advice alone—spanning business operations, customer transformation, cloud, data and analytics, cyber, digital-core modernisation, risk and regulation, technology alliances and managed services.

1. The full funnel at a glance

Market insight → Brand awareness → Target-account development
    → Executive relationship → Buying signal → Lead qualification
    → Opportunity qualification → Pursuit decision
    → Discovery and problem framing → Solution and business case
    → Proposal and pitch → Negotiation and contracting
    → Delivery mobilisation → Transformation delivery
    → Value realisation → Managed services or expansion

Also framed as: Market to lead → Lead to opportunity → Opportunity to order → Order to delivery → Delivery to value → Value to growth.

Part I: Three connected journeys

Partners, directors, industry leaders and solution engineers often stay involved from early market development through delivery and growth.

Part II: Marketing journey

Stage 1 — Market sensing​

Before a specific client contact, teams monitor regulation, economics, technology, disruption, cyber, workforce, policy, transactions, investment and leadership changes. Agentic AI, for example, may drive demand for AI strategy, governance, architecture, workforce, cyber, data modernisation, implementation and managed AI ops.

Outputs: POV documents, trend reports, priority-client lists, campaign themes, emerging propositions, talking points, sector forecasts. Public research creates awareness and a reason for senior conversations.

Stage 2 — Proposition development​

A proposition is more specific than a capability.

Components: target client · problem · trigger event · outcomes · solution shape · differentiators (industry expertise, multidisciplinary teams, alliances, risk/regulatory knowledge, delivery, assets, credentials).

Outputs: summary, buyer profile, sales narrative, catalogue, reference architecture, methodology, timeline, pricing approach, credentials, demo, campaign.

Stage 3 — Thought leadership and awareness​

Reports, surveys, briefings, webinars, benchmarks, case studies and roundtables help clients see what is changing, why it matters, what leaders do, risks, decisions and priorities. Example path: report → partner share → roundtable → executive discussion → workshop → opportunity.

Judge marketing by executive reach, meetings generated, pipeline influenced and proposal invitations—not clicks alone.

Stage 4 — Account-based marketing​

Coordinate marketing, industry leadership, relationship partners, specialists, alliances and account teams around strategic accounts: priorities, decision-makers, live transformations, 12–36 month issues, prior work, competitors, vendors, distinctive value.

Example retail-bank campaign: customer-service transformation, financial crime, cloud, AI governance, cost, workforce—via tailored briefing, benchmark, regulatory update, private roundtable, demo, alliance intro, strategic workshop. Goal: relevance and informed understanding—not pressure selling.

Stage 5 — Relationship development​

Clients buy expertise, judgement, delivery capability and trust. Map board, C-suite, risk, architecture, transformation and procurement relationships. Good meetings often focus on priorities, market insight, constructive challenge and specialist introductions—commercial opportunities may follow later.

Part III: Leads and opportunity creation

Stages 6–8 — Buying signal, triage, first conversation​

Strong signals: budget, announced programme, RFP, new executive, platform EOL, regulatory deadline, failed prior programme, board mandate, vendor evaluation, workshop request, adjacent problem from live work.

Weak signals: curiosity, webinar attendance, download, no budget/sponsorship, junior contact—nurture, do not treat as qualified opportunities.

Triage: organisation, need, service line, account team, partner, deadline, budget evidence, estimated value, next action → assign, nurture, convert, decline or refer.

First conversation is diagnostic—situation, problem, impact, desired outcome, decision process, commercial context. Avoid a full solution too early. Output: opportunity hypothesis (e.g. 12-week AI strategy and governance, then controlled implementation).

Part IV: Opportunity qualification

Stage 9 — Structured qualification​

Assess: client need · urgency · sponsorship · funding · decision process · competitive position · delivery feasibility · commercial attractiveness · risk acceptability (conflicts, independence, reputation, unrealistic guarantees).

Classifications: Qualified · Conditionally qualified · Continue discovery · Nurture · Partner-led · No bid.

Stage 10 — Pursuit (bid/no-bid) decision​

Go when the problem is strategic, capabilities fit, relationship credible, opportunity winnable and deliverable, commercials reasonable, risk manageable, account strategy supported.

No-go when no budget, spec written for another supplier, unreasonable guarantees, capability gap, impossible deadline, unresolved independence/conflicts, unacceptable liability, disproportionate pursuit cost, or professional-obligation conflict.

Decide pursuit investment: partner time, proposal support, solution engineering, prototypes, specialists, alliances, legal/commercial. Good pre-sales selects the right opportunities.

Stage 11 — Independence, conflicts, acceptance​

Check existing relationships, audit independence, conflicts, sanctions, integrity, reputation, service nature, capacity, subcontractors, data/confidentiality, regulation. Outcomes: cleared · cleared with safeguards · further consultation · modify scope · decline. Run early enough to avoid sunk pursuit cost.

Part V: Pre-sales discovery

Stages 12–15 — Team, plan, stakeholders, discovery​

Pursuit roles: lead partner · pursuit director · industry lead · solution lead · solution engineer/architect · commercial · delivery · risk/legal/independence · proposal support · alliance specialists.

Artefacts: pursuit plan, RACI, stakeholder/decision maps, competitor analysis, win themes, question/assumption/risk logs, proposal outline, review calendar, action tracker. Governance: stand-ups, partner/solution/commercial/risk/proposal reviews, pitch rehearsals.

Stakeholder map: economic buyer, executive sponsor, technical/business buyers, risk approver, procurement, users, blockers—formal vs informal power, winners/losers, preferred suppliers, evidence and reassurance needs.

Discovery methods: interviews, walkthroughs, data/architecture reviews, user research, workshops, assessments, benchmarking. Co-creation brings stakeholders together to understand, explore, design, align and decide.

Dimensions: strategy · business model · process · CX/EX · data · technology · security/risk · organisation · delivery · commercials.

Outputs: current-state assessment, problem statement, maps, requirements, data readiness, architecture summary, risk, value hypotheses, assumptions, dependencies, prioritised use cases.

Part VI: Problem framing and win strategy

Stages 16–17​

Reframe: “We need an AI chatbot” → “Reduce avoidable service demand, improve agent productivity and keep consistent outcomes without increasing conduct risk”—possibly knowledge, process redesign, agent assist, self-service, routing, training, conversational AI and controls.

Logic: business objective → problem → root causes → capabilities → operating-model changes → technology—not tool first.

Win themes (evidence-backed): industry understanding, strategy-to-execution, risk/regulatory strength, alliances, delivery team, accelerators, Responsible AI by design, managed services, collaborative approach. Example: move from disconnected pilots to a governed enterprise capability combining strategy, engineering, risk, change and managed operations.

Part VII: Solution shaping

Stages 18–22​

Options: (1) assessment and strategy · (2) discovery and pilot · (3) full transformation · (4) managed service. Evaluate on alignment, value, time to value, cost, risk, complexity, readiness, scalability, regulation, ops support.

Target operating model: organisation, governance, processes, people, technology, data, performance—without it, technology may work but nobody owns, governs or maintains it.

Technical solution engineering: architecture, build/buy, integration, data flows, security, environments, models, evaluation, observability, support. GenAI layers often include UX, identity, API/orchestration, agent/workflow, models, retrieval, data, guardrails, evaluation, monitoring, audit, infrastructure.

Alliances: platforms (cloud, ERP, CRM, ServiceNow, foundation models, specialists) contribute specialists, demos, validation, funding, training; the firm contributes industry, transformation, risk, process, architecture, change, managed services. Remain technology-appropriate for the client—not alliance-default.

Risk-tiering: lower (internal search, summarisation, drafted content with review) · medium (employee decision support, agent assist) · higher (regulated customer advice, employment/credit/health decisions, autonomous financial actions). Proportionate controls enable responsible scaling.

Part VIII: Business case and value

Stages 23–26​

Baseline operating cost, volumes, effort, errors, complaints, cycle time, revenue conversion, incidents, tech cost, availability.

Benefit types: financial · operational · customer · employee · risk · strategic. Distinguish theoretical → addressable → achievable → adopted → financially realisable; use transparent assumptions, ranges and sensitivity.

Investment model: consulting, client resources, licences, cloud/model usage, data/integration, cyber, change, training, support, managed services, contingency. Outputs: benefit/cost models, cash flow, payback, ROI, sensitivity, assumptions, benefit ownership, measurement plan—carry into delivery, do not abandon after signature.

Part IX: Delivery model and estimation

Stages 27–29​

Workstreams (example AI transformation): strategy/value · use-case prioritisation · operating model · Responsible AI · data/knowledge · architecture/engineering · cyber · change · PMO · benefits.

Methodology: waterfall, Agile, hybrid, product-based, pilot-to-scale, phased rollout. Typical phases: Discover → Design → Build → Test → Deploy → Scale → Operate.

Resource estimate validated by delivery leaders—sales estimates without delivery challenge create post-signature pain. Include partner, programme, product, architecture, AI/data/cloud engineering, BA, risk, security, change, UX, test—and client resources.

Part X: Commercial development

Stages 30–32​

Model staff cost, rates, travel, tech, subcontractors, cloud, contingency, risk premium, overhead. Challenge unrealistic assumptions (instant access, no delay, perfect data, no change, full utilisation, no rework).

Document assumptions and client responsibilities: data access SLAs, product owner, security approvals, API readiness, UAT capacity, use-case count, support exclusions, travel.

Part XI: Proposal development

Stages 33–35​

One coherent argument: we understand your situation → we identified the real problem → we propose a credible solution → we have the team → investment justified → risks manageable → we stay accountable for outcomes.

Contents often include: executive summary, understanding, challenges, POV, outcomes, scope, approach, workstreams, deliverables, timeline, governance, team, architecture, data, security, Responsible AI, change, benefits, credentials, commercials, assumptions, client responsibilities, exclusions, qualifications.

Reviews: compliance · solution · delivery · commercial · risk · executive.

Part XII: Pitch and evaluation

Stages 36–38​

Pitch structure: confirm outcome → what we heard → reframe problem → POV → solution → implementation → value → risk/governance → team → commercials and next steps.

Clients evaluate understanding, credibility, chemistry, industry/tech quality, delivery confidence, risk awareness, commercial value, cultural fit—and how the team works together, whether seniors understand the solution, listening and constructive challenge.

Demonstrations must prove a relevant point (experience, data connection, controls, integration, process improvement)—not spectacle.

Part XIII: Clarification, negotiation, close

Stages 39–43​

Assess every clarification for scope, cost, timeline, risk, resource and contract impact—do not absorb unpaid scope.

Negotiate price, milestones, rates, team, liability, IP, SLAs, acceptance, termination, warranty, data. Exchange concessions: narrower scope for lower price; longer commitment for discount; faster client decisions for faster delivery; stronger assumptions for fixed price; change control for extra work.

BAFO: final solution, price, team, contract position, differentiators, feasibility, approvals—avoid winning on undeliverable terms.

Preferred bidder ≠ done: MSA, SoW, engagement letter, DPA, security schedule, SLA, change control. Signature starts delivery obligations.

Part XIV–XVI: Handover, delivery, expansion

Stages 44–53​

Handover: context, stakeholders, contract, proposal, scope, deliverables, timeline, commercials, architecture, risks, assumptions, dependencies, client commitments, negotiation decisions, relationship sensitivities, benefits case. Keep solution engineer and delivery lead through transition.

Mobilisation: governance, access, scope validation, detailed plan, reporting, RAID/decision logs, kickoff, financial and benefits baselines.

Detailed discovery may revise pre-sales assumptions—use change control for material differences. Build/implement iteratively: plan → design → build → test → demonstrate → learn → improve.

Testing proportionate to risk: functional, integration, performance, security, privacy, a11y, UAT, ORR, DR, AI evaluation, bias, hallucination, adversarial.

Deployment includes communication, training, role/process/policy change, support, adoption monitoring, operational handover. Tech success can fail commercially without trust and use.

Benefits realisation compares to the business case; decide adjust, scale or optimise.

Operations: client transfer, PwC managed services, or another provider. Gather feedback; expand from genuine need (scale pilot, new BUs/countries, integrations, governance, managed support, new use cases)—deliver value → earn trust → understand better → next problem → next opportunity.

Part XVII–XVIII: Funnel and metrics

Marketing: reach, events, engagement, meetings, pipeline influenced. Sales: pipeline, win rate, deal size, cycle length, forecast accuracy. Pursuit: cost, quality, compliance, win/loss reasons. Commercial: contract value, margin, discount, payment terms, exposure. Delivery: scope, schedule, cost, quality, CSAT, utilisation, margin, risks. Value: benefits, adoption, ROI, customer/employee/ops outcomes.

Part XIX: Role of an AI Solution Engineering Manager

Part XX: Worked example — insurer GenAI productivity

1. Market sensing: insurers interested in GenAI but worried about harm, privacy, hallucination, regulation, legacy, governance.
2. Marketing: responsible-AI report + insurance roundtable.
3. Account: partner engages COO and CRO.
4. Signal: rising service cost; board wants an AI plan.
5. Qualify: sponsorship, likely budget, ~3-month decision, capability fit.
6. Pursue: insurance partner, AI solution lead, risk, data architect, change, commercial.
7. Discover: fragmented knowledge, long search times, variable data quality, customer-facing AI high risk, no enterprise eval framework.
8. Reframe: controlled agent-assist first + governance for future customer-facing AI—not chatbot-first.
9. Solution: Phase 1 prioritisation/data/RAI/business case/architecture → Phase 2 agent-assist pilot with approved knowledge, human verification, evaluation, audit → Phase 3 controlled deploy, training, monitoring, benefits → Phase 4 possible customer-facing expansion.
   10–12. Case, pitch, negotiate: shorter pilot accepted with fewer use cases, faster data access, dedicated SMEs.
   13–15. Contract, deliver, measure: time saved, adoption, answer quality, escalations, risk incidents, EX.
10. Expand: more teams, use cases, channels, managed AI operations once value and safety proven.

Final principles

The journey in one line: understand the market → develop propositions → create awareness → target accounts → build relationships → spot signals → triage → discover → qualify → pursue → clear risk → shape solution and TOM → engineer and govern → build the case → price → propose → pitch → negotiate → contract → hand over → mobilise → deliver → test → adopt → realise value → operate → expand where justified.

Central objective: convert an uncertain client problem into an engagement that is strategically relevant, valuable, technically feasible, responsible and secure, commercially viable, contractually clear, deliverable by the proposed team and measurable after implementation.

The strongest consulting sales journey does not end at signature. It ends when the client receives measurable value—and that value creates trust for the next important conversation.

For worked AI solution engineering scenarios drawn from this journey, see the case studies hub (Case A Meridian, Case B MonGo, Case C bid/no-bid—each with a parent and expanded parts).