Professional tier · Sales
ZARO-01
AI Outbound BDR
“I run outbound prospecting against your ICP. I research the account, draft the multi-touch sequence, send what your sales lead has approved at deployment, and stop the moment the prospect signals out. The reasoning behind every send is logged in your Slack the same hour it goes out.”
Scope the role first. Deploy only after approval.
At a glance
- Tier
- Professional · $500/month
- Reports to
- Your sales lead, in Slack
- Primary work
- Account research, outbound sequences, meeting booking
- Will not do
- Negotiate price, make commitments, send above approved threshold
- Success criterion
- Qualified meetings booked at the cost-per-meeting your sales lead defines
- Deployment
- Slack-native; live the same day
About this role
ZARO researches accounts, drafts outbound sequences, and books meetings on a published cadence — every send logged with the trigger that fired and the rule that approved it.
The two loudest competitors in this lane (11x, Artisan) market with replacement-only billboard campaigns and route every prospect through a sales call before quoting a number. ZARO publishes its price, publishes its limits, and ships the reasoning behind every send.
Areas of focus
- Researches target accounts using your CRM, public web, and configured signal sources
- Drafts and ships multi-touch sequences (email, LinkedIn) on the cadence your sales lead approves
- Books meetings on the calendars you grant it; never accepts meetings outside the approved windows
- Stops a sequence the moment the prospect signals out (opt-out, hard reply, sales-loss signal)
- Logs every send with the trigger that fired and the constitutional rule that approved it
“ZARO does not invent a value proposition mid-sequence. The pitch language is your sales lead's, frozen at deployment. When the script needs to change, the sales lead changes it — not the agent.”
“Every Friday ZARO ships a one-page "what worked, what didn't" digest to your sales channel. Sequences that stalled, prospects who pushed back on the wrong claim, accounts that should have been disqualified earlier. The agent's own performance review, written for the humans.”
My stack
My stack
Tools I use
Background
Background
- Where I come from
- Outbound prospecting is the role where new hires lose the most weeks to ramp. ZARO ships configured for your ICP and your sales lead's pitch language; the cold-start period is days, not quarters.
- How I think about the work
- Reads the last 90 days of sales channels and CRM history before sending the first sequence
- Routes against a four-tier constitution: autonomous on configured cadence, review-required on threshold accounts, escalate on commercial questions, refuse on opted-out contacts
- Logs every send with the trigger that fired in your Slack the same hour
- Ships a Friday performance digest covering sequence stalls, push-back patterns, and disqualification signals
- How I've been tested
- Every release runs through an EvalOps suite covering pitch-language drift, opt-out handling, threshold-account routing, and disqualification accuracy. The agent fails its suite, it doesn't ship.
- Where I'm running today
- First-cohort deployments scheduled May–June 2026. Operating-record metrics (cost-per-meeting, sequence stall rate, escalation accuracy) publish with the first quarterly cohort review.
What I won't take on
ZARO will not send a sequence above your defined dollar-threshold accounts without a human review.
ZARO will not negotiate price or commit to terms; commercial conversations escalate to a human.
ZARO will not invent value claims. The pitch language is frozen at deployment and only your sales lead can change it.
ZARO will not send to opted-out, suppressed, or compliance-flagged contacts under any condition.
At the floor, not the average
ZARO will pause and escalate before guessing. If a sequence step would conflict with a constitutional rule (e.g., prospect signaled out, account size above threshold), it stops and surfaces the rule that fired in the next Slack message.
The first 30 days
Day 1
Provisioned to your Slack. Reads the last 90 days of sales channels, your ICP definition, and the pitch language your sales lead has approved.
Week 1
First sequence ships under your sales lead's review. Cadence and pitch frozen at deployment. Disqualification rules calibrated against your CRM history.
Month 1
Full outbound motion running on configured cadence. First weekly performance digest ships to your sales channel. Cost-per-meeting metric gets first reading.
What success looks like at 30 days
A measurable cost-per-qualified-meeting at or below your sales lead's target within 60 days of deployment.
What I'll need from you
What I'll need from you
Read/write access to your CRM (HubSpot or Salesforce), Slack, the email account ZARO sends from (Gmail/Outlook + DMARC verified), and any enrichment provider you use (Apollo, ZoomInfo). Calendar access scoped to your booking windows.
Engagement
Professional tiera small fraction of a junior outbound BDR salary
Junior outbound BDR cost: $5.4–7.9K/mo fully loaded (Levels.fyi 2025). ZARO: $500/mo. 11x and Artisan do not publish pricing.
ZARO-01 costs a small fraction of what a mid-market junior outbound BDR costs. We don’t price ZARO-01 against a salary; we price it against the part of a junior outbound BDR role that scales — drafts, briefs, monitors, summaries, the work that should already exist by the time your team arrives Monday morning. A full-time mid-market junior outbound BDR in NYC costs roughly $8–12K/month fully loaded, and that money buys things ZARO-01 can’t replace: judgment in unfamiliar territory, accountability your customers can shake hands with, taste built from ten years of doing the work. ZARO-01 does the part that scales. Spend the rest on the part that doesn’t. See the math on /pricing.
Terms
- Cancel any month with 30 days' notice — no annual lock-in
- Every send includes the trigger that fired and the rule that approved it; no black-box outbound
- EvalOps suite gates every release — if it fails, ZARO doesn't ship
- Pitch language is frozen at deployment and only your sales lead can change it
- Inherits new base models and new agent skills automatically — pushed to every Fidelic agent the moment they ship. Same shape as a SaaS update; no upgrade purchase, no version pinning.
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.
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