Sales Enablement Library

Sales Enablement Library

Main entry hero orienting customer-facing teams to conversation guidance, capability boundaries, and specialist handoffs.

• Sales Enablement Library
  Find conversation guidance for customer and account teams, from clarifying a buyer's problem to involving a specialist. Northstar Systems is a fictional sample setting. This library supports buyer conversations; it is distinct from a marketing brand-assets hub.
• Browse conversation guidance
  Choose the topic that matches your next customer question. Customer problems Clarify the buyer's situation before proposing a response. Solution fit Compare stated needs with documented scope and known gaps. Proof and demos Prepare a focused demonstration and explain what it does—and does not—show. Objections Respond to concerns without guessing or overpromising. Specialist help Prepare a useful handoff when a question needs another role. Customer Discovery Conversation Plan a discovery conversation around the customer's problem. Proposal Pursuit Room Coordinate a proposal team from kickoff to submission. Customer Reference Request Ask a customer to act as a reference, the right way.
• Prepare for the conversation
  A short sequence for keeping the discussion grounded in the buyer's needs. Clarify the problem Capture the buyer's words, affected teams, current approach, and desired change. Check solution fit Compare the stated need with approved material; identify dependencies and unanswered questions. Choose relevant proof Use evidence that relates to the buyer's question and distinguish an illustration from a customer-specific result. Prepare for concerns Acknowledge the concern, answer from approved information, and agree how open questions will be handled. Bring in a specialist when needed Share the need, material checked, open question, and decision needed.
• Keep claims and open questions distinct
  Use conversation guidance to organize the discussion, not to turn an assumption into a fact. Separate what the buyer has told you, what approved material supports, and what still needs a reliable answer. If a capability, result, dependency, or customer-specific claim is not supported by the material you have checked, say what remains unknown and route the question to the appropriate specialist.

Customer problems

• Start with the buyer's situation
  A useful discovery note preserves what the customer said and makes uncertainty visible. Record five things: the customer's words for the problem, the teams or work affected, the current approach, the change they want, and what you do not yet know. Keep interpretation separate from reported facts. Worked example: In the fictional Northstar sample, a buyer says, “Order exceptions take time to reconcile across teams.” That is a reported problem. “The customer needs automation” is a hypothesis to test—not a confirmed requirement.
• Separate evidence from interpretation
  Keep the original signal visible before choosing a solution. Reported problem “Order exceptions take time to reconcile across teams.” Record this as the buyer's description. Ask which teams and handoffs are involved. Ask what change would make the process better. Hypothesis to test “The customer needs automation.” Do not present this as the buyer's stated need. Ask what causes the delay and what has already been tried. Check fit only after the underlying need is clearer.
• Continue with the right topic
  Assess solution fit Compare the clarified need with documented scope. Involve a specialist Route a cross-functional or unresolved question.

Solution fit

• Match the need to documented scope
  Describe fit only as far as approved evidence supports it. Start with a clearly stated customer need. Find the relevant approved solution material, compare what it documents, and identify gaps, dependencies, and unanswered questions before describing fit. The fictional examples below are practice cases for choosing a conversation stance. They are not statements about a real product or customer.
• Illustrative fit check
  Practice examples only. “Evidence to locate” means information to find in approved solution material before responding. Need and scope Need is clearly stated Approved material documents the relevant scope Matched Stance Explain the documented match Keep the explanation within what the material supports Need is clear, but a dependency or part of the scope is not Locate the documented boundary and the unresolved dependency Partial Describe the known part and name what remains open Ask a relevant specialist to assess the open point Evidence is missing or does not address the question No reliable basis for a fit statement yet Unknown Say what is not yet known Route the question before making a claim
• Make a defensible fit statement
  Write the need in the buyer's terms Keep the customer's stated problem separate from your interpretation. Check approved solution material Locate the scope or capability information relevant to that specific need. Name the boundary State which part is documented and identify any gap or dependency plainly. Route unresolved scope questions Ask a solution specialist to assess the question before making a stronger fit statement.
• Continue the conversation
  Choose proof and prepare a demo Match evidence to the need without overstating what it shows. Find specialist help Prepare a handoff for unresolved fit or scope questions.

Proof and demos

• Choose evidence for the buyer's question
  An illustration can help explain a capability; it does not by itself prove a customer-specific result. Start with the problem the buyer has described. Select approved material that addresses that question, and introduce exactly what the material demonstrates. Be clear about what it cannot establish for this buyer's situation. A focused demo answers a named question. Showing more screens or features does not make the answer more relevant.
