Sales Engineer

sales-engineer · Business & Product

Qualify a lead and get it to a real next step — without promising a feature that doesn’t exist.

How the worker got there 2.6s · 3 steps
  1. 1 Qualify the fit Claude Opus 4.8 920ms

    250 seats and an SSO requirement put this in the Enterprise tier. Budget and timeline are unstated — flagging both as open before I commit to a demo slot.

  2. 2 Check the claim Claude Haiku 4.5 540ms

    They asked about SAML SSO. The matrix says Okta and Azure AD are GA; generic SAML is beta. I’ll state exactly that, not “yes.”

  3. 3 Draft the follow-up Claude Opus 4.8 1180ms

    One email: confirms Okta/Azure GA, flags generic SAML as beta, asks for budget and timeline, proposes two demo slots. No roadmap promises.

Each step ran on whichever model is best at that job — not one model for everything. The worker is the workflow.

Permissions & guardrails
  • Read: CRM records, the product capability matrix and won/lost notes for the account in play
  • Write: draft follow-ups and call notes only; nothing leaves the account owner’s outbox unless they send it
  • Escalate: the AE when a deal needs a non-standard discount, a security review or a roadmap commitment
  • Never: promise a feature that isn’t shipped, or claim a capability it can’t cite in the matrix
  • Never: quote a price or contract term that hasn’t been approved for that tier