Performance

Our numbers,
in public.

Anyone can claim it works. We publish the dashboard: lifetime figures pooled across every client account, the dips included.

Live account data · updated June 2026
0+leads researched & worked
0+messages sent for clients
0+replies handled
0×average ROI inside six weeks
0%lifetime reply rate
0+ hrsof founder time returned

Where every lead goes.

The lifetime funnel, every account pooled. No survivorship edits.

Connections made
2,928
Messaged97.5% of connections
2,856
Replied22.0% of messaged
627
Real conversations2+ replies deep
315
Booking links sent55% of conversations
174

The machine compounds.

Reply and booking-link rates per monthly cohort of leads. The dashed tail is the current cohort, still maturing.

Replied, % of messaged Booking link sent, % of messaged
15%30%45% Apr 25Jun 25Aug 25Oct 25Dec 25Feb 26Apr 26Jun 26

It doesn't just perform. It behaves.

The operating standard your name is protected by: human pacing, office hours, and a veto-happy QA gate.

37 minmedian reply speed. Paced on purpose: an instant answer reads as a bot, and a next-day answer reads as you on vacation.
Office hours onlyMessages go out inside your working day, in your timezone. Prospects never hear from "you" at 3 AM.
99.6%+ uptimeA self-healing queue retries every hiccup and alarms us long before you would ever notice.
100% QA-gatedEvery outbound passes a second model whose only job is to veto. It earns its keep by saying no.
Agent activity · one working day

Researched Maya R., partner at an IP firm. Scored 81/100.

Drafted an opener in the client's voice. QA approved.

Reply detected. Reading the full thread, weighing intent.

Waited 17 minutes on purpose. Then answered the pricing question, no push.

Follow-up due on last Tuesday's thread. Sent.

Flagged one conversation for human judgment. Stepped aside.

End of working hours. Standing down until tomorrow, 8 AM.

How we count.

RepliedAt least one genuine inbound reply. Opens and views are not counted, ever.
Real conversationTwo or more replies from the prospect. A "thanks, not interested" is not a conversation.
Booking link sentThe client's own calendar link shared inside the thread. Our own links are excluded from prospect-side counts.
Pooled, not cherry-pickedEvery active client account, lifetime, including slow months and experiments that didn't work.
Hours returnedMessages sent × 3 minutes + leads researched × 5 minutes. Conservative on purpose.
Reply speedMedian minutes from a prospect's message to the twin's answer, measured from exact message timestamps. Deliberately paced, never instant.
ROIPipeline value clients attribute to twin-booked calls versus fees paid, averaged across accounts' first six weeks.
UptimeScheduled runs that executed on time, trailing 90 days.

Your numbers could
live here too.

Twenty minutes. Your industry, your voice, a live pipeline on screen.

Meet your twin →