Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How To Negotiate Scope Without Killing Margins
Transcript
- Lucas: The most dangerous line in any sales contract isn't the price tag. It is the vague promise of 'full implementation support.' I have seen deals where the initial quote was ten percent higher than competitors, yet the final realized margin was negative because the scope expanded until the team was drowning in unpaid work. Luna: That sounds like classic scope creep masquerading as customer success. How do you draw the line before the project starts? Lucas: You define the boundary with explicit deliverables and change order protocols. In a recent case involving a mid-market logistics platform, the sales team refused to budge on the base fee when the buyer demanded additional integration modules. They didn't raise the price; they raised the barrier to entry for those extras. Luna: So instead of saying no, they made it expensive or difficult to get? That is a subtle but powerful distinction. Lucas: Exactly. They structured the contract so that any request outside the predefined API endpoints required a formal statement of work and a minimum engagement fee. This forced the buyer to evaluate the true cost of their requests rather than assuming everything was included. Luna: It shifts the conversation from price to value realization. The buyer has to justify the spend internally. Lucas: Right. And it protects your delivery team from burnout. When scope is undefined, engineers start working late nights on 'quick fixes' that were never sold. That erodes morale and destroys profitability simultaneously. Luna: But buyers push back hard on rigid scopes. They want flexibility. How do you accommodate that without losing control? Lucas: You offer flexibility through premium tiers or add-on packages. The same logistics company offered a 'growth pack' that included three additional integrations for a fixed monthly fee. It was simpler for them to upsell than to negotiate custom dev hours. Luna: Packaging uncertainty into a predictable revenue stream. That is smart product thinking applied to sales. Lucas: It requires discipline during the negotiation phase. Salespeople are often trained to say yes to keep the deal alive. But saying yes to undefined scope is saying no to your own profit margin later. Luna: Do you see this happening more in services or in software products? Lucas: Services obviously, but SaaS companies are falling into the same trap. They sell a platform and then provide endless custom configuration without charging for it. It becomes a service business disguised as a product business. Luna: And that kills valuation multiples eventually. Investors don't pay product multiples for service revenue. Lucas: Precisely. So the early decision to enforce strict scope boundaries actually enhances the long-term strategic value of the company. Luna: I am going to pause us here briefly. If these conversations about protecting margins and structuring deals have moved your work forward in some small way, consider supporting the show directly. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo. It helps us bring you more deep dives like this one without ads. Lucas: We appreciate the support. It allows us to keep digging into the operational details that matter. Luna: Back to the deal structure. What happens when the buyer refuses to accept the change order process? Lucas: Then you walk away or renegotiate the entire commercial model. In that logistics case, the buyer initially resisted. But the CFO stepped in and recognized that the alternative was unpredictable vendor costs. Stability won out over cheap upfront pricing. Luna: The CFO cares about predictability just as much as the sales VP cares about closing. Aligning those incentives is key. Lucas: Yes. You need to speak the language of the budget holder. Uncontrolled scope creates variance in financial forecasting. No CFO likes variance. Luna: So you frame strict scope as a risk management tool for their finance department. Lucas: Exactly. It transforms a potential conflict into a shared objective. Both parties want to avoid surprise invoices and surprise delays. Luna: What about post-signature? Once the contract is signed, how do you prevent drift? Lucas: You establish a governance committee with clear meeting cadences. Any deviation from the roadmap must be reviewed by both sides quarterly. This prevents small requests from accumulating into massive hidden projects. Luna: Regular check-ins keep everyone honest. It stops the slow bleed of resources. Lucas: It does. And it gives you data. If a client consistently asks for changes outside scope, that is market intelligence. It tells you what features to build next. Luna: Turning scope creep into product development leads. That is a brilliant way to look at it. Lucas: Only if you charge for the initial exploration. You can offer a paid discovery phase to validate those new needs before committing engineering time. Luna: Paid discovery. That filters out the tire-kickers immediately. Lucas: It does. Serious buyers will pay for clarity. Desperate buyers will try to get it for free. You want serious buyers. Luna: Does this approach work for smaller deals too, or is it only for enterprise contracts? Lucas: It scales down. For smaller deals, you use standardized statements of work. No custom narratives. Just a checklist of inclusions and exclusions. Simplicity is your friend at lower price points. Luna: Standardization reduces legal review time and speeds up closing. Efficiency gains on multiple fronts. Lucas: Right. And it builds a reputation for reliability. Clients know exactly what they are getting. There is no ambiguity. Luna: Ambiguity is where relationships go to die. Clarity builds trust faster than any dinner invitation. Lucas: I could not agree more. The best salespeople are not the ones who talk the most. They are the ones who define the rules of engagement clearly. Luna: So the pen is mightier than the sword, but the clause is mightier than the pen. Lucas: Well put. A well-drafted clause prevents the argument before it even starts. Luna: Are there common pitfalls in writing those clauses that sales teams should watch out for? Lucas: Vague verbs. Words like 'assist,' 'support,' or 'facilitate' are dangerous. Replace them with 'deliver,' 'install,' or 'configure.' Actionable language leaves no room for interpretation. Luna: Specific verbs create specific expectations. That makes sense. Lucas: It does. And always include a cap on hours for unspecified tasks. If something falls outside the scope, limit the labor exposure immediately. Luna: A hard stop on hours. That forces the conversation back to budget or scope adjustment. Lucas: Exactly. It puts the ball back in the buyer's court. Do they want more hours? Then they need to approve more budget. Luna: It turns a resource problem into a financial decision. Much easier for executives to handle. Lucas: Yes. And it keeps your delivery team focused on the core product rather than firefighting custom requests. Luna: Protecting the team's bandwidth is just as important as protecting the margin. Lucas: Always. Burned-out engineers make mistakes. Mistakes cost money. Money lost is margin erased. Luna: So strict scope is actually an employee retention strategy disguised as a sales tactic. Lucas: I would argue it is the most effective one. People want to solve problems, not chase them indefinitely. Luna: When we close deals with clear boundaries, everyone wins. The client gets a predictable outcome, and the seller keeps their integrity intact. Lucas: Integrity is a currency that appreciates over time. Clear contracts are the bank deposit. Luna: As we wrap up, what is the one action a listener can take tomorrow to improve their deal structure? Lucas: Review your last five closed-won contracts. Identify every instance where scope was vague. Draft a standard exclusion list for each product line and implement it for new proposals. Luna: Audit the past to fix the future. Simple, actionable, and immediately protective of your bottom line. Lucas: It is. And it sets a precedent for all future negotiations. You teach the market how to treat you. Luna: Teaching the market respect through precise language. That is a lesson worth remembering. Lucas: Indeed. The next time you sit across from a buyer, remember that the silence after you define the scope is often louder than any objection. Luna: Let the definition do the selling. Until next time.