• Plan a focused demonstration
  Use this authored planning reference to keep the session tied to a customer question. Agree on the question Before preparing the session, write one customer question the demonstration should help address. Use the buyer's language for the problem. Check that the question is within documented scope. Focus Select relevant approved material Choose only material that supports the question and is appropriate to show. Check the material's source and scope. Leave out unrelated features and unsupported claims. Select Narrate what is shown Explain the demonstrated capability without implying a result that the example does not establish. State what the example illustrates. Name relevant limits or open points. Explain Capture what remains open Record follow-up questions and identify the role needed to answer each one. Separate observed demo content from assumptions. Route unresolved fit or evidence questions to a specialist. Follow up
• Sharpen the demo
  Revisit the customer problem Check that the demonstration answers a clearly stated need. Check solution fit Review scope and identify unresolved dependencies.

Objections

• Respond to concerns without guessing
  Acknowledge the concern, clarify what is behind it, answer from approved information, and agree how open questions will be handled. You do not need to have an immediate answer to every concern. A precise follow-up is more useful than an unsupported assurance: identify the question, say what you can verify, and agree who will resolve anything still open.
• A useful response keeps the boundary clear
  Fictional dialogue for conversation practice; neither line describes a real customer's result. Useful response Buyer: “How would the handoff work across our teams?” Seller: “You’re right to ask about the handoff. Which teams need to be involved? I’ll check the documented scope before answering.” Acknowledges the concern. Clarifies what the buyer needs to understand. Commits to checking evidence, not to a particular outcome. Avoid an unsupported promise Seller: “It will work seamlessly across every team and remove the delay.” Do not promise a result that approved material does not support. Do not treat an unverified dependency as resolved. State what needs checking and identify a useful follow-up.
• Find the next answer
  Check solution fit Use documented scope to address a capability or dependency concern. Involve a specialist Route a question that needs another role to answer reliably.

Specialist help

• Involve another role when the answer needs one
  A focused handoff helps the specialist assess the actual customer question. Seek specialist input when solution fit or scope is uncertain, a question crosses business-unit boundaries, evidence needs interpretation, or a customer concern falls outside what you can confirm from approved material. Northstar's sample uses role-based routes as examples of responsibility, not as named contacts or a promise of response time. Use the appropriate verified contact route established by your organization.
• Prepare the handoff
  Summarize the customer's stated need Use the buyer's words and note which teams or work are affected. List what you checked Name the approved material reviewed and the part relevant to the question. State the unanswered question Separate the open point from assumptions and explain why it matters to the conversation. Ask for a specific decision or input Say whether you need a scope assessment, evidence interpretation, or demonstration recommendation.
• Choose a role-based route
  These responsibilities describe who may help; they do not identify individual employees. Solution specialist Ask about documented capability scope, fit, dependencies, and unresolved solution questions. Share the customer need. Include relevant material already checked. Demonstration lead Ask for help shaping a demonstration around the buyer's question and explaining what it shows. State the question the demo should address. Identify limits or open evidence questions. Business Operations content owner Route suspected errors, outdated guidance, or unclear ownership in this sample library. Identify the page and passage. Explain what appears incorrect or unclear.
• Return to the relevant guidance
  Customer problems Clarify the buyer's situation. Solution fit Check documented scope and identify gaps. Proof and demos Select relevant evidence and prepare a focused demo. Objections Handle concerns and agree on follow-up.

Customer Discovery Conversation

• Understand the problem before proposing a solution
  Northstar Foods is a fictional example. Its customer operations team reports that staff sometimes re-enter request details as work moves between teams. Use this conversation to understand what happens, when it matters, and what the customer considers a worthwhile improvement—not to pitch a predetermined answer. Keep customer-specific notes and follow-up in your organization's approved CRM process.
• A focused 45-minute agenda
  Reusable example agenda; these are facilitation time boxes, not a live workflow. Time Focus Intended output 0–5 min Opening context Shared purpose, participant roles, and permission to ask and clarify 5–20 min Understand the problem A clear account of the current process and a recent example 20–35 min Explore evidence Reported impact, frequency or scale, workarounds, and unanswered questions 35–45 min Agree the next step A corrected summary, one question to resolve, and an agreed follow-up owner and timing
• Prompts that uncover the customer's experience
  Ask one question at a time. Follow the customer's account before exploring possible improvements. Open with the current process “Could you walk us through what happens from the moment a request arrives to the point it is ready for the next team?” Ask for a recent example “Thinking about the most recent time this happened, what did each person or team do?” Explore impact and workarounds “What changed for the people involved?” and “What do you do today to keep the work moving?” Clarify scale and variation “How often does this come up, based on what you can observe?” and “Does it differ by request type or handoff?” Record estimates as the customer's estimates. Define meaningful improvement “What would be different in the work if this improved?” Let the customer describe a useful outcome in their own terms. Turn a leading question into an open one Instead of “Would an automated form solve this?”, ask “Where do details get lost or repeated, and what happens next?” The open version explores the experience without presuming a solution.
