A complex B2B sale is one where no single person can say yes alone. Multiple stakeholders — with different roles, different priorities, and different definitions of success — must collectively agree before the purchase is made. The selling organisation must satisfy not one buyer but a buying committee, each member of which has different concerns, different evaluation criteria, and different levels of urgency.
The skills required for complex B2B sales are fundamentally different from transactional or SMB sales. Speed and enthusiasm are not the primary variables. Patience, strategic thinking, stakeholder management, and qualification discipline are. Reps who succeed in complex B2B environments are the ones who can hold a multi-thread strategy across months, navigate internal politics they can never fully see, and maintain momentum in the face of the extended timelines and repeated stalls that characterise the segment.
---
---
MEDDPICC is the qualification and navigation framework for complex B2B sales. Each element maps to a specific challenge in the complex sale:
Metrics: In a deal with multiple stakeholders, different stakeholders care about different metrics. The EB cares about ROI and payback period. The Champion cares about the specific outcome their team achieves. The IT stakeholder cares about implementation time and integration complexity. Map the relevant metric to each stakeholder — not just to the champion. Economic Buyer: The EB in a complex sale is often not in the early conversations. They're busy, senior, and have delegated the evaluation to the champion. Getting to the EB is the central challenge of complex B2B sales — and the single most important multi-threading objective. Decision Criteria: In a committee buying process, decision criteria are often inconsistent across stakeholders. The champion's evaluation criteria and the procurement team's evaluation criteria may be entirely different. Map criteria by stakeholder and identify where alignment exists and where conflicts need to be resolved. Decision Process: The formal decision process (RFP, POC, shortlist, approval workflow) and the informal decision process (which stakeholder's recommendation carries the most weight, who can veto, who has the strongest relationship with the EB) are both critical to map. Identify Pain: Each stakeholder has a different pain. The VP Sales' pain is forecast accuracy. The CRO's pain is missed revenue targets. The RevOps manager's pain is CRM data quality. The business case must address the pain that matters to each stakeholder — not just the champion's pain. Champion: As discussed in the multi-threading article — a single champion is a vulnerability. In a complex sale, the champion must be developed into a genuinely powerful internal advocate, and secondary champions should be identified as backup. Competition: In formal evaluation processes, competitive positioning is explicit. Understand who else is being evaluated, what criteria they're strong on, and where your specific differentiation is most compelling for each stakeholder. Paper Process: In complex B2B sales, the paper process can add 60–120 days to the cycle after verbal agreement. Map it at Stage 2, not Stage 4.---
RFPs are time-consuming and completion does not guarantee a fair shot. Before investing heavily in an RFP response, determine:
- Were you involved in the RFP process before it was issued? (The vendor who helps shape the RFP criteria is at a significant advantage.)
- Is this a genuine open evaluation or a compliance exercise for a decision already made?
- Do you have a champion who is actively advocating inside the evaluation?
- Can you get a meeting to present rather than just respond in writing?
If the answer to most of these is no, the ROI of a full RFP response is questionable. A focused, differentiated partial response is often more effective than a comprehensive response that matches the same format as every other vendor.
Proof of Concept managementA POC is an opportunity — but only if it's structured well. Negotiate the POC criteria before it starts:
- What specific outcomes would constitute a successful POC?
- Who are the users involved and what is their evaluation mandate?
- What is the timeline and the decision process after the POC?
- Is there a champion within the POC team who is actively advocating for a positive outcome?
A POC without defined success criteria is an open-ended trial that can be extended indefinitely. Define success before you start.
---
Complex B2B deals lose momentum over extended timelines. Managing momentum requires a proactive cadence:
Maintain weekly or bi-weekly contact. Silence from the vendor reads as lack of urgency. Even brief touchpoints — a relevant insight, a reference customer connection, a check-in ahead of an internal milestone — maintain presence. Use the MAP to create internal milestones. A Mutual Action Plan shared with the champion creates a shared timeline that both sides have committed to. Each milestone reached is a momentum signal. Each milestone missed is a discussion — which is better than silent drift. Provide value between selling moments. The rep who sends a relevant article, introduces a useful peer connection, or shares an insight that helps the champion in their role is building relationship capital that pays out at the decision moment. Re-qualify at 30-day intervals. In long cycles, circumstances change. The budget that was available in Q1 may be frozen in Q3. The champion who was driving the initiative may have been reassigned. Re-qualifying the deal's fundamental elements — pain, compelling event, EB support — at regular intervals prevents the deal from drifting in an unhealthy direction invisibly.---
Complex B2B deals rarely close on a single call. The close is the culmination of a process — a mutual action plan that has been followed, a business case that has been built collaboratively, and a decision process that the rep has mapped and navigated. When all of those elements are in place, the formal close is the natural end of a well-run process, not a high-stakes moment that depends on closing technique.
The conditions for a confident close:
- EB is engaged and has confirmed the business case
- Decision criteria are explicitly agreed and the vendor scores well against them
- Decision process is fully mapped and all required approvals are in sight
- Champion is actively advocating and has recently confirmed internal support
- Paper process is underway — legal and procurement are engaged
- Compelling event is live and the close date is tied to a specific business reason
If all six conditions are met, close with confidence. If any are missing, address the gap before asking for the close — because a close attempted without these elements produces "we need to think about it," not a signature.
---
Brazn's MEDDPICC tracking provides real-time visibility into every element of the complex deal — surfacing gaps, monitoring multi-thread coverage, tracking stakeholder engagement, and providing the manager with objective deal quality data that makes pipeline reviews genuinely useful. In complex deals where the sales cycle is 6+ months, Brazn's deal intelligence is the consistent thread that connects every interaction to the qualification picture — preventing the amnesia that affects long-cycle deals where individual call details are lost between conversations.
---
---
Contract negotiation is the stage of the SaaS sales cycle where deals most frequently slip, shrink, or collapse — not because the parties can't reach agreement, but because the process is poorly managed. Legal reviews take longer than expected. Redlines arrive without context. Each revision cycle adds days. And the rep, who has limited legal knowledge and a quota deadline, is caught between a prospect's legal team asking for positions the rep doesn't understand and a legal team that has different priorities than closing this quarter.
Navigating contract negotiation well requires understanding which contract elements are standard and which are genuinely negotiable, how to manage the process to minimise cycle time, and how to protect deal economics while giving the prospect a commercially reasonable agreement.
---
A standard SaaS subscription agreement contains:
Subscription terms: What the customer is buying, for how long, at what price, and the renewal terms (auto-renew provisions, notice periods, price escalation caps). Acceptable use policy: How the customer may and may not use the product. Data processing agreement (DPA): How customer data is processed, stored, protected, and what happens to it at contract end. This is the section most likely to require attention from the prospect's legal and privacy teams. Service level agreement (SLA): Uptime commitments, response time for support issues, and the remedies (typically service credits) available if SLAs are missed. IP ownership: Who owns the data generated by use of the product; who owns any custom configurations or integrations built for the customer. Limitation of liability: The cap on each party's financial liability, typically expressed as a multiple of annual contract value. The most frequently negotiated commercial term. Indemnification: The circumstances under which each party indemnifies the other for specific categories of loss. Termination provisions: The conditions under which either party can terminate, the notice period required, and what happens to data and access on termination.---
Understanding which positions are fixed and which have flexibility prevents the rep from either conceding unnecessarily or stonewalling on standard requests:
| Term | Vendor Position | Negotiability |
| --- | --- | --- |
| Subscription price | List price or approved discount | Flexible within discount authority |
| Contract length | Annual standard | Flexible — longer terms for better pricing |
| Payment terms | Annual upfront | Often negotiable for enterprise — quarterly available |
| Auto-renew notice period | 30–60 days standard | Occasionally extended for enterprise |
| Price escalation cap | CPI or fixed % | Sometimes negotiable |
| Liability cap | 12 months ACV | Commonly negotiated up for enterprise |
| SLA credits | Service credits only | Rarely negotiable — termination right after repeated misses more achievable |
| Data residency | Default region | Available as contractual commitment if infrastructure supports it |
| Custom DPA terms | Standard DPA | Typically addendum-based; GDPR standard clauses available |
---
- Accept: The change is reasonable and doesn't affect commercial value.
- Counter: The change requests more than is needed — offer a middle position.
- Decline with explanation: The position is not commercially viable for a specific reason.
- Escalate: The change requires legal or executive input before responding.
Responding to every redline individually in the same category wastes cycles. Batch responses by category.
Direct legal-to-legal for technical positions. For genuinely technical legal positions — data privacy regulatory compliance, IP ownership specifics, indemnification scope — rep-mediated discussion is slow and error-prone. Connect the legal teams directly with the champion facilitating. A 30-minute call between legal teams resolves in one session what might take three weeks of written exchange. Use the MAP to create legal accountability. The Mutual Action Plan should include the legal timeline with named owners and dates. When legal review is on the MAP, both parties have visibility into the timeline — and slippage is discussable.---
The vendor's standard position is 12 months of subscription value as the liability cap. Enterprise procurement teams routinely request unlimited liability or caps significantly higher. The middle ground most SaaS vendors can accept: liability cap = 2–3× annual contract value for general claims, with specific carve-outs (IP infringement, data breach, wilful misconduct) at a higher cap or uncapped.
Data processing and GDPRFor EU/UK customers, the DPA must comply with UK GDPR and EU GDPR. Most SaaS vendors have a standard GDPR-compliant DPA. The prospect's legal team may want to negotiate specific clauses — data retention periods, sub-processor notification, audit rights. Most of these can be addressed without material change to the vendor's data infrastructure.
Auto-renew provisionsProcurement teams frequently push to remove or lengthen the auto-renew notice period. A 60-day notice period (standard) becoming a 90-day notice period is typically acceptable. Removing auto-renew entirely creates administrative burden for both parties and is usually unnecessary if the notice period is reasonable.
Termination for convenienceEnterprise buyers often request termination for convenience — the right to exit the contract without cause on [X] days' notice. For annual contracts, this is commercially problematic for the vendor. The middle ground: termination for convenience after a defined minimum subscription period (e.g., 6 months into a 12-month contract), with the remaining subscription value payable on termination.
SLA remediesBuyers request service credits for SLA misses but occasionally push for termination rights. Service credits for individual incidents are standard. Termination rights are typically available only for material, repeated, uncured SLA failures — a specific threshold (e.g., three consecutive months below the SLA level) is a reasonable compromise.
---
---
Brazn tracks the Paper Process element of MEDDPICC through the negotiation phase — monitoring timeline adherence, flagging stalled legal review, and providing the manager and CRO with visibility into contract negotiation status across all late-stage deals simultaneously. Deals where the legal process is taking longer than the historical team median are surfaced for intervention — enabling the executive sponsorship plays and direct legal engagement that accelerate resolution.
---
####
Book a demo to see how Brazn AI fits into your sales stack.
About the Author
Alex Margarit, Sales AI Expert, SaaS Sales Leader, BMC, ServiceNow, Docusign — 25+ years in SaaS sales.