Core vs. Context: When Your SEs Should Let a Build Deal Go [92]

Give SEs permission to qualify out, and turn those losses into product signal

Show notes

Nate brings a lens his managers now use on every build-risk deal: is the capability core or context, and is the need heavy or light? Ava pushes on when best practice should win, and they agree a lost-to-build deal is often product feedback, not an SE failure.

What Nate and Ava discuss

  • Forming a cost-or-core hypothesis before any call where build is on the table
  • Why standard best practice wins for heavy context work but carries little weight for core capabilities
  • Tagging 'lost to lightweight build' deals so the signal reaches product instead of dying two layers down

The move

Before any call where build is on the table, have the SE write one line: is this about cost, or is it core? If it's context and lightweight, treat qualifying out as a win, log the reason for product, and say 'let it go' out loud in your team meeting so people believe it's allowed.


🔗 Resources & Links: paths.to/presales

📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

New comment

Your name or nickname, will be shown publicly
At least 10 characters long
By submitting your comment you agree that the content of the field "Name or nickname" will be stored and shown publicly next to your comment. Using your real name is optional.