Skip to content
Menu
Cloud Gal 42
  • Home
    • Affiliate Disclosure
    • Privacy Policy
  • Solution Selling Tutorial
  • AI-SGAP
    • Beta Partners
    • Investors
  • 4022 Reader Updates
Cloud Gal 42

Solution Selling Tutorial

Moving Enterprise Deals Forward with Solution Selling and Joint Customer Workshops

An eight-part tutorial series by Amrita Mukherjee, ex-Oracle, ex-KPMG, ex-Wipro | CCSP

For account executives, solution architects, alliance leaders, and consulting partners who need to turn a customer problem into an agreed solution, a credible business case, and an executable buying decision.

Tutorial contents

  1. Qualify the problem before you qualify the deal
  2. Build the buying team before the workshop
  3. Design a JCW around a customer decision
  4. Compare architectures the customer can actually buy and operate
  5. Build a business case that survives finance review
  6. Turn the workshop into a bounded proof of value
  7. Turn technical confidence into a buying decision
  8. Measure JCW success through customer progress

Part 1 of 8 · Discovery and qualification

Qualify the problem before you qualify the deal

A customer asks about cloud migration. Another wants to explore AI. A third needs to reduce database costs. These are useful starting points. They still leave the most important question unanswered: what business decision does the customer need to make?

In my Oracle alliance and presales work, I used Joint Customer Workshops, or JCWs, to connect business priorities with architecture, economics, and delivery planning. The workshop motion helped structure opportunity development: establish the current state, compare options, examine value, define a roadmap, and identify the next commitment.

This series explains that approach. Customer identities are anonymized, and historical pursuit examples are labeled according to what they establish. The practical templates are my recommended ways to apply the lessons.

Start with a problem the customer recognizes

Solution selling begins with the customer’s needs and problems, then develops a recommendation around them. Salesforce’s overview provides a useful introduction. In an enterprise pursuit, I translate that principle into five discovery questions:

  1. Which business process needs to improve?
  2. What happens today, and who experiences the consequences?
  3. What evidence would let us establish the size of the problem?
  4. Why would the organization act now?
  5. Who owns the decision and the resources needed to act?

A request for an AI demonstration might lead to a claims-processing discussion. That discussion might reveal investigation delays, fragmented information, or excessive manual review. Each possibility implies a different solution and a different measure of value. Treat them as hypotheses until the customer confirms them.

From our pursuit work: an insurance organization

For Insurer A, our JCW design connected claims-fraud opportunities, claims-platform modernization, and potential budget levers. The useful lesson is the framing: a fraud discussion could also expose platform and funding questions that needed to be addressed together.

This was a pursuit and workshop-design example. It does not establish that a model reduced fraud or that a resulting deal closed. The questions I would carry into discovery are concrete: which claims are in scope, what constitutes a confirmed fraud outcome, how much review capacity exists, and which platform limitations prevent improvement?

Write the problem in a form that can be challenged

For [business owner], [current condition] creates [business impact]. We will validate the impact using [evidence]. The next decision is [decision], owned by [person or role].

Leave unknown fields visibly unknown. A missing baseline is a discovery task. A missing decision owner is a qualification gap. Neither becomes more reliable because a seller assigns a probability in the CRM.

Try this on one opportunity

Rewrite its description without mentioning a product. Ask the customer to correct the problem statement and identify the evidence owner.

Advance when: the customer recognizes the problem, assigns an owner, and agrees to a discovery step. Hold the stage if interest is the only evidence.

Next, we will identify the people whose participation turns that discovery into a decision the organization can support.

Part 2 of 8 · Stakeholders and partner alignment

Build the buying team before the workshop

A workshop can produce a technically sound recommendation that nobody is prepared to fund or operate. Before building an agenda, identify the people who must help make the decision—and the questions each of them needs answered.

