Stop Waiting Weeks: Make Your SE Team AI-Self-Sufficient [82]
AI assistants can enable solution engineers to self-serve work that previously required weeks of cross-team dependencies, such as creating landing pages and drafting case studies. The key is establishing templates and guardrails approved by other departments upstream, rather than giving SEs unrestricted access, to balance speed with governance.
Summary
The episode discusses how AI tools are transforming solution engineering workflows by reducing multi-week dependencies on other teams. Tim opens with an anecdote about Priya creating a webinar landing page in 30 minutes using an AI template—work that used to take weeks at his previous company. The hosts explore this pattern across two main use cases: webinar creation and customer reference documentation. For webinars, marketing pre-approves a template with brand guidelines baked in, allowing SEs to generate compliant landing pages autonomously. For case studies, SEs can draft references from call notes with AI, get customer approval, and publish same-day, eliminating internal handoffs. However, the conversation acknowledges real constraints. In enterprise settings, customer legal departments genuinely add weeks to reference approvals that can't be bypassed. Nate raises concerns about scale—200 SEs each creating custom webinars could fragment brand messaging. He also cautions against 'shadow IT' risks, citing an example where a region built unsanctioned demo environments that created governance nightmares 18 months later. The group agrees the problem isn't SEs building things; it's building without guardrails or visibility. Ava points out that the real time-sink wasn't hands-on work but weeks of chasing, waiting, and requests sitting in inboxes before reaching decision-makers. The recommended action is a dependency audit: ask SEs what they waited over a week for, then determine which dependencies can become self-serve with template approval rather than per-request approval. Crucially, leaders should partner with other department heads first to reframe self-service as reducing their queue, not bypassing their authority.
About this episode
Ava watched one of her SEs go from webinar idea to live landing page before lunch, work that once took her weeks of cross-team waiting. Nate pushes back on brand risk, shadow IT and customer legal. Together they work out which dependencies AI can remove and which ones are real.
Key Insights
- The majority of multi-week delays aren't from the actual work being complex, but from chasing, waiting, and requests sitting in inboxes before they reach decision-makers—the hands-on work was never the big part of the timeline.
- When self-service work becomes cheaper (e.g., webinars dropping from one-month to 30-minute effort), SEs attempt projects they wouldn't have tried before, leading to unexpected business outcomes like technical deep-dive opportunities from targeted webinars.
- Approving templates upstream rather than reviewing every individual request shifts the dependency model—other teams become gatekeepers of the pattern, not the execution, which preserves brand consistency and governance while enabling autonomy.
Topics
Transcript
Hey there and welcome to Leading Pre-Sales, the show for solution engineering leaders who want to build teams that drive revenue and not just demos. My name is Tim and I'm the co-founder of SE Rockstars and together with Jan, we've coached over 350 solution engineers and their leaders across several dozens of companies. Every conversation you hear on this show is based on real coaching situations, real challenges, real problems that SE leaders like you are dealing with right now. None of this is made up. We use AI to bring these stories to life through our two hosts, Nate and Ava, but the insights come straight from the trenches. Each episode gives you one actionable takeaway you can…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Leading PreSales | The Solution Engineering Leadership Show
The Iceberg Under Every Build Deal [91]
Solution engineering leaders need a standardized five-year cost model to evaluate Build vs. Buy decisions in the AI era, grounded in hidden maintenance costs and opportunity expenses rather than vendor pitches. The key is creating an 'iceberg checklist' of often-overlooked costs and having customers co-create the financial analysis rather than presenting a pre-built case.
Leaderboards, Not Cameras [89]
The episode examines why AI adoption dashboards and leaderboards often fail to drive behavior change, and proposes an alternative approach: publicly sharing AI workflows that actually shipped on real deals, ranked by peer reuse rather than usage metrics.
Your SEs Just Inherited the Customer's Bill [88]
Solution engineers must own usage estimation and sizing in consumption-based pricing models, even though they don't set prices. When SEs fail to accurately estimate how often workflows trigger, customers face billing surprises that damage relationships and renewals.
Rebrand or Real Role? The FDE Test [86]
The episode examines whether Forward Deployed Engineers (FDEs) represent a genuinely different role from Solution Engineers or merely a rebranding strategy. Through analysis of real job postings and market trends, the hosts present a three-question test to distinguish authentic FDE positions from SE roles with inflated titles.
No Quota, Still Commercial [85]
Forward Deployed Engineers (FDEs) should be measured on time-to-first-value and usage ramp rather than traditional sales quotas, with compensation tied to commercial outcomes that directly correlate to revenue under consumption pricing models. Success requires a disciplined 10x cost-recovery model, a defined pilot-to-contract path, and mandatory product feedback loops to prevent FDE teams from becoming expensive consulting operations.