Books meetings while the pipeline builds itself.
Outbound fails on consistency, not on ideas. An AI SDR works the same list every single morning: it reads last night's product Signals, researches the accounts that moved, writes the opener for each one, sends the day's Sequence step, and handles the replies before you have finished your coffee. Every Contact, Deal, and touch lands in Revenue, so a human AE opens a pipeline that is already warm.
The two hours a day an AE loses to list building, enrichment, and copy-pasting the same email into a new tab.
- Overnight signal sweepEvery weekday, 06:40
- Daily sequence stepEvery weekday, 09:00
- Reply triageEvery 30 minutes, 08:00–19:00
- End-of-day sales noteEvery weekday, 17:45
- score-inbound-signal
- research-account
- write-first-touch
- handle-reply
- book-meeting
What Robin does between waking the servers and going quiet.
Every hour below is one Routine you can open, read, and change — including the one where it stopped and asked a human.
- 06:40
Reads what happened while everyone slept
Pulls the overnight Signals — trials started, seats added, docs read three times — and scores each account against the ideal-customer profile written into its Soul. 31 accounts moved; 9 are worth a human's time.
Revenue · Signals - 07:55
Builds the day's list, and kills the duplicates
Enriches 74 new Contacts, merges the 6 that already existed under a different address, and drops the 12 sitting inside an open Deal. Nobody gets prospected by a company they are already buying from.
Revenue · Contacts - 09:00
Sends the first touch
58 first-step emails go out, each one written against what that account actually did — not a merge tag with a first name in it. Sending is throttled and every address is checked against the suppression list first.
Revenue · Sequences - 10:20
Works the replies, not the inbox
Reads all 14 responses. Books 3 meetings straight into the AE's calendar, answers 5 questions from the docs, routes 2 support issues to the right queue, and honours 1 unsubscribe immediately and permanently.
Email - 11:00
Second angle on last week's silence
Re-approaches the accounts that opened but never replied — different angle, shorter, one specific question. Anything still silent after step four is closed out rather than emailed a fifth time.
Revenue · Sequences - 13:30
Asks before it crosses a line
Stopped for youOne target account is already flagged in the Customers record as an escalation with Legal. Instead of guessing, it writes a Decision with both options and the context, and moves on to the rest of the list.
Decisions - 15:10
Researches tomorrow
Reads funding news, job posts, and stack changes for the next 40 accounts, then drafts the opener for each and files the evidence on the Contact so the AE can see why it said what it said.
Revenue · Contacts - 17:45
Reports like a person would
Posts the day to the sales channel: what was sent, what came back, which 3 meetings are on the calendar, and the two accounts it thinks are dead and why.
Workspace
- 3
- Meetings on the calendar
- 118
- Emails sent, none duplicated
- 1
- Decision that needed you
- Northstar is in Legal's escalation list — do I still run outbound into it?
- Two AEs both own contacts at Vertex. Which one gets the meeting?
Answering one performs no side effect. The employee writes the question and the options itself, and an ordinary Member can answer it.
Capable in the ways that matter, bounded in the ways that count.
Research that leaves evidence
Every claim in an opener traces back to something it read — a job post, a changelog, a Signal in your own product. The sources sit on the Contact timeline, so an AE can see the reasoning before the call.
Sequences with a stop condition
Multi-step outbound with per-step delays, reply detection, and a hard stop. A Contact who replies leaves the Sequence; a Contact who never engages is closed out instead of touched a fifth time.
Suppression it cannot override
Unsubscribes, bounces, and blocked domains are checked before every send, and the employee has no tool that removes an address from the list. That is a deliberate gap, not an oversight.
Hands off cleanly
A booked meeting arrives with the thread, the research, and the reason it converted — assigned to the right human on the right Deal, not dropped in a channel for someone to notice.
Four documents, and then you stop being the trigger.
Everything that makes this an SDR rather than any other role is plain, editable text. Change how it thinks by editing a document, the way you would rewrite a job description.
How it judges
- Voice, priorities, and the lines Robin will not cross alone.
What it repeats
- score-inbound-signal
- research-account
- write-first-touch
- handle-reply
- book-meeting
When it works
- Overnight signal sweep — Every weekday, 06:40
- Daily sequence step — Every weekday, 09:00
- Reply triage — Every 30 minutes, 08:00–19:00
- End-of-day sales note — Every weekday, 17:45
What it can reach
- Gmail Connection for the outbound mailbox
- Revenue — Contacts, Deals, Sequences, Signals
- The positioning notebook in Notes
- The competitive teardown in Resources
It works your records, not a copy of them.
Everything Robin does happens inside the products your team already uses — the same rows, the same threads, the same queues. There is no export step and no second system of record.
See every productThe ones people actually ask.
- Will it send email from my domain without me seeing it?
- Only if you grant it send access. Email access levels are read, draft, and send — start it on draft, read a week of its outbound, and promote it when you trust the writing. Everything it sends is on the thread and the Contact timeline either way.
- How is this different from a sequencer with AI copy?
- A sequencer waits for someone to load a list into it. This researches the list, writes the copy, sends the step, reads the reply, and books the meeting on its own schedule — and when it hits something genuinely ambiguous it writes a Decision instead of guessing.
- What stops it from emailing the same person twice?
- Contacts are deduplicated on the way in, and an address inside an open Deal or on the suppression list is excluded before a Sequence is built. Both checks run server-side, not as an instruction in a prompt.
Every other role, working the same way.
Build an autonomous company today.
Install Genosyn, choose an AI Model, write the first role, and put it on a schedule. Tomorrow morning, one job runs without you. The company grows from there.