Spotlight.ai in Leadr Magazine: The Artisan Problem
- Lolita Trachtengerts
- 2 days ago
- 6 min read
Spotlight.ai on why the best value teams in B2B SaaS are getting smaller, and that's probably good news.
We're excited to share that Leadr Magazine just published a piece by Spotlight.ai's Lolita Trachtengerts, VP Growth & GTM Ops. It's a direct look at the math problem sitting underneath every value engineering org in B2B SaaS, and why hiring your way out of it has never worked.
The article is called "The Artisan Problem: Why Smaller Value Teams Are the Future of B2B SaaS." And it makes a claim most value leaders feel but rarely say out loud: the function is structured to cap at roughly 20% coverage, and no amount of headcount fixes that.
Why Value Engineering Teams Cap at 20% Coverage
Walk into any enterprise SaaS company and ask what the value team does, and you'll get a beautiful answer. Custom business cases. Deep discovery workshops. ROI models tuned to each champion. Hand-built BVAs. POV decks that took three weeks to assemble.
Then ask how many deals the team actually touches. The number is always roughly the same. About 20%.
That's the artisan problem. The defining identity of a value consultant is craftsmanship. Every output is bespoke. Every business case is hand-stitched to the customer it's built for. Six artisans cannot meaningfully cover three hundred AEs working four thousand deals a quarter, and adding two more artisans doesn't change the shape of the problem.
The Artisan Tax
Most value leaders assume the 80% of deals their team can't reach get a watered-down version of value selling. They don't. They get nothing.
No business case. No ROI model. No champion arming. The AE walks into the CFO meeting holding a feature list and a discount. The buying committee receives a proposal that reads like a price quote. The deal lands or dies on factors that have nothing to do with the value of what's being sold.
This is the cost of the artisan model that nobody puts a number on. The 20% of deals the team touches outperform. The 80% they don't are running a completely different sales motion, with no value layer at all. The gap between those two populations is where most of the lost revenue lives.
The Budget Meeting
Every couple of years, the CFO or the new CRO wants to know what the value team actually moved last quarter.
The artisan answer is a list. Decks built. Workshops run. Champions trained. It sounds like work because it is work. But it doesn't sound like a number, and in the meeting where budget gets allocated, that distinction is the whole game.
The teams that survive walk in with different ammunition. Coverage rate as a percentage of pipeline. Win rate lift on touched versus untouched deals. Average deal size impact. Hard savings their customers were willing to put their name on. The function is the same. The vocabulary isn't.
"The artisan reports activities. The architect reports outcomes. That's the difference between a team that gets renewed headcount and a team that gets re-orged." — Lolita Trachtengerts, VP Growth & GTM Ops, Spotlight.ai
The Way Out Is Not More Artisans
Hiring more value consultants is the obvious move. It doesn't work. Sales teams scale exponentially because sales hires scale with revenue. Specialist functions scale linearly because each new hire adds one more set of hands. A team of 60 will hit the same wall a team of 6 hit, just at a higher altitude.
The way out is to stop producing one business case at a time.
Every customer interaction in a deal contains the raw material a business case needs. Pain points. Impact estimates. Champion conviction. Economic priority. Competitive context. Today, almost none of that material is captured systematically. It lives in someone's notes, or in the artisan's head, and when the artisan moves to a different deal, the signal is lost.
Structure those signals once, capture them automatically, map them to the opportunity, and the math of the function changes. Business cases stop being three-week projects and start being on-demand outputs. The team stops being the people who build business cases. They become the people who design how business cases get built.
What Changes When the Value Layer Exists
Coverage moves from 20% to 100%, and the team's headcount stays exactly where it was. The high-trust, high-stakes deals still get the human treatment. The 4,000 deals that used to go naked stop going naked.
The QBR conversation flips. Coverage rate becomes a real metric, tracked over time. Win rate lift becomes a real metric, comparable across geographies. Hard savings becomes a number with a customer's name attached to it. The team stops defending its budget every year because the budget defends itself.
The work that's left for the humans is the work that always mattered most. Building trust with technical champions. Coaching them for the rooms the value team will never sit in. Reading the politics, navigating procurement, knowing when to push and when to wait. The judgment work.
The calculations get cheap. The judgment gets more valuable.
The Upgrade: Artisans Become Architects
Three things move at once. Coverage shifts from the top 20% of deals to every pricing proposal that goes out. Output shifts from handcrafted decks to a structured value layer any rep on any deal can pull from. The team's role shifts from executor to architect.
None of this is a story about the value function shrinking. It's a story about the value function repositioning, and the leaders who recognize that early are about to have the most strategic seat in the GTM org. Not because they fought for it. Because the math finally works in their favor.
See What an Architect-Mode Value Layer Looks Like
The Spotlight.ai Value Intelligence agent captures every signal across every deal, structures it into a business case the buying committee will actually open, and gives every rep the same value layer your top 20% deals get today.
Not a workshop. Not a three-week BVA build. A value layer that runs on every deal in your pipeline.
FAQs - The Artisan Problem
Q: Where does the 20% coverage number actually come from?
Every value leader I've talked to lands on roughly the same figure. It's not a survey result, it's the math. If your team has six value consultants and each one can run two to three full BVA engagements a quarter, you're looking at 12 to 18 deals out of a pipeline of several thousand. That's 20% if you stretch, less if you're honest. The number is so consistent across orgs because the constraint is the model, not the team.
Q: Why doesn't hiring more value consultants fix this?
Because sales scales exponentially and specialist functions scale linearly. Every revenue dollar you add pulls more AEs into the org, which pulls in more deals. Your value team doesn't grow on that same curve. The gap between the two curves only widens. A team of 60 hits the same wall a team of 6 hit, just at a higher altitude. You're not solving the problem; you're paying more to live with it.
Q: What's the first move for a value leader who reads this and agrees?
Stop building one business case at a time. Audit what's already being captured across your deals, discovery calls, email threads, Slack channels, executive meetings. The signals a business case needs are already in those interactions. They're just trapped in someone's notes or in the artisan's head. Once you structure that capture and make it systematic, the math of the function changes. You go from output-per-headcount to output-per-deal.
Q: How do you talk to a CFO about this without sounding like you're asking for headcount?
Walk in with coverage rate, win rate lift, and hard savings. Not decks built, not workshops run. Activities defend nothing. Outcomes defend everything. If you can tell the CFO that 100% of deals over a certain ACV got a business case last quarter, and the deals that did closed at a higher rate with a bigger ACV, the conversation is over. You're not defending the budget anymore. The budget defends itself.
Q: What does the value team actually do once the value layer exists?
The work that always mattered most. Building trust with technical champions. Coaching them for the rooms you'll never sit in. Reading procurement politics. Knowing when to push and when to wait. The judgment work that doesn't fit in a model. The calculations get cheap. The judgment gets more valuable. That's the upgrade.
Q: What's the role you see value engineering playing in the GTM org five years from now?
The most strategic seat in the room. Right now value engineering reports to sales or to product, gets treated as a support function, and fights for budget every cycle. When coverage hits 100% and the function reports outcomes instead of activities, that flips. Value leaders become the architects of how the company sells. The leaders who get there first are about to have a very different career.
Comments