The GUI Is Dead. Long Live the API. [18]

The GUI Is Dead. Long Live the API. [18]

When your buyer asks for an MCP server, can you answer? 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. WHAT NATE AND AVA DISCUSS * 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 THE MOVE 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. ---------------------------------------- 🔗 Resources & Links: paths.to/presales [https://paths.to/presales] 📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call [https://calendly.com/serockstars-tim/discovery-call]

Nobody Showed Up — Because You Didn't [17]

Why your team quit the training you bought them — and the five-minute fix. 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. WHAT NATE AND AVA DISCUSS * 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 THE MOVE 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. ---------------------------------------- 🔗 Resources & Links: paths.to/presales [https://paths.to/presales] 📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call [https://calendly.com/serockstars-tim/discovery-call]

Fifty Times Faster, Fifty Times Wrong [16]

Why AI is making your discovery gaps bigger, not smaller. 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. WHAT NATE AND AVA DISCUSS * 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 THE MOVE 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. ---------------------------------------- 🔗 Resources & Links: paths.to/presales [https://paths.to/presales] 📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call [https://calendly.com/serockstars-tim/discovery-call]

The SE Who Rewired the Team [15]

What happens when one curious SE on your team quietly rewires the whole job. 🎙️ Live webinar May 21: Tim & Jan on building a PreSales team that drives revenue — not just demos. serockstars.com/webinar [https://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. WHAT NATE AND AVA DISCUSS * What Marcus built: agent orchestration wired into CRM, deal conversations, knowledge base, and the product via MCP server — spins up a tailored demo environment in four minutes * The standardization tension: the floor goes up for everyone (even the two-months-in SE) but the ceiling — reading the room, catching an exec's pause — is still human * The coaching and hiring shift: stop coaching the template, coach the judgment. The "organized operator" profile just got cheap * The bus factor: what if Marcus leaves? A real risk Ava actively manages through pairing and documentation * Nate's enterprise reality: six-month security reviews mean he can't ship this yet — so he's starting with the context layer, a fight he can win this year THE MOVE 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. ---------------------------------------- 🔗 Resources & Links: paths.to/presales [https://paths.to/presales] 📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call [https://calendly.com/serockstars-tim/discovery-call]

Prep the People, Not Just the Demo [14]

Why your demo prep survived everything except the actual demo 🎙️ Live webinar May 21: Tim & Jan on building a PreSales team that drives revenue — not just demos. serockstars.com/webinar [https://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? WHAT NATE AND AVA DISCUSS * Why dry runs rehearse content but not behavior — and why that gap kills complex demos * The "rules of engagement" conversation: scripting reactions, not just presentations * Giving AEs an active role during demos instead of asking them to stay quiet THE MOVE 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. ---------------------------------------- 🔗 Resources & Links: paths.to/presales [https://paths.to/presales] 📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call [https://calendly.com/serockstars-tim/discovery-call]