My alliance work involved coordinating sales, architects, product teams, GSI leadership, delivery specialists, and customer executives. That experience informs a simple rule for JCWs: attendance should follow decision responsibility.

Map the decision, then invite the participants

RoleQuestion to resolveContribution
Business ownerWhat outcome matters?Priority, scope, baseline, acceptance criteria
Budget owner or financeHow could this be funded?Investment limits and benefit validation
Architecture and operationsCan we implement and run it?Dependencies, standards, staffing, support
Security and riskWhat must be demonstrated?Control requirements and review path
Procurement and legalHow will a purchase happen?Contracting process and lead times
Executive sponsorHow will competing priorities be resolved?Organizational support and escalation

One person may hold multiple roles. Some specialists may contribute before or after the main session. The objective is coverage of the decision, rather than a large audience.

From our pursuit work: a medical technology organization

The planning brief for MedTech B connected a substantial cloud migration ambition with a recurring savings requirement. That pairing changes the workshop. Architecture alone cannot settle whether the migration is fundable; a savings model alone cannot establish whether the workloads can move.

A workshop designed around that problem needs infrastructure inventory, application dependencies, cost ownership, and migration constraints. Finance should help define what counts as a saving. Operations should identify which costs actually disappear when a workload moves. This is a lesson from the planning problem, not a claim that those savings were achieved.

Give the vendor and GSI distinct responsibilities

For an Oracle and North American GSI workshop, I would assign Oracle responsibility for substantiating product capabilities, service constraints, and commercial assumptions. The GSI should substantiate implementation scope, integration effort, delivery staffing, and operational transition. The customer owns business priorities, acceptance, and the buying decision.

Before the customer session, agree who facilitates, who captures decisions, and who owns each follow-up. Resolve contradictory assumptions early. If one team assumes a database migration and the other assumes application redesign, they are estimating different projects.

Also distinguish a helpful contact from a champion. A potential champion can help explain the internal decision process, bring the right colleagues into the conversation, and test the recommendation internally. Do not assume they control the budget.

Try this on one opportunity

Create a role map with a name, decision responsibility, unresolved question, and next action for each participant. Use “not identified” where necessary.

Advance when: the decision path is understood and the people needed for the next step have agreed to participate. Unresolved procurement or security questions stay visible.

The next post turns that stakeholder map into a workshop with a specific decision at its center.

Part 3 of 8 · Workshop design

Design a JCW around a customer decision

A useful JCW starts with a sentence: “By the end of this workshop, the customer should be able to decide whether to ___.”

The blank might be a funded assessment, a bounded proof of value, or a preferred architecture for further validation. Choose something the available evidence and participants can realistically support. An early workshop rarely resolves every technical, financial, security, and contractual question.

From our pursuit work: a consumer-products organization

For Consumer Products C, our workshop planning examined Oracle database modernization, deployment alternatives, and how potential optimization savings could support a broader transformation. The proposed work connected discovery, architecture, migration validation, economics, and an executive readout.

The reusable lesson is the sequence. Inventory informs architecture; architecture informs migration effort and cost; those findings inform the investment decision. The historical plan does not establish completed migration, realized savings, or approval of the next phase.

Prepare a one-page charter

  • Business question: what decision should become easier?
  • Scope: which workload, process, geography, or business unit is included?
  • Inputs: what evidence must the customer and partners bring?
  • Outputs: which artifacts will support the decision?
  • Decision owner: who accepts the recommendation or requests more work?
  • Boundaries: what will remain outside this workshop?

Request a manageable evidence pack: an inventory extract, a current architecture, a cost baseline, known constraints, and relevant performance or recovery requirements. If access is unavailable, make the session a discovery workshop and adjust its intended output.

A practical one-day agenda

The following agenda is a reusable teaching template, not a reconstruction of the historical engagement.

