Navigating the Discount Dilemma: A CEO's Guide to Protecting Margins and Profits in Software Development

2023-01-31

#business#management
 Navigating the Discount Dilemma: A CEO's Guide to Protecting Margins and Profits in Software Development

A client looks at your carefully assembled budget and asks for 50% off on two line items. Your gut says no. Your calendar says your developers are free next month. Your head starts doing math it doesn't want to do.

This happened to me. The project was 20,242€ with a 20% margin. The client wanted 50% off 8,436€ worth of items. Sounds like a negotiation. It's actually a trap — and most agency CEOs walk right into it.

The Math Nobody Wants to Do

The development cost on those discounted items was 3,374€. Our total profit on the project was 4,068€. Accept the discount, and the profit drops to 2,388€. But here's the part that hurts: even if everything goes perfectly — on time, no scope creep, no surprises — you're still losing 986€ on the deal overall. The "discount" doesn't just reduce profit. It creates a net loss.

Most agencies don't do this math. They see a smaller number and think "less profit." The reality is often "negative profit disguised as a smaller deal."

The Instinct to Say No Is Right. The Execution Is Wrong.

Rejecting a discount request outright burns the relationship. But accepting it burns your margin. So what do you actually do?

Reframe the conversation around scope, not price. When a client asks for a discount, what they're really saying is "this costs more than I expected." The fix isn't to do the same work for less money. It's to do less work for less money. Review the requirements together. Cut what's non-essential. Reprioritize. You protect your rate, they get a budget they can live with.

Weigh the relationship, not just the project. Some clients are worth losing money on once. If this project opens a door to three more — or to referrals that are worth ten times the margin — then the loss is a marketing expense, not a business failure. But be honest with yourself about how often that actually happens versus how often you tell yourself that story.

Factor in idle time. If the project is short and your team has nothing else lined up, an idle developer costs more than a discounted project. Taking the hit might be smart damage control — as long as you're conscious that it's damage control, not a business model.

The Real Lesson

Every discount negotiation is a moment of truth about how well you understand your own numbers. If you can't instantly calculate the impact of a discount on your actual margin — not revenue, margin — you're negotiating blind.

The discount itself isn't the problem. Accepting one without knowing exactly what it costs you is.