• Capture evidence without mixing it with interpretation
  Record what the customer described, what your team inferred, and what remains unknown as separate things. What to capture For each concrete example, note the situation, roles involved, sequence of events, reported frequency or scale, impact, workaround, and unanswered questions. Attribute statements to the customer or participant role rather than presenting them as independently verified facts. Recent example: which request and handoff the customer described Roles involved: who entered, checked, or received the information Impact and workaround: the effects and compensating steps the customer reported Unknowns: details to verify before drawing a conclusion Evidence Worked example: repeated request details In the fictional Northstar conversation, the customer operations lead describes a recent request whose details were entered by one team and re-entered when another team picked it up. The lead estimates that this occurs on several requests in a typical week; no measured count is supplied. Customer-reported: a recent request was entered twice during a handoff Customer estimate: the pattern occurs on several requests in a typical week Team interpretation: the handoff may not carry all needed context; this is a hypothesis, not a confirmed cause Unknown: which request types are affected and whether the estimate can be checked against an approved source Illustrative example
• Close with an agreed next step
  A useful close gives the customer a chance to correct the record and leaves both sides clear about what happens next. The conversation itself does not submit or store a record. Put customer-specific notes and follow-up in your organization's approved CRM process. Summarize what you heard State the current process, the example discussed, the reported impact, and the workaround in neutral language. Invite corrections Ask, “What have we misunderstood or left out?” Update your summary based on the customer's response. Name the question to resolve Choose one open question that would change your understanding, such as which request types are affected. Agree who follows up and when Confirm an owner and a mutually agreed timing aloud. Record the customer-specific agreement in the approved CRM process.

Proposal Pursuit Room

Hero section establishing a shared working hub for proposal teams aligning needs, win themes, and reviews.

• Proposal Pursuit Room
  A working space for bid teams aligning the customer need, proposal story, inputs, and reviews. Fictional worked example: Northstar Foods is preparing a phased distribution-planning proposal. Use this page to coordinate proposal production—not to evaluate supplier bids.
• Three practices that keep the proposal coherent
  Apply these checks before drafting expands across teams. Translate needs into evidence For each stated customer need, record the proposal response and the evidence that can substantiate it. Make each theme specific A win theme should connect a customer priority to a distinct response—not promise an outcome the team cannot support. Own every handoff Assign a responsible role, a concrete contribution, a review stage, and a reviewer to each workstream.
• Section Divider
  Worked example From customer need to coordinated response
• Build a narrative the team can support
  Northstar Foods is a fictional scenario; its needs and proposal details are illustrative. Start with the need The fictional customer wants a phased approach that connects planning across distribution sites. The team records this as a need to address, not as evidence that any specific result is guaranteed. Need: connect planning across distribution sites. Response: describe a staged planning approach and what each stage covers. Evidence: cite only approved examples, capabilities, or operating facts the team can verify. Customer need Shape a supportable win theme Illustrative theme: “One planning view, introduced in manageable stages.” It is useful only if the proposal explains what the view means, how the stages fit the customer's stated need, and which approved evidence supports the response. Tie the theme to the stated need, rather than a generic strength. Describe the proposed response in terms the delivery team can explain. Remove or qualify any claim without an identifiable source and owner. Narrative
• Worked example: contribution and review handoffs
  Illustrative stages and roles for the fictional Northstar Foods proposal; these are not commitments or service levels. Workstream Responsible role Concrete contribution Review stage Reviewer role Customer need Bid lead Summarize the phased-planning need and map each response to the relevant request text. Narrative outline Business-unit lead Solution response Solution lead Describe the proposed stages and identify assumptions that need confirmation. Draft review Delivery lead Evidence and claims Evidence owner Attach approved source references to factual claims; flag unsupported outcomes for removal or qualification. Claim check Commercial response Commercial lead Check that proposal wording matches the authorized commercial inputs for this pursuit. Final review Authorized commercial reviewer Integrated narrative Section owners Resolve terminology differences and provide complete, review-ready sections to the bid lead.
