SDR · ARIA · live

One persona.
One voice. Every channel.

Aria is your SDR. She runs voice, email, and LinkedIn under one identity — so when she emails Marcus then calls, the call opens with the email context. When he replies, her voice remembers the call. Spin up as many named instances as your GTM needs — one per motion, segment, product, or geo — each with their own playbook, all inheriting from the same role memory.

Role → instances

One SDR role. Every motion you run.

Spin up as many Aria instances as your business needs. Each named instance covers a different GTM motion, book, or segment — inbound triage, enterprise outbound, SMB speed-to-lead, partner co-sell, expansion. Config inherits from the role; each instance overrides. Harmony adapts to your org chart — not the other way around.

Aria-Inbound
INBOUND · MQL triage
Handles inbound MQLs the moment they land. Qualifies, enriches, and books meetings — conversion-led opener, speed over volume.
MQLs qualified / wk247
Aria-Outbound
OUTBOUND · Net-new
Net-new outbound prospecting into target accounts. Signal-led cadences, reliability opener, multi-threaded from first touch.
Meetings booked / mo84
Aria-ENT-Outbound
ENT · OUTBOUND · ABM
Enterprise outbound into named accounts. ABM plays, 6+ personas per org, exec-level tone, patient sequencing that waits for the right signal.
Avg close38 days
Aria-SMB-Outbound
SMB · OUTBOUND
High-volume SMB outbound with speed-to-lead focus. Short cycles, direct CTAs, book-the-demo-today energy without sounding like spam.
Dials / wk1,840
Aria-Partner
PARTNER · Co-sell
Partner-sourced leads and co-selling motion. Knows which partner introduced whom, keeps the partner in the loop, credits the right rep.
Co-sell pipe / qtr$2.1M
Aria-Expansion
EXPANSION · PLG
Expansion SDR working the existing customer base. Product-signal first — converts free-tier power users and adjacent teams into paid convos.
Expansion meetings / mo62
Add your own
ANY MOTION · ANY SEGMENT
Any motion your team runs — split by product line, language, vertical, region, or customer tier. Name it, scope it, ship it in a day.
Instancesn

Scale up to however many instances you need. Split by motion, segment, product, geo, or language — whatever your GTM motion requires. Every lesson one instance learns, every other instance inherits the next day.

What Aria does

Signals in. Booked meetings out.

01 · IDENTITY

Voice + email + LinkedIn under one identity.

Aria binds all three channels to a single persona memory. When she emails Marcus and then calls, the call opens with the email context. When he replies, her voice remembers the call. One prospect. One relationship. One name on the other side.

Channels stitched at the memory layer, not the routing layer.
02 · VERTICAL DEPTH

A vertical persona, not a horizontal skin.

Each instance publishes a diffable playbook card: vocabulary (reliability vs efficiency vs compliance), objection library, regulatory guardrails, timezone rules, allowed channels. Manufacturing talks uptime. Healthcare talks HIPAA. EMEA talks GDPR. FinServ talks audit windows. Inheritable → overrideable.

The opener Aria-Inbound uses is not the opener Aria-ENT-Outbound uses.
03 · SIGNAL → ACTION

Signals routed through autonomy sliders.

New-job signal at autonomy 85% → Aria sends immediately. Funding signal at 40% → Aria drafts and asks. Churn signal on an open deal → Aria pauses her own sequence, pings Atlas in the Revenue Channel. Each action has its own leash.

Per-action autonomy. You pick the leash, she picks the move.
04 · MEMORY COMPOUNDING

Every lesson promotes to the role the next day.

When one instance's "reliability opener beats efficiency 2:1 in Manufacturing" gets vouched by a human, it becomes a promoted learning on the role page — visible to every sibling instance, and every new instance spun up after. The graph only gets sharper.

Cross-agent handoff to AE, AM, Marketing in the Revenue Channel.
Auto-setup

Connect Gong. Meet your SDR in 10 minutes.

Skip the month of configuration. Aria reads your best reps' recorded calls, parses your won deals, and writes her own ICP, persona playbook, objection library, and signal rules. You review, edit, approve — then she starts booking.

11 min
Average time from connect → Aria sending
Based on design-partner cohort · Q1 2026 · mid-market cohort
STEP 01

Connect

Pick Gong, Salesforce, HubSpot, Outreach, or SalesLoft. One-click OAuth — read-only until you approve more.

Source · oauth
Gong read-only
Last 90 days
Won deals
Statusconnected
STEP 02

Analyze

Aria reads 247 calls, 53 won deals, 118 hours of audio. Streams findings live as she clusters patterns.

Live · streaming
🎯 ICP: mid-mkt mfg, 200–2k
💬 Pain: supply-chain visibility · 74%
🏆 Hook: "40% fewer blind spots"
STEP 03

Review & approve

ICP, personas, ranked pain, objection handlers, winning messages, signals, playbooks. Edit anything. Approve per item or all at once.

Findings · editable
ICP chips4 ✓
Personas5 ✓
Objection handlers4 ✓
Playbooks3 ✓
12 findings applied
STEP 04

Go

