You Don't Need to Be Technical to Win
The most expensive misconception in enterprise software buying is that IT contract negotiation belongs to the technologists. It does not. The terms that decide whether a deal is good or ruinous — the discount, the renewal uplift cap, the audit clause, the exit rights — are commercial questions a CFO or procurement leader is far better equipped to judge than an architect. Vendors benefit when the conversation stays technical, because technical complexity is where their information advantage lives. A non-technical executive who keeps the negotiation on commercial ground — cost, risk, optionality — is negotiating on home turf. Everything in our negotiation handbook is accessible without a technical background; what it requires is the discipline to ask the right commercial questions and refuse to be hurried past them.
Five Questions Every Executive Should Ask
You can lead a software negotiation with five questions, none of which requires technical depth. First: what is the all-in annual cost, including support, uplifts and platform fees? — not the headline price, the effective price. Second: what do comparable organisations actually pay? — the benchmark, because list price is a fiction and real discounts for enterprise deals commonly run from around 23% off list to far deeper. Third: what happens at renewal? — specifically, the cap on price increases, where uncapped uplifts of 5% to 25% are routine. Fourth: what does it cost to leave? — the exit and data-portability terms that determine whether you have any future leverage. Fifth: what are we actually using? — because with the average enterprise running over 300 applications and tens of millions in SaaS spend, a large share is typically unused.
These five questions reframe the negotiation around value and risk rather than features, and they expose the areas where money is most often lost. The benchmark question in particular is the spine of the whole effort — without it every other answer floats free — and it is worth understanding properly through our guide to IT contract benchmarking. An executive who insists on clear answers to all five, in writing, has already out-prepared most buyers.
Judge Total Cost of Ownership, Not Sticker Price
The number on the first page of a proposal is the least important figure in it. What matters is total cost of ownership over the full term: licence or subscription fees, mandatory support (often 18–22% of licence value annually for on-premise software), implementation, training, integration, and the renewal uplifts compounding across years. A deal with an attractive Year 1 price and an uncapped 10% annual uplift is more expensive over five years than a higher headline price with a 3% cap — and the vendor structures proposals knowing most buyers anchor on Year 1. Modelling the full-term cost, and the cost of the realistic alternative, is the analysis that actually decides whether a deal is good. It is squarely a finance skill, which is why the CFO belongs at the centre of it, supported by the governance discipline in our CIO Contract Governance white paper.
| What the Vendor Shows | What the Executive Should Model |
|---|---|
| Year 1 headline price | All-in cost across the full term |
| Discount off list | Effective price vs peer benchmark |
| "Standard" renewal terms | Capped uplift and exit cost |
| Licences proposed | Licences actually used |
Two Cardinal Rules: Budget and the First Quote
Two rules protect every software negotiation, and both are commercial instincts a seasoned executive already has. The first: never reveal your budget. The moment a vendor knows your number, every proposal converges on it, and any "discount" is theatre performed against a price they set to your ceiling. Keep the budget confidential and make the vendor compete against the benchmark and the alternative instead. The second: never accept the first quote. A vendor's opening proposal is calibrated to the top of their achievable range, and buyers who accept it without counter-negotiating consistently overpay relative to comparable organisations. These are not technical insights; they are negotiating fundamentals, and they matter most precisely when the subject matter feels unfamiliar and the temptation to defer to the vendor is strongest.
The two rules that protect every IT deal are commercial, not technical: never reveal your budget, and never accept the first quote. The vendor relies on you forgetting both when the subject feels over your head.
Build the Cross-Functional Team
A non-technical executive should not negotiate alone, but nor should they hand the deal to IT. The strongest position is a small cross-functional team: finance to own the commercial model, IT to validate what is genuinely needed, procurement to run the process, and legal to hold the terms — with a single empowered lead who speaks to the vendor. This structure does two things. It ensures every dimension of the deal is covered by someone competent to judge it, and it denies the vendor the chance to exploit disagreement between your people in the room. Vendors are trained to find and widen internal gaps, which is why aligning the team before engagement — the subject of our guide to multi-stakeholder negotiations — is as important as anything said at the table.
The role of the technical members is specific and bounded: tell the team what the organisation genuinely needs, and confirm whether the vendor's claims about features, integration and effort are accurate. That is invaluable, and it is different from owning the negotiation. The risk in handing the deal to IT is not competence but incentive — technologists are naturally drawn to capability and continuity, and a vendor will happily reframe a commercial negotiation as a technical one to move the conversation onto ground where the buyer concedes more easily. Keeping a non-technical lead in charge, with IT advising rather than deciding, holds the deal where it should be: on cost, risk and optionality. The executive does not need to understand the architecture; they need to make sure someone trustworthy does, and that the commercial decision remains theirs.
Where Your Leverage Actually Lives
Your leverage as an executive comes from three sources, none of them technical. The first is information — a benchmark and a clear-eyed read of the contract, the discipline of reading the clauses that matter. The second is optionality — a credible alternative and a real willingness to walk, which is what converts every other argument into pressure. The third is timing — engaging early enough to use the vendor's calendar rather than be trapped by your own, where buyers who start well ahead of renewal capture far better outcomes than those who begin under deadline. An executive who controls information, optionality and timing is negotiating from strength regardless of how the technology works. That is the whole point: the deal is won on commercial ground, and commercial ground is yours. To bring an experienced negotiating team alongside your executives on a live deal, request a confidential briefing.