Your sales team wants to customize every deal. Here's what to do.

You've done the hard part. You productized, launched your first few offerings, and signed your early clients. Then the requests start. Your best consultant (who happens to be your best seller) comes back from a pitch convinced this client is different. Another wants to swap out a module, stretch the timeline, and take something off the price. Within a quarter, your new offerings look a lot like custom engagements again, and your product team spends its week building one-offs.

Why do sellers push for custom work?

Consultants (sellers) push for custom work because most of them built their careers selling it. Scoping a bespoke engagement is what they know how to do. Selling a fixed offering feels like selling with one hand tied, so when a client hesitates, the reflex is to reshape the offering instead of explaining it.

Start by asking the seller to describe the client's problem, before discussing the change they want. Most of the time, it's a problem many of your other clients share, and the standard offering already solves it. What the seller needs is a clearer way to explain that. Our post on overcoming client resistance to standardized offerings covers how to have that conversation.

How should you answer a custom request?

Every custom request has one of four answers: it's already covered, it becomes an add-on, it goes on the roadmap, or you say no.

1. It's already covered. The standard offering solves the problem. Help the seller reposition it and move on.

2. Make it an add-on. If delivering the request mostly costs time and materials, give it a set scope and a set price. Custom work is built around one client. An add-on is built once and sold again, which is what makes it scale. If you expect more clients to want it within six months, it's worth building. Try it with this client, then sell it to the next one.

3. Put it on the roadmap. Ask why the client wants it. If the answer points to a change other clients would value, it may belong in the core offering. Prioritize custom work that builds toward an offering you want to sell more of, then standardize it.

4. Say no. If the request serves only one client and doesn't move the business where you want it to go, decline it or price it as a rare premium exception. Saying yes carries real risk: tailor an offering far enough and it becomes so specific to one client that you can't sell it to anyone else.

Who should approve custom deals, sales or leadership?

Both. Sellers approve changes inside written guidelines, and leadership approves anything outside them.

Every tailoring decision trades a closer fit for one client against the efficiency of your standard offering. If sellers can configure every part of the deliverable, every deal turns into a negotiation. If nothing can flex, you lose deals you should win.

The guidelines should spell out which add-ons sellers can include, how much discount they can offer, and how far contract terms can flex. Write them down before your next pipeline review, because limits that aren't written down get negotiated away.

What should a business case for a custom request include?

A business case for a custom request should cover the client, the contract value, whether the client will pay enough to cover cost plus margin, timing, and expected revenue over the next year.

The form does two jobs. Sellers have to weigh a request the way an owner would before they make it. And the people building the offerings no longer have to referee every deal.

What’s the right amount of custom work?

The goal isn't zero custom work. It's custom work you chose on purpose, because it pays for itself or points to the next thing you'll sell.

If your sellers are pulling your new offerings back toward custom, we can help you set the guardrails and the approval process.

Book a call with our team.