Pick a leash — conservative, balanced, aggressive. Aria starts staging first-touches against your matching accounts.

Live · sending
Balancedhot 85% · warm 55%
Matched accts1,284
First touches47 today
live booked 2 in 3h

What Aria learns from your calls.

ICP
Your real ideal customer, not your pitch deck one.

Aria reverse-engineers the accounts you actually close — industry, size, revenue, geo — from won deals, not aspirations.

"Mid-market manufacturing, 200–2,000 FTE, $50–500M revenue, multi-site ops on SAP or Oracle."
Personas
Who actually signs, not who picks up first.

Ranked by won-deal frequency and average sentiment. Champion vs. economic buyer vs. technical gatekeeper — with the role that stalls deals flagged.

"VP Operations — primary economic buyer in 72% of won deals. VP IT is the stall point on security review."
Pain points
The phrase they use, not the phrase you use.

Clusters verbatim language from discovery calls. You'll see your buyer's words, ranked by frequency, with example quotes.

"We cannot see inventory at our Pittsburgh plant from Cincinnati in real time." — 74% of discovery calls.
Objection handlers
What your winning reps said when it worked.

For each top objection, Aria drafts the response — pulled from the exact moment in a won call where your best rep turned it.

When they say "we tried this in 2019 and it failed," say: "most failed because they ripped out the ERP. We sit on top."
Winning messages
The five lines that close.

Top-performing hooks with win-rate, tagged by stage. The generic "AI automation" pitch gets flagged as a loser.

"We cut supply-chain blind spots by 40% without ripping out your ERP." — 18 won deals, 72% win rate.
Signals
What to watch for in the wild.

Signal patterns Aria noticed in your won deals — then subscribes to external sources to catch them on new accounts.

Prospects who mention "our current vendor's contract is up" close 3.2× faster. Now a tracked signal.
Reads from
How Aria is different

The SDR-agent category, honestly compared.

Here's where Aria is sharpest, and where other tools in the category are. Everything else is table stakes and we have it too.

Dimension
Harmony · Aria
11x
Alta
Artisan (Ava)
Regie
Unify
Voice + Email under one identitySingle persona memory across channels
~
Alice + Jordan split
·
Email only
·
Email only
·
Email only
·
Signal + email
Vertical personasMfg / HC / FinServ / EMEA with tone + compliance
·
Horizontal
·
Horizontal
·
Horizontal
·
Horizontal
·
Horizontal
Cross-agent handoffTo AE, AM, Marketing with shared memory
·
·
·
·
·
Role-level memory compoundingInstance lesson → role doctrine next day
·
·
·
·
·
Outcome attributionPipeline, not activity
~
Meetings
~
Meetings
·
Activity
·
Activity
~
Signal→meeting
Multichannel sequencesTable stakes, we have them
Owned-deliverability stackWarmup, domain health, sending infra
~
Partner
~
·
~
·
The cross-role moat

"Every point tool lives inside one team. Their agents don't cross the team boundary because the team boundary is the company boundary."

Harmony ships four roles on one memory substrate. When Echo's nurture cohort trips intent, Aria has the full nurture history as first-touch context. When Aria books a call, Sage has the prospect's objection pattern queued. When the deal closes, Atlas inherits Sage's call memory and knows what the customer was promised.

That's not a feature — that's the product.

See the agent

Four steps. One flow.

From signal to handoff. The rep never leaves the Revenue Channel.

STEP 01

Aria reads the signal

Signal · 09:14
New VP of Ops · ACME
Role: Operations leadership change
Intent scorehigh
Source: LinkedIn · 2h ago

Cross-referenced with the Revenue Channel: Aria remembers ACME from Q1. Old thesis was reporting speed — new VP may have killed it.

STEP 02

Drafts in your voice

Draft · First-touch email
Marcus — saw you joined ACME 11 weeks ago. Noticed the reporting stack overlap with FieldOps who hit the same wall on exec rollups.

Quick 15 min to show how the new org is fixing it? —Aria
Tonereliability-led
Autonomyauto 85% · send

Vocabulary matches the persona playbook: reliability, not efficiency. Autonomy-aware: sends at 85%, asks at 40%.

STEP 03

Runs voice + email + LinkedIn

Cadence · all channels
Day 1 · emailsent
Day 3 · LinkedIn touchsent
Day 5 · voice dialqueued
Call opener pulls from: [email thread], [LinkedIn reply], [Q1 qualifier notes]
ONE identity

Same voice. Same memory. When Marcus replies to the email, Aria's voice remembers the call. One identity across every channel.

STEP 04

Hands off to the AE

Handoff · Revenue Channel
@Sage · @Sam — Marcus booked Thu 14:00. Pain = exec rollups. Objection library: buy-vs-build, 6-mo procurement.
Context packattached
Nurture historyEcho, 120d
shared memory

Sage prepares the rep with Aria's full qualification history. Echo's nurture touches are attached as first-touch context. The AE walks in already briefed.

Hire Aria this week.

30-minute demo. We'll plug Aria into a dataset that looks like yours — and show what one instance, scoped to your motion and segment, would book in the first 30 days. Numbers, not slides.