TimeActivityOutput
09:00–09:30Confirm business prioritiesAgreed problem and decision
09:30–10:30Review current stateBaseline and evidence gaps
10:45–12:00Compare feasible optionsShortlist and tradeoffs
13:00–14:00Examine economics and deliveryAssumptions and dependencies
14:00–15:00Design validationTest scope and acceptance criteria
15:15–16:00Customer decision readoutDecision or bounded next step

During the session, keep separate lists for facts, assumptions, decisions, and open questions. A proposed architecture remains a proposal until the appropriate customer owners accept it. A promising saving remains an estimate until its inputs and realization path are validated.

End by reading the decisions back to the participants. Ask whether the record accurately captures their position. A facilitator should make disagreement visible while the people who can resolve it are still present.

Try this on one opportunity

Write the charter before the slide deck. Remove any agenda item that does not help answer the decision question.

Advance when: the customer accepts the outputs and agrees to a named next action, owner, and date. An unresolved question may justify a smaller assessment instead of a larger commitment.

Next, we will examine how to compare cloud options without deciding the winner before the evidence is available.

Part 4 of 8 · Solution selection

Compare architectures the customer can actually buy and operate

The customer’s fastest route to value depends on what already exists: applications, data, contracts, skills, controls, and operational processes. A comparison that ignores those conditions can recommend an attractive architecture that takes too long to adopt.

In our modernization pursuit work, we compared cloud and multicloud approaches alongside the customer’s business priorities. For Consumer Products C, the planning included OCI and a Google Cloud database deployment alternative. The lesson is to compare complete implementation paths, including what must change around the database.

Build a comparable shortlist

The options below are evaluation paths, not rankings. Oracle currently documents database offerings across AWS, Azure, and Google Cloud on its multicloud overview. Verify the exact service, region, capabilities, and commercial terms for each pursuit; do not apply today’s availability to a historical plan.

OptionQuestion for the workshop
OCIWhat changes if the selected workload runs on OCI, including its application dependencies and operating model?
AWSWhat is the complete AWS deployment design, including the chosen database service and any required application changes?
Microsoft AzureHow does the design fit the customer’s application estate, identity approach, and operations?
Google CloudHow does the design fit the customer’s data, analytics, application, and operational requirements?
Oracle Database@AWS, Database@Azure, or Database@Google CloudDoes the relevant offering meet the workload requirements while fitting the customer’s application location and cloud strategy?
Retain and optimizeWhat improvement is possible without migrating now, and what limitations remain?

For each option, define the same workload boundary, service expectations, demand assumptions, and cost horizon. Specify whether the proposal retains Oracle Database or changes database technology. Those paths may involve very different conversion and testing work.

Evaluate mandatory requirements before preferences

Start with requirements that must be satisfied: supported workload, required location, security acceptance, recovery needs, and a feasible migration path. A low price cannot compensate for failing a mandatory requirement.

Then compare feasible options against customer-agreed priorities. Use a simple one-to-five score if it helps, but attach evidence and confidence to every score. Mark unknowns as unknowns. Do not award points for assumptions that have not been tested.

Identify three winners separately

  • Fastest time to market: the feasible path with the shortest credible critical path through access, contracting, migration, testing, and acceptance.
  • Lowest TCO: the feasible path with the lowest complete cost over the agreed period.
  • Highest ROI: the feasible path with the strongest validated net benefit relative to investment.

These may be different options. Explain the tradeoff and let the customer’s priorities determine the recommendation. Without workload and commercial inputs, naming a universal cloud winner would be guesswork.

Try this on one opportunity

Compare two feasible architectures and the status quo. Identify the three unknowns most likely to change the recommendation.

Advance when: the customer accepts the shortlist, selection criteria, and validation plan for the remaining unknowns.

The next post turns that architecture comparison into an economic case finance can examine.

Part 5 of 8 · Economics and funding

Build a business case that survives finance review

A proposal can show a lower future run rate and still require more cash than the customer can commit today. Migration costs arrive before all savings do. Existing contracts may continue. People still need time to test, learn, and operate the new environment.

