What to Expect When Negotiating a B2B Contract

Ray spent twenty years inside corporate, most of it at companies the size of small cities, before they went independent. The deal we talk about in this episode was their first with a client that big on the other side of their own table: a Fortune 500 company, a former manager who wanted them back in a different capacity, and three months between the first real conversation and a signed statement of work. We get into what those three months actually felt like, the intellectual property clause that almost cost them something they couldn't get back, and the difference between holding a boundary and just being difficult. Note: this post may have affiliate links and we donate 100% of those funds to non-profits and a children's group home🫶🏾 

The three months it took Ray to close their first six-figure corporate contract were not spent arguing over fee schedules. Once the actual negotiating started, it moved fast. If you're trying to figure out how to negotiate a consulting contract with a company that has a legal department bigger than your entire client list, the technical parts are rarely what gets you. It's the space between sending something and hearing nothing. A statement of work goes out, and then a week passes, then two, and your brain fills that silence with its worst material. Maybe the budget disappeared. Maybe the person who wanted to hire you got moved in a reorg nobody warned you about. You know, rationally, that someone is probably just back from vacation with four hundred emails ahead of yours in the queue. Your nervous system does not care what's rational.

The Three Months Nobody Sees

"The most anxious I was during the process was the dead zones between communications," Ray told me. They'd send a draft, then sit with the not-knowing for a week or two, wondering if it was too soon to check in. They caught themself catastrophizing every silence into a lost deal, a vanished budget, a client who'd quietly moved on. What they did with that waiting is worth naming: they compartmentalized it. Put it in a box, worked on their marketing plan, started building other client relationships in case this one fell through, and made room for video games and bird watching and the poetry they'd been meaning to get back to. They'd started the business partly to have time for those things, and the negotiation limbo was, ironically, the first real test of whether they'd protect that time or let the waiting eat it.

Ray kept calling the deal luck. A former manager reached out at the right moment, in a new role, wanting to work together again. That part is real, and it happens. But when I pushed on it during the conversation, what surfaced underneath the luck was years of being someone people wanted to bring with them. They'd been available. They'd done work worth trusting. They'd stayed a person worth remembering. The company didn't hand them a contract. A person they had an actual relationship with did, and that person happened to work somewhere with a budget attached to her.

We talk a lot in this work about courting companies, chasing logos, treating a name on a proposal like it does the convincing for us. What closes the deal, almost every time, is a person who remembers what it felt like to work with you. That's not a networking tactic. It's a reason to be a decent colleague in your 9 to 5, especially if you're already thinking about your exit, because the people you work with now are often your first clients later.

What a B2B Procurement Process Actually Looks Like From the Inside

If you've never sold into a large organization, the B2B procurement process is genuinely disorienting the first time, and almost nobody explains it out loud beforehand. You don't negotiate with the decision maker. You negotiate with a rotating cast of people who report to her, none of whom sign anything, all of whom shape whether you'll be allowed to. Ray talked to the leader who wanted them in February. She sent them to someone on her team. That person sent them to someone else. Each conversation refined what the engagement would actually look like, and each one added weeks.

Once there's alignment, you draft a statement of work and send it into what can feel like a void. Ray's approach here is worth stealing: they pitched two options instead of one, which gives the client a sense of choice and gives you room to move. Then, once everyone has agreed on price and scope, you hit what they called "the annoying logistics part," the part nobody warns you about. Big, older companies rarely invest in vendor onboarding the way they invest in their customer-facing products, so be ready for a system that hasn't been updated since a prior decade. Your beautifully formatted proposal gets replaced by their template, full of legal boilerplate you didn't write. Then comes the background check, the vendor portal, and a separate invoicing system, because whatever number you're charging is well past what fits on a corporate card. It's tedious. It's also the price of getting into the system permanently, which means the next contract with that company moves faster than this one did.

The Clause That Would Have Cost Me My Business

Somewhere in that boilerplate is where the real risk lives, and it's rarely in the parts that look scary. I had a client once who wanted to license some of HmntyCntrd's content, and buried in their legalese were clauses that would let them clone the work, improve it, and use it without paying me another cent. Renewal fees were capped for up to ten years, and even then, at half a percent. I would have signed away the actual asset of a service business, my intellectual property, if I hadn't had someone read it line by line. When a bigger company sends you their contract, spend the money on an attorney. I mean that as a genuine plea, not a suggestion you can skip if the timeline feels tight.

Ray ran into the same fight from the other direction. Their client's master service agreement said, in essence, that anything produced while working for them belonged to them, standard language and one of the reasons a lot of us leave corporate in the first place. But they'd be running workshops built on frameworks they'd developed over years, and they weren't willing to hand those over. So they added their own IP clause to the statement of work, specific language protecting their preexisting methodologies while still giving the client what they actually needed: the ability to use those frameworks internally after the engagement ended. "We had to really tie the language carefully so I keep the IP while you keep usage," they said. That single sentence took real back-and-forth to land, and it was worth every round of it.

Money terms deserve the same scrutiny. I once had a client whose contract specified net six months for payment. Not ninety days, six months. I negotiated it down to net 30, and we worked together well for a couple of years until they tried to reinstate the six-month term. I told them we were done. A business with a Fortune 500 balance sheet can afford to sit on an invoice. A small business can't, and pretending otherwise is how you end up funding a client's cash flow with your own.

A Boundary Isn't the Same as a Wall

Ray was clear about where their hard lines actually were, and it wasn't everywhere. Getting money down before starting was non-negotiable; they might have flexed the percentage, but not the principle. They asked for 50% up front, framed to the client as a scheduling fee, protection for the time they were reserving on their behalf instead of taking on other work. The client didn't push back. Payment timing, on the other hand, they treated as genuinely flexible. Net 75 wasn't his preference, but it wasn't a line worth losing the deal over.

I encourage this same 50% structure, especially for larger projects, and I'd add: make it non-refundable. It protects your calendar and it protects you if the client's circumstances change a month into a six-month engagement. You could have spent that time finding other work. The deposit is what makes sure you didn't lose out for having trusted them.

The instinct to avoid all of this, to just accept the ninety-day net and the vague scope because at least you'll have a client, is understandable. Corporate trains you to absorb friction: reorgs, shifting priorities, leadership that changes its mind. When you leave, you don't have to keep absorbing it, and clients who are actually worth keeping will meet you halfway. As Ray put it, most of what makes this feel scary is a machine of documents and templates, but the edges of that machine are people, and the person who's gotten this far in a conversation with you generally wants you there.

How to Negotiate a Consulting Contract With a Corporate Client

A few things worth carrying into your next one. Treat the whole process as an ongoing conversation, not a single high-stakes event; almost every term has room to move until you actually sign. Read the master service agreement in full, even the parts that seem untouchable, because language like "per the SOW" is often a door into flexibility you didn't know you had. Add your own IP clause to your statement of work if the client's boilerplate claims ownership of everything you produce; you can usually protect your frameworks while still giving them the usage they need. Ask for money down, and treat it as protecting your calendar rather than distrusting the client. And before you panic over a clause, ask whether it's actually a hard line for them or just the default language nobody's bothered to update. Often it's the second one.

Ray is still refining their elevator pitch, and honestly, so am I most days. That's a post for another time.

If you've already got a client at the table and what's standing between you and steadier revenue is more of these conversations happening at all, How to Book Your First 10 Discovery Calls has the scripts for exactly this stage, getting people from "let's talk" to a signed statement of work.

Originally aired as Episode 65 on the Choose Courage Inc. podcast