top of page
Search

Commercial Negotiation: My Top 5 Lessons on getting a great technology deal

Writer: Chris Gracie
Chris Gracie
2 hours ago
8 min read

You’ve chosen the software. You’ve chosen the vendor. Everyone is keen to get started.

Or perhaps the system is already live, and you need to put support, maintenance, managed services or ongoing development arrangements around it.


Either way, you’ve reached the point where everything promised during procurement needs to become something both parties can actually deliver. I’ve negotiated complex, multi-million-dollar technology agreements on behalf of customers. I’ve also had to work with those agreements afterwards, through implementation, change, go-live and ongoing support.


Having to work with these contracts after signing has taught me what to look out for!


The clauses that seem the most important around the negotiating table aren’t always the ones you’ll rely on every week. And some of the things that can feel like minor details during negotiation become incredibly important six months later when there’s a change request, production incident or disagreement about who was supposed to do what.


So in this article I’m sharing five things experience has taught me to focus on: what you’re actually buying, where the commercial boundaries sit, how you’ll work together, who owns what, and what happens when things go wrong.


But first, there’s an important question.


First, what kind of negotiator are you?



I’ve worked with a few different approaches to negotiation.


There’s the Competitor: win every point, squeeze every last dollar out of the supplier and make sure they know who’s boss.

There’s the Compromiser: let’s split the difference and meet in the middle.

There’s the Accommodator: you care more about this than I do, so you can have it.

And there’s the Collaborator: how do we both walk away with a deal that works?


Collaboration is my style.


I want the best possible deal for my customer, but I also want the supplier set up to succeed. That means pushing hard on the things that matter, understanding what’s driving the other side’s position, and giving ground where it makes sense.

I take that approach because most technology negotiations aren’t one-off transactions. Signing the contract is the beginning of the relationship, not the end.Many of the agreements I work on create relationships that will last five years or more. Winning every clause can be a pretty hollow victory if you then need the same supplier to implement, support and continually improve a business-critical system.


And if collaboration doesn’t work? Well, you can always become the Competitor later!


What are you actually negotiating?

There are several several components or areas your commercial deal needs to cover. Depending on the relationship, you might be negotiating an MSA setting the overarching commercial and legal terms, an implementation SOW defining what will actually be delivered, and software licence or subscription terms covering how the product can be used and how much it costs.


Technology contracts are usually broken up into multiple agreements, like:

  • Master Services Agreement (MSA): The overarching commercial and legal rules for working together.

  • Implementation Agreement / Statement of Work (SOW): What is being delivered, responsibilities, timing, acceptance and cost.

  • Software Licence / Subscription: What software you can use, how you can use it, pricing and renewals.

  • Roadmap Development / Additional Projects: How future enhancements will be scoped, estimated, prioritised and approved.

  • Support & Maintenance: How the live solution is supported and maintained, and what's included versus separately chargeable.

  • Managed Services: What the supplier is responsible for operating and managing on an ongoing basis.

  • Service Levels: How performance is measured, including availability, severity, response and restoration or resolution targets.

  • Security, Privacy & Data: How your information is protected, where it can be held, who can access it and what happens to it when the relationship ends.


You don’t need a separate agreement for each of these. I’ve seen them structured plenty of different ways, often with an MSA supported by SOWs and schedules. Don't get hung up on how many documents there are. Focus on whether all of the important areas are covered, the boundaries are clear, and the agreements actually work together.


There’s also something else experience has taught me: timing matters.


Before you start: negotiate while you still have leverage

The easiest negotiations I’ve been involved in are the ones where there is still time to negotiate.


Your strongest commercial position is generally before you’re committed to starting.

Once the vendor has been selected, the project team mobilised, internal communications have gone out and an executive has a go-live date in their calendar, the dynamic changes.

I’ve seen unresolved points quickly move from “we need to sort this out before we sign” to “can we just deal with this later?” That pressure is understandable; Nobody wants a contract discussion holding up a project. But “later” usually means you have less leverage.


The same applies after go-live. Once a supplier is supporting a business-critical system that your organisation relies on every day, your practical alternatives become much narrower.

So give yourself enough time to negotiate properly while you still have choices.

Then I concentrate on five things:


1. Be absolutely clear about what you're buying

You'd think this would be the easy bit. Surprisingly, it's left unclear far more often than it should be.


I ask a very simple question:

Can both sides point to the same documents and say, “That’s what we’ve agreed to deliver”?


If we can’t, I don’t think we’re ready to sign.


That doesn’t mean squeezing hundreds of detailed requirements into the legal agreement. I’m perfectly comfortable with requirements, designs, solution documentation and other project artefacts sitting elsewhere.


What matters is that the agreement tells us which documents define what we’re buying and, ideally, what takes precedence if two of them contradict each other.

Then I ask another question: How are we going to know when it’s actually been delivered?


I’ve learned to pay close attention to acceptance. What are we testing against? Who accepts the deliverable? How long does the customer have to test it? What happens when something fails? What constitutes a material defect? Because if we don’t agree what “done” means during the negotiation, we’re probably going to negotiate it later. And negotiating “done” after the work has been completed and the invoice has arrived is considerably harder.


2. Know what's included and what costs extra