Our pursuit planning for MedTech B and Consumer Products C connected modernization with potential savings and funding levers. That is a useful way to structure a business case, provided the team distinguishes an opportunity to save from money available to spend.

Build the baseline with its owner

Agree on the period and scope before calculating. Include infrastructure, software, support, operations, backup, recovery, networking, facilities where relevant, and any genuinely avoidable costs. For the proposed path, include migration, integration, testing, training, parallel operation, and decommissioning.

Classify benefits carefully. Reduced spending is different from avoiding a future purchase. Staff capacity released is different from a reduced payroll expense. Potential risk reduction is different from a guaranteed cash benefit. Finance should decide how each category enters the model.

A worked example with invented teaching numbers

The following figures are illustrative and are not customer results. Assume a three-year evaluation, an existing annual run cost of $1.2 million, a proposed annual run cost of $900,000, and a one-time transition cost of $450,000. Assume the annual reduction starts immediately after transition and remains constant.

CalculationResult
Status-quo three-year TCO: $1.2m × 3$3.60m
Proposed three-year TCO: $0.9m × 3 + $0.45m$3.15m
Annual operating cost reduction$300,000
Three-year net saving: $3.60m − $3.15m$450,000
Simple ROI on transition investment: $450k ÷ $450k100%
Simple payback: $450k ÷ $300k per year1.5 years after savings begin

This is an undiscounted model. Its ROI denominator is the incremental transition investment, not total solution spending. The assumptions deliberately simplify timing; a real model should show monthly cash flows, delayed savings, demand changes, and the customer’s finance-approved discount rate.

Now test the downside. If the annual reduction is only $150,000, three-year gross savings equal the $450,000 transition cost. Net savings and simple ROI become zero; payback takes three years after savings begin. That sensitivity deserves as much attention as the attractive base case.

Make the funding path explicit

Ask which budget pays for transition, when old costs can be retired, and who approves the release of funds. Treat vendor credits or assessment funding as conditional until eligibility, amount, scope, and approval are confirmed. Future savings do not automatically fund today’s project.

Try this on one opportunity

Create base, downside, and upside cases. Give every material assumption an owner and a source, then identify the assumptions that change the decision.

Advance when: finance accepts the model’s scope and assumptions, and a plausible funding path exists. A spreadsheet produced by the seller is a proposal until reviewed.

Next, we will turn the uncertainties behind the model into a bounded proof of value.

Part 6 of 8 · Technical and business validation

Turn the workshop into a bounded proof of value

A proof of value earns its place in a deal when it resolves uncertainty that matters to the buying decision. Start by identifying that uncertainty. Then design the smallest credible exercise that can answer it.

For a migration, the question might concern application compatibility or downtime. For an analytics workload, it could concern representative query performance. For a resilience project, it may be whether the organization can restore a usable service within its agreed requirements.

From our workshop planning: hospitality resilience

For Hospitality D, the JCW design examined recovery architecture choices, recovery objectives, and economics. It proposed a recovery exercise as part of the decision process. This is a workshop-design example; it is not a report of a successful recovery test.

The lesson is to connect product evaluation with the customer’s operating question. A recovery demonstration should have a defined starting condition, workload boundary, dataset, timing method, and validation procedure. Otherwise, participants can leave with different interpretations of what the demonstration proved.

Write the test contract before running the test

FieldWhat to agree
DecisionWhich purchase or implementation decision will this inform?
HypothesisWhat must be true for the proposed solution to be viable?
Representative scopeWhich workload, data, users, and failure conditions will be included?
AcceptanceWhat threshold applies, who selected it, and who accepts the evidence?
MethodHow will results be measured, retained, and reproduced?
BoundariesWhat cost, time, access, and operational limits apply?
ExitWhat happens after a pass, a fail, or an inconclusive result?

