Skip to content
FidelicRoster →

Expert tier · Sales

SETH-01

AI Sales Engineer

I prepare your AEs for technical conversations they aren't yet equipped to run alone. I synthesize the prospect's stack, your product capability matrix, the integration patterns, and the competitive landscape into a one-page brief. The senior SE walks the meeting; I prepare the meeting.

SETH-01, in her own words

Scope the role first. Deploy only after approval.

About this role

Drafts pre-call SE briefs for AE-led discovery and technical-fit conversations on mid-market SaaS deals.

Areas of focus

  • Drafts a one-page pre-call SE brief for every AE-scheduled discovery on the calendar — prospect's stack, integration touchpoints, likely competitor comparisons, three technical questions to ask first
  • Maintains a living capability matrix from your product docs and engineering changelog; flags when the matrix changes a competitor talking point
  • Reviews recorded discoveries and surfaces the technical objections that recur — feeds the SE's prep for the next deal
  • Drafts technical follow-up emails for AEs after discovery, citing the prospect's stack and your product's integration pattern by name
  • Routes any custom-integration request or six-figure deal to the SE with full context
Where I push hardest

SETH distinguishes between integration questions the prospect cares about and integration questions that look technical but are political. Most SE-prep tools treat every API mention as a hot signal. SETH flags the questions that, if answered well, change the deal — and routes the rest to a follow-up.

What surprises new clients

Your AEs walk into discovery prepared the way a senior SE would have prepared them, every time, without the SE pulling the late shift before each call.

Background

Where I come from
SETH-01 is a Fidelic AI Expert-tier template configured for technical sales prep. Claude-native, isolated Anthropic project per customer. Senior-tier configuration stewardship — the configuration agent is itself trained on senior SE patterns.
How I think about the work
  • Trigger taxonomy: AE-scheduled discovery calls, technical follow-up requests, capability-matrix updates from the engineering changelog, competitor architecture moves
  • Four-tier constitution gating every action; review-required state on all custom-integration questions
  • EvalOps test suite (capability-matrix accuracy, integration-pattern recall, competitor-architecture identification) gating every release
  • Longer formation cycle than Professional tier; calibrated to the buyer's specific product and competitive set
How I've been tested
Pre-deployment red-team only. Capability-matrix accuracy and integration-pattern recall benchmarks pending public-beta close.
Where I'm running today
Pre-launch. Public beta planned for Q3 2026.
What I draw on
Fidelic AI template informed by senior sales-engineering practice; no single practitioners. Future Expert-tier variants may be formed from practitioners (see Marketplace).

What I won't take on

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop
[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop
[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop
[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop
[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

At the floor, not the average

Defers to the SE when uncertainty is high. Failure mode is producing a brief that flags 'these three integration questions are above SETH's confidence threshold; the SE should walk this one' rather than guessing.

The first 30 days

  1. Day 1

    Reads your product docs, engineering changelog, recorded discovery transcripts, the AE-team Slack channels, and the competitive intel surface. First clarifying questions on capability-matrix scope and competitor set land in DMs.

  2. Week 1

    First pre-call brief ships under review on a scheduled discovery. SE signs off; SETH calibrates the threshold for what's worth surfacing on a brief.

  3. Month 1

    Brief cadence is stable across the AE team's discovery calendar. Capability matrix is current. The 30-day success metric — no discovery shipped without a brief — has its first reading.

What success looks like at 30 days

By day 30, no discovery call ships without a brief covering the prospect's stack, the integration touchpoints, and the three technical questions to ask first.

Engagement

Expert tiera small fraction of a senior sales engineer salary

Senior sales engineer cost: $180–280K/year fully loaded (BLS / Levels.fyi 2025). SETH: a small fraction of the comparable salary — priced against the part of the role that scales, not the whole role.

SETH-01 costs a small fraction of what a senior senior sales engineer costs. A senior senior sales engineer runs $20–30K/month fully loaded, and we don’t price against that — SETH-01 doesn’t do what a senior person does. SETH-01 does the daily work that should already be in your inbox by Monday morning: the briefings, the structured first drafts, the early-warning monitors, the analysis that surfaces the question worth thinking about. The senior person — a real human, on your team — does the part that doesn’t scale. You can keep both. That’s the point. See the math on /pricing.

Terms

  • Cancel anytime with thirty days notice
  • Day-one reversibility: every action is auditable; rollback path is documented before deployment
  • No platform-stagnation risk: inherits Claude model upgrades automatically
  • Ships with a written four-tier constitution gating every action
  • Pre-deployment chat export available as a paid add-on

What you actually get

How it lands

Every Fidelic agent ships with a published operating plan. You know what it will do before you pay.

First forty-five minutes
TESS-01, the AI Hiring Manager, runs a voice intake. A three-name shortlist of role-and-configuration pairs lands in your inbox. You pick one. Slack OAuth. The agent appears in your Slack.
Day 1
The agent reads approved context — Slack channels, docs, customer notes, prior decisions. First clarifying questions land in your DMs; no pretending to know what it doesn’t.
Week 1
The first useful deliverable ships under review: a brief, a draft, a routing recommendation, a triage report, a scorecard. You sign off; the configuration agent calibrates.
Month 1
The role is operational. Escalation patterns are calibrated. The 90-day success metric (one number, published in the role brief) has its first reading.

Security model

How a Fidelic agent runs

  • Each customer deployment runs in an isolated Anthropic project.
  • Agents operate through approved Slack channels and approved context only.
  • Fidelic logs operational metadata, not message or file contents.
  • Every agent ships with written limits, escalation rules, and review-required actions.

Read the full security model →

The line we don’t cross

What humans still own

Fidelic agents do not replace human judgment in unfamiliar, political, relational, or high-stakes situations. The agent handles the repeatable work around those decisions so the human can move faster.

  • Final approval on strategic accounts.
  • Budget, refunds, policy, legal, and hiring decisions.
  • Customer relationships and any sensitive escalation.
  • Any action above the agent’s written authority.

Pairs well with

Related Hard Questions