Module 1: The B2B Landscape

How Complex B2B Deals Differ

Selling a phone to a consumer and selling a fleet management system to a logistics company are both "sales", but they are very different activities. In business-to-business (B2B) selling, especially for larger deals, you are selling to an organisation rather than a person, the stakes are higher and the process is longer and more structured. Salespeople who succeed in simple sales often struggle in complex ones because they apply the same habits: pitch quickly, push for a close, move on. This lesson explains what makes complex B2B deals different and what that means for how you sell.

Key differences

What this means for you

1. Diagnose before you prescribe. In complex sales, the customer often has not fully defined the problem. Your value lies in helping them understand it, including its cost and causes, before proposing a solution.
2. Sell to a group, not a person. You must understand and influence everyone involved in the decision, including people you may never meet directly.
3. Reduce risk. Buyers worry about choosing wrongly. References, pilots, clear implementation plans and contract terms all reduce perceived risk.
4. Manage the process. Complex deals stall without a shared plan. You help the buyer navigate their own internal steps.
5. Think long term. The first deal is often the beginning. How you behave during the sale shapes the relationship for years.

Worked example

Wanjiru has been selling payroll software to small businesses with five to twenty staff. A typical deal involves one meeting with the owner and a decision within a week. She is now assigned to larger clients and starts working with a hypothetical manufacturing company with 800 employees across three sites in Nairobi, Thika and Mombasa.

She approaches it the way she always has: a demo to the HR manager, a proposal and a follow-up call. The HR manager is enthusiastic, but nothing happens for two months. When Wanjiru asks why, she learns that:

• The finance director must approve any spend of this size and is worried about migration risk at year end.
• The IT manager has concerns about data security and integration with the existing accounting system.
• Procurement requires three competing quotes and supplier registration documents.
• The managing director wants to understand how the system will reduce payroll errors that caused staff complaints.

Wanjiru resets her approach. She asks the HR manager to help her meet the finance director and IT manager, prepares a migration plan timed after the year-end close, answers the security questionnaire, quantifies the cost of payroll errors with the HR team, and registers as a supplier. The deal takes five months, but it closes, and the client later adds the HR module.

Common mistakes to avoid

• Pitching too early. A demo before you understand the problem wastes the best chance to show insight.
• Relying on one contact. If that person leaves or loses influence, the deal dies.
• Ignoring the formal process until the end, then being surprised by procurement or legal requirements.
• Discounting to speed things up. Price is rarely the reason a complex deal stalls; unresolved risk or unclear value usually is.
• Treating the close as the finish line. Implementation and adoption determine whether you will grow the account.

The rest of this course gives you the tools to handle each of these differences: understanding long cycles, buying committees, account planning, stakeholder mapping, business cases, pilots, procurement and expansion.