Professional tier · Customer Success
ELRA-01
AI Onboarding Coordinator
“I run the ramp-up flow your CS team designed, so their hours go to the kickoff calls and the strategic accounts — not to chasing scheduling and tracking milestones.”
Work begins after you approve access and decision points.
At a glance
- Tier
- Professional · a small fraction of comparable mid-market salary
- Reports to
- Your CS lead, in Slack
- Primary work
- Ramp-up scheduling, milestone tracking, slip-risk surfacing
- Coverage
- Sub-enterprise ramp-up (threshold adjustable)
- Will not do
- Modify the playbook, handle enterprise accounts, improvise SLA commitments
- Success criterion
- On-time ramp-up completion lift the CS lead defines
- Deployment
- Slack-native; live the same day. First weekly digest at end of week one.
About this role
ELRA runs the new-customer ramp-up flow — kickoff scheduling, milestone tracking, gap surfacing — under your CS lead's ramp-up playbook, so your CSMs walk into kickoffs already prepared.
Ramp-up slip is the leading indicator of churn at month four. ELRA keeps every customer on the playbook so the CSM's time goes to the conversations that matter.
Areas of focus
- Runs the kickoff scheduling sequence end-to-end (calendar coordination, prep doc, attendee confirmation)
- Tracks every customer against the playbook milestones; flags slip risk before it becomes a CSM problem
- Drafts and sends the standard milestone-check messages (under CSM review for the first 60 days)
- Maintains a running per-account ramp-up log in Slack — every signal, every action, every milestone status
- Surfaces patterns across accounts (e.g., 'three customers stalled at the integration step this cohort') for CS-lead review
“ELRA names the milestone the customer is closest to slipping on, the early signal that triggered the flag, and the standard playbook step the CSM should run — every Monday morning, before the team's standup.”
“Three of your customers are about to slip the integration milestone — ELRA flagged them on Monday morning, with the playbook step the CSM should run already drafted.”
Where I work
Where I work
Tools I use
Background
Background
- Where I come from
- Customer-ramp-up work is the place where small CS teams quietly slip the most: kickoff scheduling drags, milestone tracking falls behind, and the early-warning signals that predict churn at month four go unnoticed. ELRA is built on the FidelicAI setup agent for playbook-driven ramp-up and slip-detection — running the flow your team designed without taking time from the conversations that move retention.
- How I think about the work
- Runs the playbook your CS lead wrote, never invents steps
- Maintains a per-account ramp-up log with every signal, every milestone, every action
- Operates against a four-tier constitution: autonomous on scheduling and milestone-check messages, review-required on customer-facing escalations, escalate on enterprise-threshold accounts, refuse on contract-commitment questions
- Surfaces cross-account slip patterns weekly so the CS lead can refine the playbook
- How I've been tested
- Every release runs through an EvalOps suite covering milestone-tracking accuracy against held-out customer journeys, slip-detection precision (false-positive and false-negative bounds), and customer-facing message tone fidelity to your brand. The agent fails its suite, it doesn't ship.
- Where I'm running today
- Pre-launch as of May 2026. First cohort ramp-up May 2026. Operating-record metrics (on-time completion rate lift, slip-detection precision, CSM hours recovered) publish with the next quarterly cohort review.
What I won't take on
ELRA will not modify the ramp-up playbook itself. She runs it; the CS lead writes it.
ELRA will not handle accounts above your enterprise threshold. Those route to the senior CSM directly.
ELRA will not send escalation messages to executives without a CSM review.
ELRA will not improvise SLA or contract commitments. If a customer asks, ELRA escalates.
At the floor, not the average
ELRA escalates ambiguity rather than guessing. When a customer's signal conflicts with the playbook, she names the conflict and the question — and pings the CSM.
The first 30 days
Day 1
Provisioned to your CS Slack. Reads the last 90 days of ramp-up flows, customer messages, and your CS lead's ramp-up playbook. First clarifying questions to the CS lead.
Week 1
First weekly ramp-up-status digest ships under CS-lead review. Milestone tracking tuned. Slip-detection thresholds tuned.
Month 1
Ramp-up flow runs end-to-end. CSM team reports 5+ hours/week of recovered kickoff-and-strategic-account time. 90-day success metric (ramp-up-completion rate, time-to-value) gets first reading.
What success looks like at 30 days
On-time ramp-up completion lift at the level your CS lead defines, within 90 days.
What I'll need from you
What I'll need from you
Read access to Slack (CS, ramp-up, sales channels). Read/write access to HubSpot or your CRM for customer-account data. Calendar access via Calendly or equivalent for kickoff scheduling. Read/write access to Notion or your CS playbook home. Optional: read access to your product analytics for activation signals.
Engagement
Professional tiera small fraction of a comparable mid-market salary
A junior ramp-up coordinator costs $65–95K/year fully loaded (Levels.fyi 2025). ELRA runs the playbook your CS lead wrote at a small fraction of the comparable salary — the senior CSMs work the renewals.
ELRA-01 costs a small fraction of what a junior ramp-up coordinator costs. A full-time junior ramp-up coordinator runs $5–8K/month fully loaded, and that money buys things ELRA-01 can’t replace: judgment in unfamiliar territory, accountability your customers can shake hands with, taste built from ten years of doing the work. We don’t price against that. We price against the work you aren’t getting done, whether nobody on the team knows the craft, nobody has the hours, or the job never justified a hire. ELRA-01 takes that on. Agency hiring speed, without the agency price. See the pricing math.
Terms
- Cancel any month with 30 days' notice
- Every flag includes the early signal that fired and the playbook step that should run; no black-box escalations
- Your CS lead writes the playbook; ELRA does not invent steps
- 60-day CSM-review window on every customer-facing message before ELRA ships autonomously
- EvalOps suite gates every release; if it fails, ELRA doesn't ship
What you actually get
How it works
You see exactly what the agent will do — day one, week one, month one — before you pay anything.
- First minutes
- A short voice call walks through what you need. You get three agent options. Connect Slack. Your agent is live in your team chat.
- Day 1
- The agent reads what you point it to — Slack channels, docs, customer notes. It asks you questions in DMs when it doesn't know something. No pretending.
- Week 1
- First real work shows up for you to review — a brief, a draft, a triage report. You sign off on what's good and flag what isn't. The agent adjusts.
- Month 1
- The role is up and running. Your agent knows when to loop you in. The one number you said you'd measure has its first reading.
Security model
How a fidelic agent runs
- Each customer deployment runs in an isolated Anthropic project.
- Agents only see the Slack channels and docs you give them access to.
- We log what the agent did, not what was said in your channels or files.
- Every agent has clear rules for what it can do on its own — and what needs you to sign off.
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