For a recovery exercise, separately agree the recovery time objective – the target time to restore the scoped service – and recovery point objective – the acceptable data-loss window. Define how each will be measured, including the start and end of the recovery timer. Validate the recovered application and data, rather than relying only on an infrastructure status.

For Insurer A’s claims-fraud theme, a teaching example would evaluate detection quality alongside the investigation workload created by false positives. The business owner should decide whether the resulting review burden is workable. This proposed evaluation is not a description of a historical test.

Keep three outcomes available

A pass supports the decision only within the tested conditions. A fail identifies a limit, a redesign need, or a reason to stop. An inconclusive result means the evidence did not answer the question—for example, because the data was not representative.

Agree on those outcomes in advance. Adding tests after a result can be appropriate when new uncertainty appears, but it should require a revised question, scope, owner, and time limit.

Try this on one opportunity

Write three acceptance criteria in the customer’s language. For each, specify the evidence and the person authorized to accept it.

Advance when: the agreed results are accepted and the remaining production gaps are documented. A successful demonstration alone does not establish production readiness.

Next, we will connect accepted evidence to the actual commercial decision.

Part 7 of 8 · Commercial decision and handoff

Turn technical confidence into a buying decision

A customer can accept the architecture and still be unable to buy. Funding may remain undecided. The implementation scope may be incomplete. Procurement may require a process that the project team has not started.

The final stage of solution selling connects the evidence developed during discovery and validation with the organization’s actual decision process. In a vendor-and-GSI pursuit, that means aligning product and services commitments around one customer outcome.

Build a concise decision brief

I recommend a brief with six sections:

  1. Problem: the customer-confirmed issue and its business importance.
  2. Recommendation: the selected option and the reason it fits.
  3. Evidence: what discovery and validation established.
  4. Economics: investment, expected benefits, assumptions, and funding source.
  5. Delivery: scope, responsibilities, dependencies, and acceptance.
  6. Decision requested: the specific commitment and outstanding approvals.

Do not erase limitations from the executive version. Translate them into decision language: what remains unproven, what it might change, and who will resolve it.

Use the historical examples at their actual stage

Our Capital Markets E pursuit work connected risk-compute modernization with scalability and economics. That supports a discussion of solution shaping. It does not establish a procurement outcome.

To progress an opportunity of that kind, I would ask whether the business owner accepts the performance requirements, whether finance accepts the cost model, and whether delivery has scoped the transition. Those are teaching questions for the next stage, not reconstructed customer actions.

Create a mutual action plan

A mutual action plan records commitments the customer and selling teams have actually agreed to. The template below illustrates its structure; the dates should come from the real decision process.

MilestoneAccountable roleCompletion evidence
Accept validation findingsCustomer technical ownerRecorded decision and open items
Confirm fundingCustomer budget ownerApproval under customer process
Complete security reviewCustomer security ownerAccepted review or authorized exceptions
Agree implementation scopeCustomer and GSI delivery leadsAccepted scope, exclusions, and responsibilities
Complete contractingAuthorized procurement and legal ownersExecuted required agreements
Start deliveryCustomer and delivery sponsorAccepted kickoff and handoff

Add a due date and dependencies to every row. If a customer has not agreed to a date, label it proposed. A seller’s desired close date does not become a customer commitment through repetition.

Protect the delivery promise

Have the GSI delivery lead review the scope before the commercial proposal is finalized. Confirm what the customer must supply, how acceptance works, and which assumptions could change effort or timing. Product capability, implementation services, and customer responsibilities should fit together.

Try this on one opportunity

Compare the latest proposal with the workshop decision record. Identify any promised outcome that lacks evidence, an accountable owner, or funded work.

Advance when: the required commitments are completed under your organization’s stage definitions. Record a closed win only when its formal booking criteria are met.

The final post explains how to measure the workshop motion without taking credit for outcomes it has not established.

Part 8 of 8 · Measurement and repeatability

Measure JCW success through customer progress

