Leading PreSales | The Solution Engineering Leadership Show

An SE leader running thirty SEs across multiple markets split his enablement into two completely separate tracks: an internal team for product knowledge and an external partner for sales skills. They never overlap — and that's the point.

Split your enablement into two tracks. Internal team owns product knowledge, demos, technical onboarding. External partner owns sales methodology, discovery, positioning. Protect both calendars equally — the moment a product release eats your sales skills time, you're back to one pillar pretending to be two.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

An SE leader scaled from three to thirteen direct reports in eighteen months before getting team leads approved. By the time he got the structure, he wasn't coaching anyone — he was doing triage.

If you have more than six direct reports and your team is still growing, start the team-lead conversation with your leadership today. Build the case around what you could be doing with freed-up capacity — and start identifying the SEs other SEs already go to for advice. Don't wait until you're drowning to ask for a lifeboat.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

An SE leader scaling from five to twenty SEs stopped hiring from the presales talent pool. His last six hires were former controllers and accountants from his customers' world — and they got into customer meetings independently in three months instead of four.

If you're in a vertical product company struggling to find SE talent, look at your customer's org chart. Rewrite the job description around the domain ("deep understanding of financial close processes") instead of years of presales experience — then redirect the budget you save on product training into structured sales skills development.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

When demos commoditize and AI-first competitors look better on paper, what wins deals? Nate makes the case that accountability is now the durable moat — and explains how SE leaders need to retrain teams to sell it.

• Why auditors, lawyers, and tax advisors still get paid in an LLM world
• The CFO question that ends most AI-first vendor pitches: "if the model is wrong, who pays?"
• Why accountability can't be demoed — but it can be told
• Where to find the stories that aren't in your sales library yet

This week, pull your team's last ten customer reference stories. Read each one with a single question — "is this about features delivered, or outcomes owned?" The ratio tells you exactly where to invest in training and content this quarter.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

Roadmaps are wishlists. Release notes are receipts. Ava walks through how she now evaluates every vendor when she's buying software for her own team — and why the way she buys today is exactly how her customers will buy from her tomorrow.

• Why a 12-month roadmap is the wrong artifact to evaluate a vendor on
• Cadence relative to peer set: how to compare release velocity without comparing to AI labs
• The pivot: if SE leaders are doing this as buyers, customers will start doing it too
• Why a static one-pager contradicts the velocity message — and how a live release page fixes it

This week, pull your product's last six months of public release notes. Build a live page — a URL that compiles from your release feed and updates every time you ship. Put it in front of every SE on your team.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

SaaS vendors are still hiding their API behind the Enterprise tier — and your customers are about to start asking for it. Nate breaks down what API maturity now means for SE leaders, both as buyers and as builders of their own product story.

• Why the GUI is becoming the wrong place for products to be evaluated
• The backwards pricing logic of "free GUI, Enterprise-only API"
• How customer expectations are shifting toward agentic, MCP-aware workflows
• The two-way move: audit your own product's API maturity AND your team's vendor selection process

This week, walk over to product and ask "what's our API surface, and is it gated behind which tier?" Then add API/MCP availability to your team's own vendor evaluation rubric. Don't pick tools your future workflows can't talk to.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

Ava sent her whole team to a leadership course — twelve SEs, six finished. She was ready to blame the vendor, until one of her SEs handed her a mirror: "You never mentioned it again after kickoff." Nate and Ava dig into why the content was never the problem.

• Why identical training lands at 80% completion for some managers and 30% for others — the only variable is whether the manager acts like it matters
• "The manager is the program": a course is step one of ten, not ten of ten
• The five-minute weekly habit — name one concept, reference it in 1:1s, let peers reinforce it
• The hard line: if you wouldn't bring it up in your next 1:1, don't enroll your team

Pick ONE idea from whatever training your team is in right now. Name it in your next 1:1 — not as homework, as signal. Reference it the next time your team is together. Your calendar is the training program.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

Nate shares an experiment from one of his SE Managers: two teams used the same AI demo tool with identical timelines. The team that did structured discovery first booked next meetings every time. The team that skipped it shipped polished demos that went nowhere.

• Why AI amplifies bad discovery instead of replacing it
• The pain chain: a fifteen-minute gate that transforms demo quality
• How the AI productivity race is quietly killing the discovery skill

Before your SEs touch any AI demo tool, require a one-page pain chain. Start with the surface complaint and walk it up until you land on a metric the CFO actually cares about. No artifact, no demo.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

🎙️ Live webinar May 21: Tim & Jan on building a PreSales team that drives revenue — not just demos. serockstars.com/webinar

Ava's team runs on an agent orchestration setup that one of her SEs — Marcus — built on three weekends. Nate pushes on the hard questions: standardization, coaching, hiring, and what happens if Marcus leaves.

Find your Marcus. Every team has one — the SE quietly obsessed with AI, building scripts on the side. Give them oxygen; they'll build the future of your team faster than any vendor ever will. And as a leader, start thinking now about what the ceiling looks like — because in eighteen months, everyone's floor will be the same.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales

🎙️ Live webinar May 21: Tim & Jan on building a PreSales team that drives revenue — not just demos. serockstars.com/webinar

Your SE ran a dry run, sent a strategy reminder, and built a tight agenda. Five minutes in, an AE went off-script and the whole flow collapsed. Why does this keep happening — and what can SE leaders actually do about it?

Stop telling your AEs to be quiet. Give them a job — like owning the live question log — so their energy protects the demo flow instead of blowing it up. And build your rules of engagement into the dry run itself, not a Slack message after.

🚀 Join the PreSales Leadership Community: serockstars.com/community

🔗 Resources & Links: paths.to/presales