Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How to Negotiate the Hidden Cost of Implementation
Transcript
- Lucas: We tend to think of the close as the finish line. The signature, the handshake, the relief. But in enterprise B twenty B sales, the close is actually just the starting gun for the most expensive part of the relationship. Specifically, implementation. Luna: Right. Because once they sign, the clock starts ticking on delivery, and if the scope isn't locked down tighter than a drum, the margin evaporates before day one. Lucas: Exactly. And here is the thing that trips up even seasoned operators. They treat implementation as a variable cost that can be squeezed later. It isn't. It is a fixed liability baked into the contract language, whether you realize it or not. Look at a typical mid-market SaaS deal from today, October nineteenth, two thousand twenty six. You have a base license fee, sure. That is predictable. But then you have the onboarding package. Three months of dedicated engineering time. Data migration. Custom API integrations. That is where the profit goes to die. Luna: I see this all the time with our clients. The sales rep promises flexibility to get the signature, assuming they can figure out the details later. Later never happens. Lucas: Later becomes a budget overrun. I want to talk about a specific mechanism we call the Definition of Done. Most contracts use vague terms like 'reasonable efforts' or 'standard integration.' Those are liability traps. When you define done, you set the boundary for your resources. Let's look at a hypothetical but very common scenario. A logistics company buys a route optimization platform. The sales deck shows a dashboard. The contract says 'integration with existing ERP systems.' That sounds simple. But which ERP? How many legacy modules? Is data cleansing included? Without explicit boundaries, the implementation team assumes infinite work. Your gross margin drops from forty percent to ten percent within sixty days. Luna: So the fix is hyper-specificity in the statement of work. But doesn't that make the proposal harder to sell? Buyers want simplicity. Lucas: That is the myth. Buyers don't want simplicity; they want certainty. Ambiguity scares procurement more than complexity. When you provide a detailed implementation roadmap with clear exclusion clauses, you signal confidence. You are telling them, we know exactly what this takes, and we have priced it accordingly. It shifts the conversation from 'how much will this cost me?' to 'can this vendor actually deliver?' In my experience, clarity wins deals against cheaper, vaguer competitors because it reduces perceived risk. Luna: I agree, but there is a pushback. Procurement loves to negotiate scope creep because they think they are getting more for free. How do you hold the line? Lucas: You hold the line by pricing the out-of-scope items explicitly upfront. Do not hide fees. Put them on the table. Say, 'Here is the standard package. Here is what it includes. Here is the hourly rate for additional custom development.' When you make the marginal cost transparent, buyers self-regulate. They realize that every extra feature has a price tag. It forces them to prioritize what actually matters versus what is nice to have. It turns implementation from a black box into a menu. Luna: That makes sense. It protects your margin while giving the buyer control. But what happens when the client changes their mind mid-project? Scope creep isn't just pre-signature anymore. Lucas: Mid-project creep is inevitable. The key is having a change order process that is frictionless but costly. Not financially costly, operationally costly. Require formal written requests. Make the client's internal stakeholders sign off on every deviation. When you force their project manager to justify every new requirement, they slow down. They stop asking for frivolous tweaks. The barrier to entry for changing scope becomes higher than the inconvenience of sticking to the plan. Luna: It’s psychological warfare, really. Making the admin work for changes discourage the changes themselves. Lucas: Precisely. And this ties back to the initial contract. If you have a robust change management clause, you aren't being difficult; you are being professional. You are protecting the timeline. Delays hurt everyone. By enforcing structure, you keep the project on track, which keeps the client happy in the long run. Happy clients refer business. Frustrated clients churn. Churn kills revenue ops models faster than anything else. Luna: Speaking of churn, let's talk about the handoff. Sales and customer success often hate each other. How does tight implementation scoping improve that dynamic? Lucas: It eliminates the blame game. When the statement of work is signed by both parties, CS knows exactly what was promised. Sales cannot overpromise because the technical lead reviewed the scope. CS cannot underdeliver because the specs are clear. It creates a single source of truth. I’ve seen companies reduce early-stage churn by fifteen percent just by requiring joint sign-off on implementation plans before the first invoice is issued. Luna: That joint sign-off is crucial. It forces alignment before the money moves. But does this approach slow down the sales cycle? Detailed SOWs take time to draft. Lucas: It adds a few days, maybe a week, depending on deal size. But compare that to the three-month delay caused by a botched implementation. Speed is not always speed. If you close a bad deal quickly, you are just accelerating your own pain. Better to spend five days getting the scope right than five months fixing the relationship. In the current Q four environment of two thousand twenty six, buyers are more risk-averse anyway. They appreciate the diligence. Luna: True. Risk aversion is high right now with economic uncertainty. Buyers want partners who can execute, not just pitch. Lucas: Exactly. So, let's drill down into one concrete tactic. The 'Exclusion List.' Every statement of work should have a section titled 'Out of Scope.' List what you will NOT do. No custom reporting beyond standard templates. No support for legacy operating systems. No data entry by your team. It sounds negative, but it defines positive space. It clarifies the boundaries of your value proposition. It stops the endless email threads of 'but can you also...' Luna: I love that. It’s proactive denial. Instead of reacting to demands, you set the perimeter. It saves so much emotional energy for the project managers. Lucas: It does. And it empowers the account executives to say no without fear. They have the contract on their side. They can point to page four, paragraph two. It removes the personal conflict from the equation. It becomes policy, not preference. Luna: Does this work for smaller deals too? Or is it only for enterprise-level contracts with legal teams? Lucas: It works for small deals. In fact, it is more important there. Small deals have less slack. One unexpected task can wipe out the entire profit margin. A startup selling a fifty thousand dollar service engagement cannot afford to spend two hundred hours on customization. The math doesn't work. Simple, clear scopes are non-negotiable for healthy unit economics at any size. Luna: Okay, so we have defined the scope, we have the exclusion list, we have the change order process. What about the actual execution phase? How do you measure if the implementation is staying on track? Lucas: You measure milestones, not hours. Track progress against deliverables. Did the data migrate successfully? Did the API connect? These are binary outcomes. Hours spent are irrelevant if the outcome isn't achieved. Set weekly check-ins focused solely on milestone completion. If a milestone is missed, trigger the change order process immediately. Do not let slippage accumulate. Early detection prevents crisis management. Luna: Binary outcomes are easier to track than subjective progress. It keeps the project moving forward rather than drifting. Lucas: It does. And it builds trust. The client sees tangible progress every week. They feel in control. Transparency is the antidote to anxiety. When clients are anxious, they micromanage. When they see progress, they step back. Stepping back gives your team breathing room to execute efficiently. Luna: There is a lot of wisdom here. It feels like treating sales and implementation as one continuous process rather than two separate silos. Lucas: That is the core insight. Silos create leakage. Alignment creates profit. Operators who integrate these functions see higher net retention and better cash flow predictability. It is not glamorous work, but it is foundational. Luna: Before we wrap up, I want to touch on the human element. Salespeople are incentivized to sign. Implementation teams are incentivized to deliver. How do you align those incentives? Lucas: Tie a portion of the sales commission to successful implementation milestones. Not just payment received, but go-live confirmed. If the deal fails during onboarding, the rep loses part of their bonus. This forces reps to sell realistically. They stop promising moonshots they know are impossible. It aligns their interest with yours. It is a powerful lever. Luna: That changes the behavior immediately. Reps become quality filters instead of just volume drivers. Lucas: Exactly. Quality over quantity. Sustainable growth beats explosive, fragile growth every time. Luna: This has been incredibly practical. I think a lot of listeners need to audit their current statements of work right now. Lucas: They do. Start with the exclusions. See what is leaking out. Fix the boundaries. Protect the margin. Luna: Yeah, it’s amazing how much clarity comes from just saying what you won’t do. Lucas: It really is. Boundaries create freedom. Now, I know we have been deep in the weeds on contracts and margins, but remember that behind every SOW is a relationship. The goal isn't to trap the client; it's to ensure both sides succeed. Luna: Absolutely. Success breeds loyalty. And loyalty is the best ROI. Lucas: Well said. Before we go, I want to mention something important. This show runs on listener support. A couple of dollars a month is genuinely what keeps these conversations ad-free and sustainable. If you've gotten value from the analysis, head to buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Your support directly funds the research and production that makes this possible. Luna: Thank you for listening. It really means a lot to us, especially with the effort put into digging into these operational details. Lucas: Back to the topic. One final thought on implementation. As you build these frameworks, look at your historical data. Which deals had the smoothest onboarding? What did they have in common? Was it the client size? The industry? The specific rep who sold it? Pattern recognition is your next level of advantage. Luna: Data-driven refinement. You can't improve what you don't measure. Lucas: Correct. So, audit your past twelve months. Find the winners. Reverse engineer their scope documents. Copy the winning patterns. Delete the losing ones. It is systematic improvement. Luna: Systematic. I like that word. It removes the guesswork from scaling. Lucas: It does. And that is the ultimate goal. Scalable processes that protect margin and delight customers. It is a balance, but it is achievable. Luna: For sure. I think we have given operators a solid toolkit to start implementing tomorrow. Lucas: We have. Start with the exclusions list. It is the lowest hanging fruit. You will see immediate results in reduced scope creep emails. Luna: And reduced stress for the whole team. Less fighting, more doing. Lucas: Exactly. Less fighting, more delivering. That is how you build a resilient revenue engine. Luna: Agreed. Thanks for breaking this down so clearly, Lucas. Lucas: My pleasure, Luna. Let’s keep tightening those nets. Until next time.