• Consolidate, check, and hand off
  Before review: confirm each section answers a recorded customer need, uses the agreed theme consistently, and names its responsible role and reviewer. Check that assumptions are visible and that the requested review stage matches the handoff in the table. Claim check example: “The approach will reduce planning time by 30%” is not ready if the team has no approved source for that figure. The bid lead routes the statement to the evidence owner: provide a verifiable source and its scope, or remove or qualify the claim before it enters the reviewed narrative. Handoff: section owners deliver review-ready contributions to the bid lead. The bid lead consolidates comments, resolves conflicting wording with the relevant workstream owner, and routes unresolved claims to the evidence owner before final review. Business Operations owns this fictional guide. Send a guide correction through the established Business Operations route; take a customer-specific proposal question to the bid lead.

Customer Reference Request

• Find the right customer reference, then ask once and ask well
  Use this page when a prospect, partner or internal team wants customer proof. The examples follow a fictional case: Northstar Systems wants Alder Works, a customer, to talk with a prospect about a phased rollout. Start by checking what Alder Works has already agreed to. Then pick the smallest reference that answers the prospect's question. Ask the account owner to coordinate the contact, so the customer hears from one person.
• Reference types and what each one needs
  Permission for one use does not automatically cover another. Approved written quote The lightest ask. A customer has already approved specific wording for specific uses. Use the approved wording exactly as recorded, with the attribution the customer chose. Check the approved channels. A quote cleared for a proposal may not be cleared for a public web page. If you need new wording or a new channel, treat it as a new request. Customer-led conversation A prospect speaks directly with a customer about their experience. Needs the customer's agreement to take part in a live conversation. A quote approval does not imply it. Agree the topics in advance and keep them to the customer's own experience. The account owner makes the introduction. Do not share customer contact details or set up the call yourself. Reference event or panel A webinar, customer panel or group session where the customer speaks to several audiences. The highest effort for the customer. Consider it only when a quote or a single conversation will not answer the question. Agree the date, format, audience and any recording or sharing with the customer in advance. Plan this through the customer reference program owner, not by direct invitation.
• Worked example: a live conversation that isn't covered yet
  Northstar Systems and its fictional customer Alder Works A Northstar solutions consultant is working with Fernbank Logistics, a fictional prospect. Fernbank asks how a similar-sized team handled a phased rollout across three sites. The consultant thinks of Alder Works, which completed one last year. What the consultant checks first Approved scope: Alder Works agreed to a written quote and case-study use. Live conversations with prospects are not listed. Contact history: the account owner's notes show Alder Works was asked to review a draft case study recently. What the consultant does Asks the account owner whether a live conversation is a reasonable next ask, given that recent request. Prepares a short request covering the topic, timing and customer effort, and routes it through the reference process. Offers Fernbank the approved written quote in the meantime. What the consultant does not do Forward Alder Works' contact details to Fernbank. Email Alder Works directly. Treat the case-study approval as permission for a call.
• Prepare the request and follow up
  Six steps from the prospect's question to the thank-you. Clarify the prospect's question and audience Write one sentence: who is asking, what they want to know, and by when. "How did a three-site team sequence its rollout?" is a better brief than "a reference for a logistics prospect". Choose the narrowest useful reference Try an approved written quote first. Move to a conversation or event only if the quote does not answer the question. Check existing permission and contact history Look up what the customer has approved, for which uses, and when they were last asked for anything. Record anything you cannot confirm and raise it with the account owner. Summarize topic, timing and customer effort State the topics you will ask about, the topics you will not raise (such as pricing or contract terms), the proposed dates and how much of the customer's time it takes. Route through the account owner and the reference process Submit through the organization’s authorized reference-request route. The account owner contacts the customer. Do not contact the customer yourself while the request is open. If the route is unclear, ask the account owner or reference-program owner before contacting the customer. Record the outcome and thank the customer Log the result in the system your reference program uses, including any new or declined permission. The account owner or program owner sends the thank-you. Do not make a new ask until the account owner confirms the next step.
• Example request summary
  A sample for the Alder Works scenario. This is the level of detail a request needs. Request field Sample entry Prospect and question Fernbank Logistics asks how a similar-sized team handled a phased rollout. Reference needed Customer-led conversation, 30 minutes, one customer speaker. Existing permission found Written quote and case-study use approved. Live conversations not listed. Proposed topics Rollout sequencing across three sites. Not pricing, contract terms or security details. Timing Any weekday within the next three weeks; the customer chooses the slot. Effort for the customer One call, plus a short briefing from the account owner beforehand. Who is involved Requesting solutions consultant. Account owner copied and leads customer contact.
• Submit a customer reference request
• Who to ask for help
  Owns the relationship with the customer Account owner Account management. Ask about contact history and whether a new ask is sensible. Coordinates approved references and events Customer reference program owner Customer advocacy. Ask about permissions on record and reference formats. Keeps this page accurate and current Page owner Business Operations. Report unclear guidance or outdated steps.