Some of the most expensive arguments in technology contracts start with innocent questions during the project's delivery. Do any of these sound familiar?

  • Is this a defect or an enhancement?

  • Is this support or consultancy?

  • Is this BAU maintenance or roadmap development?

  • Is this included scope or a change request?

  • Is this the customer's responsibility or the supplier's?


I've negotiated agreements and then had to deliver under them. That's taught me how important these definitions become in practice. At the negotiating table, the distinction between a defect and an enhancement can feel academic, but six months later, when there's a $50,000 change request attached to that definition, it doesn't feel academic anymore.


Defining what's chargeable is also only half the job. You also need to understand how much it can cost.

  • How can day rates increase?

  • What happens to subscription and support charges?

  • How are hosting-cost increases passed through?

  • Is there a CPI mechanism?

  • How frequently can pricing change?

  • Is there a cap?

  • What evidence does the supplier need to provide to support an increase?


These mechanics need to be clear and simple. If you don't define what's included, what costs extra and how those costs can change upfront, you'll probably negotiate them later with considerably less leverage.


3. Write down how you'll actually work together

This gets missed all the time! A huge amount of effort goes into negotiating price, liability, intellectual property and termination rights. Then everyone signs the contract, starts work and things get chaotic because nobody has properly agreed how the relationship will actually operate.


For an implementation, define how you'll handle:

  • change requests

  • estimation and approval

  • acceptance

  • decision-making

  • reporting

  • escalation.


For support and managed services, define:

  • how incidents are logged and prioritised

  • what the SLAs actually measure

  • what gets reported and how often

  • how recurring problems are managed

  • how releases and deployments work

  • how roadmap items are prioritised

  • how security and compliance are reported

  • how and when issues escalate.


One lesson I’ve learned is to make these arrangements practical. Who meets? How often? What information do they need? What decisions are made there? And what happens when an issue needs to escalate? I’d rather have a simple governance model that people actually use than pages of contract-management obligations that become a box-ticking exercise.


I take the same approach to SLAs. 24/7 support, Priority One, 30-minute response all sound impressive until the system goes down. A 30-minute response doesn’t necessarily mean anything has been fixed. When a critical system is unavailable, the business ultimately wants to know one thing: when will we be operating again? That’s the outcome your service levels should be designed around.


4. Make responsibilities clear

Contracts can use broad language about each party providing “reasonable assistance”, but that can leave a lot of room for interpretation once the work starts. Be specific about who owns the important activities. Who provides requirements, tests and accepts releases? Who monitors production, maintains integrations, manages security updates and deals with third parties?


I like using a simple RACI-style responsibility matrix to make this clear. It forces both parties to work through who is responsible, accountable, consulted and informed, and often exposes activities that everyone assumed somebody else owned.


This isn’t about shifting as much responsibility as possible onto the supplier. A good agreement should make the customer’s responsibilities just as clear as the supplier’s. The same applies to security and operational assurance. Be clear about who provides reporting, manages incidents, tests disaster recovery, monitors resilience and escalates issues.

Because when something does go wrong, you want everyone focused on resolving it, not debating who was supposed to be responsible for it.


5. Negotiate the bad days while you're having a good day

One thing I’ve learned from negotiating technology agreements is that the best time to talk about the bad days is while everyone is still having a good day.


At the start, everyone is optimistic. The supplier has won the work, the customer wants to get moving and both sides are focused on making the relationship successful. That makes it the right time to work through what happens if delivery slips, a critical service goes down, performance consistently falls short, or eventually the relationship simply isn’t working.

I’ve seen contracts that are very clear about when a customer has the right to terminate, but much less clear about what happens next. Having the contractual right to leave and being practically able to leave are two very different things, particularly when the supplier is supporting a business-critical system.

When I’m negotiating an exit, I want to understand what happens to:

  • your data

  • documentation

  • credentials and configuration

  • source code, where applicable

  • knowledge transfer

  • transition timeframes

  • cooperation with an incoming supplier

  • transition assistance and what you’ll pay for it.


These things can feel a long way off when you’re about to start a new relationship. But if you ever need them, they suddenly become some of the most important provisions in the agreement. That experience has left me with a pretty simple rule: don’t just negotiate your right to terminate. Negotiate your ability to transition. And negotiate it early, while everyone is still motivated to make the relationship work.


A good deal sets both parties up for success

For me, setting up both parties up for success is ultimately what good technology negotiation is about.

The best negotiations leave both parties feeling valued and understood, with clarity about what’s being delivered, what’s included, who’s responsible for what, when money will change hands and how you’ll work together through both the good days and the difficult ones.

Remember, signing the contract is the beginning, not the end. Most of the technology agreements I negotiate establish relationships that will last five years or more. You’re not negotiating for a short-term win at the negotiating table. You’re establishing the rules for delivery, support, change and thousands of decisions that will happen long after everyone has forgotten what was said during the negotiation. So push hard where it matters. Understand what’s driving the other side. Give ground where it makes sense. Aim for clarity, fairness and an agreement both parties can successfully deliver.


Get that right and you create the foundations for a successful, enduring technology partnership.


Before you sign...

If you’re buying technology, negotiating a new agreement or working through a contract with an existing supplier, let’s get the best out of all the parties. I can help you work through the commercial detail, identify the areas worth pushing on specific to your project, and get to an agreement that sets both parties up to succeed.



 
 
bottom of page