People-first sales: solve the problem before pitching the product

Your buyer does not owe you your quota. They have work to finish, commitments to keep and problems competing for attention. A product deserves a place in that picture only if it helps. People-first sales starts there: understand the person and the problem before deciding what to recommend, including whether to recommend anything at all.

This is not a softer script for pushing the same deal. It is a practical discipline for discovery, outreach and follow-up. The seven principles below adapt a People-First Sales coaching playbook into an enterprise-selling approach. Public guidance on customer collaboration and active listening provides supporting techniques, not proof that this particular framework increases sales.[1][2]

1. Swing the club. Research and preparation matter, but they cannot tell you everything a buyer will say. Take the smallest useful action that tests your understanding: ask one relevant question, share a short example or invite someone to correct your view of their process. The aim is to learn, not to maximise messages sent. A thoughtful conversation that disproves your assumption is more useful than another week polishing a pitch around it.

2. Put people and problems before the product. Imagine an operations manager at a large retailer dealing with last-minute schedule changes. This is a fictional example, not a customer account. Starting with “our AI optimises workforce allocation” assumes both the problem and the answer. Start instead with: “Walk me through what happens when someone calls in sick. Where does the process become difficult?” The trouble might be approvals, missing information or unclear responsibilities rather than scheduling itself.

Ask how the work happens today, what breaks, who is affected and what has already been tried. Then check your understanding: “You said changes get lost between the spreadsheet and team messages, leaving supervisors to chase confirmations. Is that the main issue?” Use that recap only if the buyer actually said it. Salesforce’s relationship-selling training distinguishes clarifying questions, which invite elaboration, from confirming questions, which check understanding.[1] Neither is an invitation to steer someone towards a pain they do not have.

3. Translate technology into human value. A feature describes what a product does. Value describes a change someone cares about. For the fictional manager, the desired outcome might be fewer evenings spent chasing replies, more predictable staffing costs or greater confidence that a change reached the right person. Ask which matters. Do not assume that the person operating the system, the finance lead and the executive sponsor want exactly the same thing.

Use four lenses to prepare questions: time, finances, recognition or connection, and confidence or peace of mind. These are conversation prompts, not a scientific taxonomy or an exhaustive account of why people buy. Connect a verified problem to an outcome and then to evidence. If you cannot support a promised saving, propose a way to measure it. A baseline and a limited trial are more honest than a confident return-on-investment number invented for the proposal.

4. Find the painkiller before selling the vitamin. A problem can be real without being urgent. Ask what happens if nothing changes, whether there is an actual deadline and what else competes for attention. A recurring failure before a busy trading period is a different buying situation from a mildly inconvenient report. Let the buyer establish the consequence. Do not turn your quarter-end into their emergency or manufacture scarcity to make a low-priority purchase feel necessary.

5. Let trust accumulate through behaviour. Keep small promises. Send the document when you said you would. Distinguish an available capability from a roadmap item. Admit when the product cannot meet a requirement. Treat a concern as information rather than resistance to overcome. Harvard’s Program on Negotiation describes active listening through paraphrasing, inquiry and acknowledgment, and stresses that acknowledging a concern does not mean agreeing with it.[2]

For example, “too expensive” could mean an unavailable budget, unclear value, implementation risk or a competing option. Those are possibilities, not a diagnosis. Ask: “What makes the price difficult to justify in your situation?” Then respond to the answer with evidence or a clear limitation. If there is no fit, a respectful exit is a valid outcome. People-first selling does not require endless free consulting or pretending that commercial disagreements do not exist.

6. Be useful before asking for commitment. Offer something relevant and small: a process checklist, a worked example or an introduction made with permission. It should still be useful if the person never buys. In the fictional scheduling scenario, an opening could be: “When a shift changes at short notice, how do supervisors confirm everyone has seen the update? I have a short checklist for mapping that handoff. Would it be useful?” Only offer the checklist if you actually have one. Do not invent conversations with similar companies as social proof.

Follow-up should add a reason to reply, not an obligation. After a real discussion about missed handoffs, a message might say: “You mentioned that confirming changes is harder than creating the schedule. Here is the handoff checklist I promised. Is the approval step the right place to start?” Send the resource, preserve the buyer’s actual words and make a reply optional. If they decline or opt out, stop. Relevance is not permission to keep contacting someone indefinitely.

7. Keep your quota out of the buyer’s business case. Targets belong in your planning, not in the explanation of why someone should purchase. Ask for a next step because it resolves a shared question: reviewing one workflow, involving the budget owner or agreeing what a trial must demonstrate. Be explicit about scope, effort and responsibility. If the offer solves no important problem, better closing language will not create one.

Before the next call, write down the buyer’s role, your problem hypothesis and what would disprove it. During the call, explore the current process, consequences, timing, desired outcome and people affected. Summarise what you heard before showing features. Afterwards, record what is confirmed, what remains uncertain and the next step both sides actually agreed. “Interested” is not the same as a verified need or a commitment.

Practice in short sessions: choose a plausible buyer, write open questions, draft a useful message and role-play an objection. Review whether you listened, checked assumptions, linked value to evidence and respected a no. Track problems verified, commitments kept and useful next steps alongside commercial outcomes. Activity volume alone cannot tell you whether you helped anyone make a better decision.

Scope and sources: this is practical analysis adapted from a coaching playbook, not a controlled study or a promise of higher conversion. All buyer situations and sample messages are fictional. The Salesforce material supports the distinction between clarifying and confirming questions; the Program on Negotiation article supports the listening techniques.[1][2] Neither independently validates the seven-principle framework or the four value lenses.