The value of a JCW should become visible in what the customer can decide and do afterward. That might mean approving an assessment, choosing a solution to validate, identifying a funding constraint, or deciding that the proposed project should not proceed.

In my alliance work, the repeatable workshop motion helped surface business problems, shape opportunities, clarify priorities, and connect modernization discussions to next-step ownership. Those are meaningful contributions. Claims about faster sales cycles, improved win rates, or achieved savings require additional evidence.

Measure success at several levels

LevelUseful measureEvidence
Workshop qualityDid the customer find the session relevant and clear?Direct feedback and unresolved concerns
Decision progressWas the intended decision made?Customer-accepted decision record
Pipeline progressWas a qualified next step completed?Stage history and required approvals
Commercial outcomeDid the opportunity meet booking criteria?Authoritative opportunity and booking record
Customer valueDid delivery achieve the agreed outcome?Accepted baseline and post-delivery measurement

Choose a measurement window before reporting conversion. For example, count workshops in a defined cohort and measure how many produced a customer-accepted next step within 30 days. State the denominator, exclude events that have not had the full observation window, and report how many remain pending. The 30-day window is a suggested measurement design, not a historical result.

Avoid attributing the entire deal to one workshop

Enterprise opportunities involve many contributors and interactions. Separate opportunities sourced through the workshop motion from existing opportunities it helped shape. Define “influenced” consistently and deduplicate records before adding pipeline values.

Even if workshop-associated deals show a higher win rate, selection may explain part of the difference. Teams may invite their strongest opportunities into workshops. Compare similar opportunities by stage, size, segment, and maturity, and describe an observed association as an association.

Capture the reason a deal moved or stopped

After each workshop, record the customer decision, missing evidence, objections, actions completed, and changes to the recommendation. A decision to pause because the economics do not work is valuable qualification. Keep it distinct from a commercial win.

Our historical examples offer reusable themes: connect claims-fraud work to the wider platform and funding question; connect migration ambition to realizable savings; compare complete architecture paths; and design recovery validation around the service the customer needs restored. Their documented value is in pursuit framing and workshop design. Customer-specific outcome claims need their own records.

Make the next workshop easier to run

Maintain a reusable kit: discovery questions, stakeholder map, workshop charter, architecture comparison, economic model, validation plan, decision brief, and mutual action plan. Update it when a real engagement reveals a missing question or an assumption that failed.

Ask the customer whether the recommendation addressed the problem they brought into the discussion. Carry that answer into delivery, where the promised value has to become observable.

Try this with your team

Review five completed workshops. For each, identify the intended decision, actual decision, next action, and evidence. Where the evidence is missing, record “unknown.”

Series takeaway: advance an opportunity when the customer’s evidence and commitment support the next stage. Use the JCW to make that progress explicit.

Recent Posts

  • ARTEX and the ConnectWise Supply-Chain Breach: What Happened and How to Check Your Tenants
  • Local Wiki Part 5 · The wiki was running. Why couldn’t I open the Learning Room?
  • Building AI-SGAP: Inside the Engineering Work Since Our Last Update
  • Building a Local Knowledge Wiki Part 4 Exact Evidence Partial Answers and Human Review
  • Building a Local Knowledge Wiki Part 3 Source Imports and Retrieval Failures

Recent Comments

  • Rafael on Installing Debian on OCI
  • Jorge on Installing Debian on OCI
  • admin on Installing Debian on OCI
  • Andreas on Installing Debian on OCI
  • admin on Installing Debian on OCI

Archives

  • November 2026
  • October 2026
  • December 2022
  • February 2022
  • September 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • February 2021
  • January 2021
  • November 2020
  • October 2020

Categories

  • aws
  • bcdr
  • cloud
  • cloudsecurity
  • compliance
  • informationsecurity
  • oracle
  • pci
  • QuickGuide
  • security
  • Uncategorized
©2026 Cloud Gal 42 | Powered by WordPress and Superb Themes!