The award call was going great. Then he mentioned the price increase.

One of our clients installs landscaping for production home builders. Their COO asked what to do about a builder whose policy bans price increases:

“The purchasing guy at Builder X reached out to inform me that we were awarded a new community. We’ve been their landscaper on several other new build projects. I let him know we enacted a modest price increase since the last community they awarded us. He said his boss told him to switch vendors if any contractor asked for a price increase on anything. I know that the other landscaper he’s considering has a higher cost base than me, and he admitted that switching will actually make their costs go up!  What do I do?”

If you sell to big customers, you’ve hit this wall. Corporate sends down a directive to hold costs. Every purchaser gets the same instruction. Any increase, any category, any reason, and you’re out.

Our answer? This common challenge is about policy more than cost management.

Why the Policy Exists

A bright-line rule is nearly free to enforce. They don’t have to train anyone to discern or analyze a price increase request. They just ask their people to follow this simple rule.  And they know that granting one increase in one category opens the door on everything.

Arguing merits against a rule designed to be indifferent to merits is the losing move.

Three Places to Look

• Get inside the policy rather than around it. A no-increase policy governs increases to existing line items. It rarely governs new SKUs, spec changes, scope changes, change orders, mix, or terms. Same money, different category, and the purchasing manager gets to say yes without breaking anything. Helping him stay inside policy matters more than cost.
• Ask how substantiated increases are handled. Plenty of large customers reject blanket increases and consider documented ones. Ask him what the exception process is. Show up with a table showing changes in raw material and direct labor inputs, with published nursery stock and wage index data attached. It might convert “we don’t accept increases” into “we accept documented ones.”
• Weigh the possibility that they’ll stay with you anyway. Sometimes a purchasing manager threatening to switch is bluffing, and he already admitted the alternative will cost him more. Before you decide whether to call the bluff, get honest about how easily another landscaper could really cover this community. Then consider that you just won a new community, which is almost never just about price.  Something is winning you that work, and understanding what that is gives you leverage with every builder you serve.

Be Hard to Replace

Landscaping is often buyer-dominated because substitutes are plentiful, and no negotiation tactic magically solves that. What solves it is being hard to replace. Absorbing a schedule swing, covering four communities at once, carrying the lowest callback rate, taking a single-source award.

The Number Travels

Builder pricing leaks. One project manager, estimator, or purchasing manager leaves there for another builder, and now that builder starts challenging you on pricing.

Over time, that can cost you far more than this one community ever could. The failure mode isn’t losing the argument with Builder X; it’s that number migrating into every other quote you write.

Run the math before you decide anything. What does that community actually earn you at the old pricing? What would you have to hold elsewhere to replace it? Weigh the real cost of underpricing against the risk of customer churn.

Pushback Is Their Job

Purchasing pushes back on price. That’s their job, and a soft market makes them louder. Complaints are noise.

They gave you the community. That’s the real data.