Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Reps Now Need a Technical Co-Seller
Transcript
- Lucas: If you're selling enterprise software in 2026 and you walk into a procurement meeting without someone who can pop open a terminal, you're probably going to lose. Luna: That is a very specific image. And I think it's true. The sales rep alone just doesn't carry the same weight anymore. Lucas: Right. And I want to be clear what I mean by 'technical co-seller.' I'm not talking about a sales engineer who shows up for the demo and then vanishes. I'm talking about a dedicated technical resource — often a Solutions Architect or a customer engineer — who is embedded in the deal from discovery through negotiation. Someone who can answer the 'how does this actually integrate with our stack?' question without saying 'I'll have to get back to you.' Luna: That rep who says 'I'll have to get back to you' — that's the kiss of death in a competitive procurement now. The other vendor's SA is already on the call, screen-sharing, showing the API call live. Lucas: Exactly. And this isn't a fringe case. I looked at a Gartner survey from late 2025 — it said 62 percent of enterprise software evaluations now require a technical buyer sign-off as part of the formal procurement process. That's up from something like 38 percent in 2020. So in five years, the technical buyer went from a nice to have to a gatekeeper. Luna: Sixty-two percent. That's a number worth sitting on for a second. Because it means nearly two-thirds of the time, the sales rep is not the person who closes the deal. The Solutions Architect is. Lucas: And the companies that have figured this out are building their go to market motion around dual-track sales. One track is the traditional rep — handles relationships, commercial terms, negotiation. The other track is the technical co-seller — handles architecture, security review, proof of value. They're a team, not a handoff. Luna: It reminds me of something I heard from a VP of Sales at a mid-market SaaS company. She said her best reps now spend less time pitching and more time 'orchestrating the technical conversation.' Meaning they bring in the SA early, they prep the SA on the account, and then they step back and let the SA run the technical validation. Lucas: That's a genuinely different skill set. And I think it's worth asking: what drove this shift? Why now? Lucas: I have a theory. It's the combination of two things. One, procurement teams have gotten much more sophisticated. They've been burned by overpromised integrations and vendor lock-in. Two, the technical buyer — the CIO, the CTO, the VP of Engineering — is now much more involved in procurement than they were five years ago. They don't trust a rep's slide deck. They want to see the actual product, connected to their actual infrastructure. Luna: And if the vendor can't demonstrate that live, the deal stalls. Or worse, it gets killed at the technical review stage, which is often the last step before signature. Lucas: I've seen that happen. A deal I know of — anonymized, but real — a seven-figure SaaS contract was sitting at 'verbal commitment' from the business sponsor. The procurement team scheduled a technical review with the vendor's SA. The SA couldn't answer two questions about data residency and latency. The deal got sent back to legal for 'further evaluation' and never closed. Luna: Ouch. And that's where the co-seller model directly protects the revenue. If that vendor had a more prepared SA, or if the rep had coached the SA on the prospect's specific infrastructure concerns, the deal might have closed. Lucas: Now, a lot of our listeners are either selling enterprise software or thinking about moving into that world. So I want to get concrete about what the technical co-seller actually does in practice. Because the title 'Solutions Architect' can mean a lot of different things. Luna: Give us the playbook. What are they doing in each stage? Lucas: In discovery, they're the ones asking about the prospect's current stack, the integration points, the compliance requirements. They're mapping out the technical landscape. They're also identifying potential friction points — like, 'Oh, you're on AWS GovCloud? That changes our deployment model.' Lucas: In the demo, they're not just clicking through the UI. They're running a customized scenario using the prospect's own sample data. Or they're showing how the API connects to their CRM. They're building trust by demonstrating competence. Luna: And then in the proof of value, they're essentially doing a mini-engagement. They're helping the prospect set up a sandbox, running through use cases, measuring success criteria. That's the part that most reps can't do. Lucas: Right. The proof of value is where the technical co-seller earns their keep. And it's also where the rep needs to know when to step in. Because the SA might get too deep into technical weeds and lose sight of the business outcome. The rep's job is to keep the conversation anchored to value. Luna: So it's a dynamic dance. The rep handles the 'why,' the SA handles the 'how.' And if they're not aligned, the prospect feels it. Lucas: Exactly. And this is where I think a lot of organizations get it wrong. They hire great SAs and great reps, but they don't invest in the pairing. They don't train them to work together. They just throw them on the same deal and hope for the best. Luna: It's like a doubles tennis partnership where one player is a baseline specialist and the other is a serve and volleyer. They can both be world-class individually, but if they don't know each other's positioning, they're going to leave the court open. Lucas: Good analogy. And the vendors that are winning right now — I'm thinking of companies like Snowflake, Databricks, AWS — they've institutionalized this partnership. Snowflake, for instance, has a whole program called 'SA Enablement' where they train their Solutions Architects not just on the product, but on how to work with sales reps. How to qualify technical fit. How to handle objections. How to write a statement of work. Luna: So they're essentially turning SAs into a kind of hybrid role — part engineer, part salesperson. But without taking away their technical credibility. Lucas: That's the key. If the SA starts sounding like a sales rep, the technical buyer will see through it immediately. The SA has to stay authentic. They need to be able to say 'that's a limitation we're working on' or 'here's how we'd architect around that.' Honesty builds trust. Luna: And that trust translates into faster deals. I've seen data that deals with a dedicated technical co-seller close 20 to 30 percent faster than those without one. Because you skip the 'get back to you' cycle. Lucas: Twenty to thirty percent is huge. Especially in enterprise where the average sales cycle is 9 to 12 months. Shaving off even 10 percent is real money. Luna: Let's talk about the career implications. Because I think for a lot of listeners who are technical — maybe they're developers or system admins — the Solutions Architect track is becoming a very viable path into the business side. Lucas: Absolutely. The SA role has evolved from a support function into a core revenue role. And the comp reflects that. At top-tier SaaS companies, senior SAs are earning total comp packages that rival the reps — base salary plus variable comp tied to deal closure. I've seen numbers in the $250,000 to $400,000 range for experienced SAs at companies like AWS or Microsoft. Luna: And it's not just the comp. It's the career optionality. An SA who understands sales can later move into product management, or into a sales leadership role, or even into a CTO advisory position. It's a springboard. Lucas: Right. And the flip side is also true. Reps who develop technical fluency — who can at least understand the architecture — are becoming more valuable. They don't need to be able to code, but they need to be able to speak the language. They need to know what a REST API is, what a data warehouse is, what single sign-on means. Luna: I've noticed a rise in what I'd call 'tech-adjacent' certifications for sales professionals. Like, there's now a Salesforce Sales Rep certification that includes a module on API integrations. And HubSpot has a 'Technical Sales' track in their academy. Lucas: That's smart. Because the bar is rising. And if you're a sales rep who can't answer basic technical questions, you're going to get filtered out by procurement before you even get to the economic buyer. Luna: So we've talked about the 'why' and the 'how.' Let's get to the tension. Because not everything about the co-seller model is smooth. There are real costs. Lucas: Costs, complexity, and conflict. I'll start with cost. Two people on a deal means double the comp cost. And if the deal doesn't close, you've burned a lot of expensive hours. So the unit economics have to work. That's why you typically only see dedicated technical co-sellers on deals above a certain ACV threshold — usually $100,000 or more. Luna: Below that, you might have a shared pool of SAs who float across deals. But then you lose the specialization. It's a trade-off. Lucas: Then there's the conflict piece. Who gets credit for the deal? If the rep gets full commission and the SA gets a salary plus a small bonus, there's no incentive for the SA to go above and beyond. But if you give the SA a variable comp tied to deal closure, you risk turning them into a salesperson. It's a delicate balance. Luna: Some companies have solved this with a team-based comp model. The rep and the SA share a pool of commission based on the overall team performance. That aligns incentives. Lucas: I've seen that work. But it requires a level of trust and transparency that not every sales culture has. You have to have a good CRM and a clear way to track contribution. Luna: Let's talk about the security review piece. Because it's a huge part of the technical co-seller's job now, especially post-2020. Every enterprise deal goes through a security questionnaire, and if the SA can't answer those questions, the deal hits a wall. Lucas: That's actually a great point. Security review has become its own gate. And the technical co-seller is often the one filling out the security document, or at least coordinating with the security team. If they're not prepared, the procurement team flags it and the deal gets delayed. Luna: I talked to a security architect at a large bank recently. She said they now require vendors to provide a 'security architecture diagram' as part of the RFP. And if the vendor can't produce one that matches their standards, they're disqualified. No exceptions. Lucas: So the technical co-seller not only has to know the product, they have to understand the customer's compliance landscape — SOC 2, HIPAA, GDPR, FedRAMP. It's a lot. Luna: It is. But that's also why these roles command such high salaries. They're not easy to fill. Lucas: If these conversations are useful for what you're building or running, I want to say something quickly. This show stays ad-free because listeners chip in a couple of dollars a month. It genuinely makes a difference — buy me a coffee dot com slash fexingo keeps the lights on. Luna: Yeah, it's a small thing that adds up. We appreciate it. Lucas: So back to the co-seller model. I think one of the most interesting developments is how some vendors are now offering technical co-sellers as a service — almost like a consulting engagement that wraps around the software sale. Especially in the data and AI space. Luna: Give me an example. Lucas: Snowflake, again. They have a program called 'Snowflake Professional Services' where they embed a data architect with the customer for the first 90 days. That architect is essentially a technical co-seller during the sales process and then transitions into an implementation consultant. It's a seamless handoff from sales to delivery. Luna: That's brilliant because it de-risks the implementation for the buyer. And it creates a natural expansion path. Once the architect is inside the customer, they see opportunities for additional workloads. Lucas: Exactly. It turns the technical co-seller into a long-term revenue driver, not just a deal closer. And that changes the ROI calculation entirely. Luna: So where do you see this going? In three years, is every enterprise rep going to have a technical co-seller on speed dial? Lucas: I think the model scales up, but it doesn't become universal. Companies selling lower acv products will still rely on a strong demo and a good product. But for any deal over six figures, I think you'll see a dedicated technical resource as standard. And I think the role will become more specialized — you'll have SAs who focus on security, SAs who focus on AI/ML, SAs who focus on compliance. Luna: That sounds like a fragmented field. But also a lucrative one if you're an engineer who can communicate. Lucas: That's the bottom line. The technical co-seller is not a passing trend. It's a response to a structural shift in how enterprises buy software. Buyers are more technical, more skeptical, and more process-driven. And the vendors that adapt — that invest in the rep sa partnership — are going to win the deals that matter. Luna: I think the takeaway for our listeners is clear. If you're in sales, get technical. If you're technical, get commercial. The middle ground is where the value is. Lucas: And the middle ground is where the co-seller lives. Thanks for listening — we'll see you next time.