Brief procurement and legal before the negotiation starts, not after the vendor sends paper. The brief should give them three things: the commercial targets and walkaway, the specific clauses that must change, and a clear map of who decides what. A negotiation stalls when legal sees the contract for the first time the week before signature, because that is when avoidable risk turns into avoidable delay. This is part of our ITSM procurement playbook.
Book a contract negotiation review.
$420M+ negotiated across 500+ engagements. We align procurement, legal, and IT before the vendor sets the agenda. Fixed fee or gainshare.
Book a contract negotiation review →Why brief procurement and legal early?
Vendors win on speed and on dividing your side. If procurement does not know the technical priorities and legal has not seen the clauses, the vendor sets the timeline and picks off each function separately. A single brief, shared before first contact, keeps your side aligned and stops the vendor from quoting one story to IT and another to procurement. It also means legal raises its red lines while there is still time to negotiate them.
Do this next: draft a one-page brief and circulate it to procurement, legal, and the IT owner before the first vendor call.
What goes in the brief?
| Section | What it contains | Why it matters |
|---|---|---|
| Commercial targets | Target price, walkaway, uplift cap, term length | Procurement negotiates to a number, not a feeling |
| Clause red lines | Audit, liability, data, auto-renewal, exit | Legal flags issues while they are still negotiable |
| Scope and seats | Reconciled seat count, tier, AI usage | Stops the vendor quoting off an inflated baseline |
| Decision rights | Who approves price, terms, and signature | The vendor cannot split your side or find a soft approver |
| Timeline | Renewal date, notice window, internal approvals | You control the clock instead of the vendor |
What is the step-by-step?
- Reconcile the estate first. Bring procurement a true seat count and AI usage so they are not negotiating the vendor's inflated number.
- Set targets and walkaway. Agree the price target, uplift cap, and the point at which you walk, in writing.
- Give legal the clauses early. Flag audit, liability caps, data and exit terms now, so red lines are known before paper arrives.
- Map decision rights. Write down who approves price, who approves terms, and who signs, so the vendor cannot route around the hard approver.
- Agree the single channel. Decide who talks to the vendor and route everything through them, so your side speaks with one voice.
Who owns which decision?
Ambiguity here is where deals slow down and leverage leaks. IT owns scope and technical fit, procurement owns commercial terms and the competitive process, legal owns risk and the clause language, and a named executive owns the final trade-offs. The full mapping is in our pillar on who owns the ITSM renewal: roles, RACI, and decision rights, and the leverage side of the RFP is in how to write an ITSM RFP that creates real price leverage.
Do this next: write a one-line RACI for the deal so every function knows whether it is responsible, accountable, consulted, or informed.
Our contract terms guide gives legal a ready list of the clauses worth fighting for.
How do you keep the brief alive during the deal?
A brief written once and filed is worthless. The vendor will move the goalposts: a new bundle, a deadline, a sweetener aimed at one function. Keep the brief live by reviewing it at each phase and updating the targets as you learn. When the vendor introduces something that was not in scope, the brief is the test: does this move us toward the agreed targets, or is it a distraction aimed at a single approver?
Hold a short internal sync before every vendor milestone so procurement, legal, and IT walk in aligned. Fifteen minutes of alignment beats an hour of cleanup after a function commits to something the others did not agree.
Do this next: schedule a recurring 15-minute internal check-in tied to each vendor milestone for the length of the deal.
What does a single vendor channel look like in practice?
One person, usually in procurement, owns all outbound and inbound vendor communication on commercial matters. Technical clarifications can flow between IT and the vendor's engineers, but anything touching price, scope, or terms routes through the channel. When the account team emails the executive sponsor directly with a "special offer," the sponsor forwards it to the channel and does not reply. This feels rigid; it is the point. The discipline denies the vendor the ability to find the fastest yes.
Tell the vendor who the channel is in writing at the start. A vendor that keeps going around it is telling you something about how the relationship will run after signature. The full role map is in our pillar on who owns the ITSM renewal.
Do this next: name the channel in your first email to the vendor and ask them to confirm they will route commercial discussion through it.
What does a one-page brief actually look like?
Keep it to a single page so people read it. Five short blocks do the job: the deal in one line (what is renewing, when, and the current spend); the commercial targets (price target, uplift cap, term, and the walkaway); the clause red lines (audit, liability, data, auto-renewal, exit); the scope (reconciled seats, tier, AI usage); and the decision rights (who is accountable for each call, and who owns the vendor channel). Anything longer becomes a document nobody opens at the moment it matters.
Date it, version it, and circulate it before the first vendor contact. When the deal shifts, update the page rather than starting a new thread, so there is always one current source of truth your whole side works from. The clause detail to populate the red-lines block is in our contract terms guide.
Do this next: draft the five-block one-pager today and send it to procurement, legal, finance, and the IT owner before any vendor call.
What to do next
Write the brief, reconcile the estate, give legal the clauses early, and map decision rights before the first vendor call. When you want a buyer-side team to run it, the engagement goes through our contract negotiation service on fixed fee or gainshare.
Frequently asked questions
- What should an ITSM negotiation brief include?
- Commercial targets and walkaway, the clause red lines for legal, a reconciled seat count and AI usage, a clear map of decision rights, and the timeline with the renewal date and notice window.
- When should legal get involved in an ITSM deal?
- Before the vendor sends paper. Giving legal the audit, liability, data, and exit clauses early means red lines are negotiated while there is still time, not discovered the week before signature.
- How does a brief stop the vendor dividing our side?
- By agreeing one channel to the vendor and clear decision rights up front, so the vendor cannot tell IT one story and procurement another or route around the hard approver.
Book a contract negotiation review.
We align procurement, legal, and IT before the vendor sets the agenda. Fixed fee or gainshare.
Book a contract negotiation review →