Prospect Desk
A sales system that researches, drafts, and follows up, with a person approving what goes out.
A private product, shown with sample data.
What was missing
A normal CRM records what a seller already did. The harder system decides what should happen next across incomplete contact data, verification, qualification, drafts, send windows, follow-ups, replies, bounces, DNC status, and operator overrides without turning automation into uncontrolled outreach.
What we built
A sales operating system that researches and qualifies accounts, prepares outreach, manages follow-up sequences, reads reply state, and can move eligible work autonomously while keeping hard safety gates and an audit trail.
- Account and contact research, provenance, verification, duplicate review, qualification queues, and readiness blockers
- Operator APIs for list motion, imports, review queues, events, reply reads, and first-touch or follow-up scheduling
- Default-off unattended motion that can deliver only eligible reviewed drafts and automatically continue or stop sequences
- Reply intelligence, bounce/DNC/Not-a-fit stops, audited force controls, scheduled-email review, and deterministic hard blocks
How it works
Import or capture leads, then research the account and preserve source evidence.
Actual UI · sample dataActual account UI · locally intercepted sample research; review before outreach Qualify the contact: verify the email, identify the decision maker, and check readiness blockers.
Actual UI · sample dataQualification and message preparation · safe sample data Prepare personalized messages and follow-up steps in the review queue.
Actual UI · sample dataActual frontend, renamed for privacy · invented contacts and mock responses An operator approves eligible drafts and explicitly enables supervised autonomous motion.
Stop remaining touches on replies, bounces, do-not-contact flags, or other rule triggers.
Review the sequence history and audit events to see what was sent, stopped, or overridden.
Decisions that make it work
The engineering choices behind Prospect Desk, in plain words.
Automation that knows when to stop
A reply, a bounce, a do-not-contact flag, or an identity problem stops a sequence immediately.
Confidence is not permission
Research confidence, a verified email, and safe copy are separate checks. All of them have to pass before anything can send.
No double sends
Retries and parallel workers cannot deliver the same email twice or restart a sequence that already stopped.
Overrides leave a trail
When an operator overrides a rule, the override is narrow, explicit, and permanently logged.
Where AI fits
Research, qualification support, call briefs, reply intelligence, and draft preparation can accelerate the sales loop while deterministic policies decide what is eligible for automation.
What a person decides
Autonomous motion is an explicit operating mode, not the absence of control. Administrators set the mode and operators review exceptions, overrides, account facts, and anything the safety gates refuse.
What it makes possible
Research, qualification, drafts, and follow-ups move forward on their own when they are eligible, and stop the moment someone replies, bounces, or asks not to be contacted. Every override is narrow and logged.