For Account Executives

You’re an AE. You live in your CRM, your inbox, your Zoom calls, and your LLM of choice. Claresia adds 5 skills to your LLM picker that fold into that flow without yet another tab.

This page walks you through your first week with Claresia.

What landed in your LLM

When IT pushed Claresia for the AE Cowork, your @claresia picker now shows:

Skill	When you’d use it
sailford.pipeline-hygiene	Monday morning — review your open opps
sailford.deal-summary	Before any internal deal review
sailford.competitive-battlecard	When a competitor name surfaces in a call
sailford.discovery-call-prep	Night before a discovery call
sailford.proposal-outline	After a successful demo, before drafting

(Your IT admin may have added sailford.account-research and sailford.sequence-builder if you’re on the Enterprise Cowork — check Command Center.)

Day 1 — your Monday pipeline review

You open your LLM (Claude / Copilot / ChatGPT) and type:

@claresia.sailford.pipeline-hygiene

A parameter form appears:

• CRM filter: all_open (or won_this_quarter, slipping_this_week, …)
• Top N: 10 (typical)

You hit submit. Within ~3 seconds, you get a structured Adaptive Card:

Pipeline Hygiene — 10 opps reviewed

🔴 Acme Inc — $120K, Stage: Negotiation, no activity 12 days

• Action: Re-engage. Last touch: pricing follow-up email Apr 21.

🟡 TechCo — $87K, Stage: Demo, MEDDPICC weak on Champion

• Action: Map Champion this week. Suggested questions: …

✅ 8 other opps healthy.

---

Claresia · Pipeline Hygiene · $0.04 · 2.3s · View record

You can:

• Click View record to see the full Hub record (with provenance)
• Click Re-run to get an updated view tomorrow
• Forward the response to your manager for the 1:1

What’s happening behind the scenes

• The skill calls your CRM through a Claresia connector (you authorized once at install)
• It reads your open opps, scores hygiene per a configurable rubric
• Output is logged to your org’s Hub as an output record
• Telemetry envelope is logged to your tenant’s fn_telemetry_event
• Your maturity progress bar advances by one invocation

Day 2 — pre-discovery call prep

Tomorrow’s 9 AM is a discovery call with a new logo. You type:

@claresia.sailford.discovery-call-prep

Parameters:

• Account name: Globex Manufacturing
• Persona on call: VP Operations

Returns:

Discovery Call Prep — Globex Manufacturing × VP Operations

Account snapshot

Globex is a mid-market mfg supplier in the Midwest, 1,200 FTE, S&P 700-ish. Recent funding: Series C $40M Aug 2025. Public earnings call mentioned “AI productivity initiative — board mandate.”

Key signals

• 6 LinkedIn job posts last 60 days for Continuous Improvement Engineers
• CIO Mark Smith joined Q1 2025 from a Glean customer
• On record: “20% cost-out target by FY27”

Suggested discovery questions

1. “How is Mark’s AI productivity mandate translating into team-level OKRs?”
2. “Where in your operations is the highest variance in cycle time?”
3. “What does your current AI tooling stack look like at the engineering and ops layer?”

Suggested next-steps

• Mention the cc-053 Maturity Engine as a pilot proof
• Offer the cc-052 Synthetic Twin as a Phase-0 instrument

After the call, you’ll likely run sailford.deal-summary to capture the next steps as a Hub decision record.

Day 3 — you hit a competitive threat

Mid-call, the prospect mentions Glean. You type (in your LLM, mid-call):

@claresia.sailford.competitive-battlecard

Parameters:

• Competitor: Glean
• Deal context: Mid-market manufacturing, 1,200 FTE, AI-buyer panel

Returns the up-to-date battlecard sourced from your team’s competitive intel + Sailford’s research (if your tenant subscribes to Sailford competitive intel service).

You drop the relevant 2 talking points into the call.

Day 4 — post-demo proposal outline

The demo went well. You type:

@claresia.sailford.proposal-outline

Parameters:

• Account: Globex Manufacturing
• Product fit: PowerLens + DeepLens + Command Center
• Confirmed pain: Variance in cycle time across 8 plants; can't quantify AI ROI
• Decision criteria: Time-to-ROI < 6 months; CISO sign-off

Returns a structured proposal outline. You drop into your CRM’s proposal template (Word / Google Docs).

Day 5 — the weekly readout

Friday afternoon, your manager runs boss.team-weekly-digest for the team. She’ll see your invocations summarized: 4 this week, 0 failures, ~3.2 hours estimated time-saved. Your maturity bar advanced to L1: 75%.

What’s logged where

Every skill invocation creates these Hub records (queryable in Hub Browser):

Record	What it captures
output	The skill’s full response body, timestamp, cost, latency
telemetry_event	The envelope (skill_id, success, latency, cost)
decision (when you click “Capture decision”)	A HITL approval/rejection on the output

Your manager and IT admin can see the envelope-only view (skill, timestamp, cost, success). They cannot see your CRM-level details unless they’re in your chain of command (RBAC enforced).

Tips from real AEs

• Run pipeline-hygiene every Monday — it becomes a 5-min Monday ritual that saves 30+ min of manual stage review.
• Run deal-summary the night before any pipeline review — it does the MEDDPICC fill for you.
• Don’t run discovery-call-prep at 8:55 AM for a 9 AM call. Run it the night before — the model needs to think, and you need to read it.
• Use re-run liberally. Every run is logged to the Hub; the cost is ~$0.04. You’re not consuming a quota.

Maturity progression

You’ll progress L0 → L1 in ~4 weeks (Cowork target):

• L0 → L1: 8+ invocations/week, 3+ unique skills, 4 weeks
• L1 → L2: take a quarterly assessment + use 5+ skills/week + ship 2 multi-step workflows in your LLM

L1 = “AI Adopted Operator” badge in your LinkedIn (if you opt in) L2 = “Agent Operator” badge — meaningful for your career

Where to get help

• In-app coaching — type @claresia.forge.coaching-session for a Socratic walk-through
• Your CSM — in your Slack/Teams Connect channel
• Docs — this site (you’re on it)