Fit score
85/100
Tier A · routed to an AE
B2B software · SaaS
All industries
Amelia
AE–1932Agentic SDR
Sell software with signal, not volume.
She reads the account before anyone picks up the phone, scores it on weightings you set, answers the product questions from your own docs, and books the demo while your team sleeps.
- Grounded in
- Your docs · your pricing
- Scores on
- Fixed weightings you own
- Writes into
- Your CRM · your calendar
01
Understanding the account
Know the company. Know the number.
A form fill tells you an email address. This tells you whether the deal is worth your best rep's Tuesday.
Currently
Qualifying 14 accounts
4 channels · 3 languages
Never
Quotes a price she made up
02
What she does for a software team
An SDR who reads every account before she opens her mouth.
Not a chatbot in front of a pricing page. She resolves the company, prices the seats from your own plan, and tells an AE what is actually worth their Tuesday.
The six capabilities below are the same ones she runs in every industry. What changes here is the catalogue she reads and the arithmetic she does.
Autonomous Lead Discovery
She works your ICP continuously and surfaces accounts showing the signals you told her matter, before a form is ever filled in.
Firmographics · stack · hiring · funding
Instant Response Sales Concierge
The enquiry that arrives at 02:14 gets a real answer at 02:15 — not an auto-reply promising one.
Median first reply measured in seconds
AI Lead Qualification
Company size, stack fit, budget, intent and timing, scored 0–100 on weightings your team sets and can see.
Same inputs, same score, every time
Multi-Channel Sales Conversations
A thread that starts in web chat and continues by email stays one conversation, against one account record.
Web · Email · WhatsApp · Instagram · Messenger · Telegram
Product Intelligence
Integrations, limits, security posture, migration path, price at their seat count — answered from your docs and price book, or flagged as unknown.
Grounded in your material, not the open internet
Autonomous Demo Scheduling
She reads the AE's calendar, offers what is genuinely free, books it, and sends the brief before the call.
Writes into the calendar your team already uses
03
The signals she reads
Intent is not a feeling. It leaves a trail.
Four families of signal, each one either confirmed against a source or reported as unconfirmed. Nothing is inferred and then quoted as fact.
Firmographic
Headcount, region, funding stage, ownership, growth rate. The facts that decide whether you can serve them at all.
Confirmed against public records
Technographic
What they already run, what it costs them, and whether you replace it or sit beside it.
Self-reported or observed — labelled either way
Behavioural
Pages revisited, documents downloaded, the question asked twice. What they do rather than what they say.
From your own site and conversations
Timing
A renewal date, a new VP, a funding round, a hiring spree. The difference between a good account and a good quarter.
Stated by the buyer or filed publicly
The rule that matters more than any signal
If a fact cannot be traced to a source, it is shown as unconfirmed and the rep is told. An agent that fills a gap with a plausible guess is worse than one that leaves it empty, because your team stops being able to tell the difference.
04
The numbers
Put your own figures in. The answer changes as you type.
No industry averages borrowed from somebody else's blog post. Every input below is yours, including the one assumption this model cannot make for you.
05
Comparing the accounts
Three accounts. Change what you value, and the ranking moves.
The biggest deal, the best fit and the best return on a rep's time are three different companies. A ranked list that hides that is not intelligence, it is decoration.
06
Both sides of the table
One system, and nobody is working from a different set of numbers.
Your AEs see the pipeline she qualified. Your buyer sees the figures she explained. Neither is waiting on the other.
07
Why this way
The same inbound, handled two different ways.
Not a criticism of your SDRs. Just what happens when research, pricing and chasing stop being their job.
Dimension
How it usually runs
With Amelia
Inbound at 02:00
Auto-reply now, a human in nine hours
A real answer, with a price, in under a minute
Account research
Twenty minutes of tab-hopping per lead, if anyone has time
Done before the reply goes out, with every source named
Qualification
A gut call, and a different bar from each SDR
Scored 0–100 on weightings you set and can audit
Pricing questions
"Contact us", then a range, then a call to narrow it
The actual figure at their seat count, from your price book
Competitive questions
Deflected, or answered from a battlecard written last year
Answered straight, including where you are weaker
The handover to an AE
A transcript, and a buyer repeating themselves
A brief, the open objection, and the demo already in the diary
08
The handoff
She does the research. Your AE does the deal.
The moment a conversation turns into a commitment, it belongs to a person. She recognises it, writes the brief, and steps aside.
09
The philosophy
Buying software is a route through uncertainty.
Named for a navigator, not an oracle. She does not know whether this deal closes — nobody does. She knows what the instruments say, and she says it the same way to everyone.
A form fill
A company
A fit
A price
A brief
A deal
The last step belongs to your AE. Every step before it is hers.
“Route optimisation is where they are stronger, and I would not pretend otherwise.”
Amelia · Agentic SDR
The end of the route
Give her your docs, your price book and your calendar.
She will take it from the enquiry at 02:14 to the moment your AE opens a call already knowing the answer to their first three questions.
Start with the obvious question
A chatbot answers the message in front of it. I resolve the company behind it, score
it against your weightings, price the seats from your own plan, book the demo and
write the brief. The conversation is the smallest part of the job.
Prices come out of your price book and are computed, not written. Product answers come
from your documentation. If a question lands outside both, I say I do not know and
flag it for a human — which is the only honest answer and the only safe one.
No. I write into the CRM and calendar your team already uses. The point is that your
AEs open the tools they already open and find the work done.