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 moment in a sale isn't the final signature, it's the day after the contract is signed when the client reads the statement of work for the first time. I see founders get so excited about closing the deal that they agree to vague deliverables like 'full integration support' without defining what integration actually means to them versus what it means to your engineering team. Luna: Right, because 'support' sounds helpful until you realize it means twenty-four-seven monitoring of a legacy system that hasn't been updated since two thousand twelve. Lucas: Exactly. And then you have a delivery team working nights to keep the client happy while your gross margin collapses from forty-five percent down to twenty-two percent. This is where scope creep kills more profitable businesses than bad pricing ever will. The issue is almost always that we negotiate the price before we negotiate the boundaries. Luna: So you're saying we treat the scope definition as a commercial lever rather than just a technical checklist item? Lucas: Precisely. When I consult with mid-market software companies, I tell them to implement what I call the Scope Boundary Protocol. It starts with rejecting open-ended language in the initial proposal. You never write 'we will assist with data migration.' You write 'we will migrate up to fifty thousand records using our standard mapping tool.' Once you hit record number fifty thousand and the client wants more, that is no longer scope, that is a change order. Luna: That feels aggressive to some clients who are used to vendors just doing whatever it takes to make them smile. Lucas: It only feels aggressive if you haven't priced the service correctly. If your price reflects the defined scope, then anything outside that scope is extra work that deserves extra pay. The problem is that many operators are terrified of looking rigid during the negotiation phase, so they leave these gaps in the contract hoping the client won't notice. Luna: But the client will notice. They will notice every hour your team spends fixing something that wasn't in the original agreement. Lucas: They notice immediately. And here is the hard truth: clients respect boundaries more than they appreciate flexibility. A vendor who says 'that is out of scope, but we can add it for this fee' signals confidence and operational maturity. A vendor who says 'sure, we'll figure it out' signals desperation and poor planning. Luna: So the negotiation isn't really about convincing the client to buy more, it's about educating them on how your delivery model works. Lucas: That is exactly right. You are selling predictability. Your client wants to know that when they hand over their budget, the project will finish on time and on budget. Ambiguity threatens that predictability. By defining the edges of the deal sharply, you are actually reducing their risk, even if it makes the contract look more restrictive on paper. Luna: I had a friend who sold a marketing agency last year, and she lost three hundred thousand dollars in equity value because she couldn't enforce her own scope limits on a flagship account. Lucas: That is a classic example. She probably started with a great pitch, promised custom reporting, and then ended up building a bespoke dashboard for a client who was paying for a template. The mismatch between the product and the service delivery ate all the profit. The lesson is that the scope must be locked before the deposit clears. Luna: Locking it early seems simple enough, but how do you handle the pushback when the client says they need flexibility for things they haven't thought of yet? Lucas: You offer a contingency bucket. Instead of unlimited access, you allocate ten percent of the total project hours for undefined tasks. If they use it, great. If they don't, you keep the margin. But you never give away infinite capacity for a fixed price. That is the single biggest mistake I see in enterprise sales contracts. Luna: So you trade absolute certainty for financial safety. You accept that some unknowns will exist, but you cap the financial exposure. Lucas: Yes, and you price that cap explicitly. When you present the ten percent buffer, you frame it as a smart way to manage risk together. You aren't being cheap, you are being responsible. It changes the dynamic from you protecting yourself to you protecting the project timeline. Luna: That is a much better narrative. Clients want to feel like you are partners managing the project, not vendors hiding behind fine print. Lucas: Absolutely. And there is another layer to this which most people ignore, and that is the definition of success. You need to tie payment milestones to specific, measurable outcomes within that scope. Not just 'completion of phase one,' but 'successful testing of module A against criteria B.' Luna: Because otherwise, the client can claim the work isn't done because they changed their mind about what 'done' looks like halfway through. Lucas: Exactly. Subjective satisfaction clauses are death traps for margins. If you rely on the client saying 'I am happy with this,' you have zero leverage when they drag their feet on sign-off to delay payment. You need objective criteria baked into the scope document. Luna: So the contract becomes a technical manual as much as a legal document. It has to be readable by the engineers who will actually do the work. Lucas: If your delivery team cannot read the contract and understand exactly what they are expected to build without asking legal questions, you have already failed the negotiation. I always insist that the lead engineer reviews the scope draft before the sales team sends it to the client. Luna: That requires a level of collaboration between sales and delivery that doesn't exist in a lot of organizations. Sales just wants the logo. Lucas: And that is why the logos are expensive. You are selling labor at a retail price while buying it at wholesale rates because you didn't account for the complexity. When sales and delivery sit together, they can spot the traps early. Like realizing that the client's API documentation is outdated and that integration will take twice as long as estimated. Luna: If you catch that in the negotiation, you can adjust the price or narrow the scope. If you catch it on day one of implementation, you are just absorbing the loss. Lucas: Correct. The cost of finding a scope error in October is zero dollars. The cost of finding it in February is thousands of dollars in wasted engineering time. So the discipline of tight scope definition is actually a profit preservation strategy, not just a sales tactic. Luna: It reframes the whole conversation. You aren't being difficult about the details, you are being financially prudent for both parties. Lucas: And it filters your clients. Clients who balk at clear scope definitions are often the ones who will create the most friction later. Clients who appreciate the clarity become easier to manage because they know exactly what they are getting and what they are paying for. Luna: So a strict scope can actually improve customer satisfaction by preventing those endless arguments about whether a feature should be free or paid. Lucas: It eliminates the arguments entirely. There is no debate when the boundary is drawn in ink. The relationship moves forward based on execution, not renegotiation. And that is where the real efficiency gains happen. Luna: I think a lot of operators struggle with this because they equate flexibility with good service, but clearly that is a false equivalence. Lucas: It is. True service is delivering what was promised, reliably. Anything beyond that is a premium offering that needs a premium price tag. Mixing the two confuses everyone involved. Luna: This brings me back to the idea of the contingency bucket. How do you handle it when the client burns through that ten percent buffer in the first month? Lucas: Then you trigger the change order process immediately. You do not let them dig a hole and expect you to fill it for free. You send a notification that the buffer is exhausted and any further work will be billed at the agreed hourly rate or require a new fixed-price amendment. Luna: That feels risky for the relationship. Won't they feel attacked when the billing starts? Lucas: Only if you haven't managed expectations throughout the project. If you have been transparent about the buffer usage, it is just a administrative step. If you stayed silent until the end, it is a shock. Communication is the key to making the scope boundaries feel collaborative rather than combative. Luna: So you are constantly updating the client on how their requests impact the timeline and the budget, keeping them in the loop. Lucas: Yes. You become the guide who shows them the map. When they ask to go off-road, you show them the toll booth. Most clients will pay the toll if they understand that it keeps the journey moving smoothly. They just hate surprise fees. Luna: Surprise fees are the enemy of trust. Clear scope builds trust because it aligns incentives. Lucas: It does. And ultimately, a well-scoped deal allows your team to focus on quality rather than firefighting. That is the hidden benefit that rarely makes it into the sales deck, but it is the reason your net promoter score stays high. Luna: Quality execution is hard when you are constantly pivoting to fix scope misunderstandings. Tight boundaries create the stability needed for excellence. Lucas: Exactly. So next time you are reviewing a term sheet, look past the headline price. Look at the edges. Are they sharp? Are they clear? Because that is where your profit lives. Luna: And where your sanity lives too. Lucas: Let's talk about supporting the network. If these conversations about operational precision have helped you tighten your own processes, consider supporting the show directly. Listener contributions keep the production independent and ad-free. You can find us at buy me a coffee dot com slash fexingo. Every bit helps maintain the quality you hear here. Luna: We really appreciate the community that chooses to engage with the work this way. Lucas: Back to the deal dynamics, there is one final nuance to the scope protocol. You must define the exclusions just as clearly as the inclusions. Tell the client what you are not doing. Luna: Negative space. Defining what is off-limits protects you from assumption-based scope expansion. Lucas: Precisely. A list of exclusions is often more valuable than a list of features because it manages the lowest-hanging fruit of disputes. It prevents the 'I assumed you would handle that' conversation before it ever happens. Luna: So the contract acts as a shield for the relationship, removing the ambiguity that usually causes friction between partners. Lucas: It is the ultimate act of care. By being rigorous about the details, you ensure that the relationship survives the delivery phase intact. Profitability and partnership are not opposites; they are dependent on each other. Luna: When the money is clear, the human connection can actually flourish. Lucas: Exactly. So define the edges, price the buffer, and let the delivery speak for itself. What part of your current scope definitions feels the most vulnerable to creep?