The agency
Books meetings in their system, on their story. You get a calendar, not the reasoning.
New signal
Arborio is hiring a Head of Sales
Matches ICP · 2h ago
One record per account — signals, drafts, sends, replies, meetings, and deals. Canvass drafts the next move from that memory. You approve every send.
Free to explore · Nothing sends without your review
Works with the stack you already run
"Hi Dana — saw Northbeam is hiring three AEs…"
"Congrats on the Series B, Marcus — teams at this stage…"
"Saw Fleetquill just expanded into the EU…"
Meeting booked
Dana R. · Tue 10:30
From the hiring trigger · on the record
The problem
The context that makes outreach work — the trigger, the history, the last "no" — falls out between the tools, and the CRM only hears about it after the fact.
Books meetings in their system, on their story. You get a calendar, not the reasoning.
Fires steps from a list, not a trigger. Last quarter's "no" lives in a spreadsheet.
Forgets the account when you close it. Personalization starts over every time.
Stores fields, not reasons. Knows what your reps typed last quarter — not who moved this week.
One living record per account — signals, drafts, sends, replies, meetings, and deals — and a loop that turns a buying signal into the next email. You work a shortlist instead of a blank page.
What it does
Five jobs, one workspace, no tab sprawl.
ICP — draft v2
Paste your homepage. Canvass reads it and drafts the ICP — the companies, the buyers, the changes that matter. You edit it. Sales, marketing, and ops work from the same picture.
Minutes, not a workshopHiring, funding, and reply signals land on one account record. Weak cases are skipped. The few that matter get a draft.
Hi Dana — saw Northbeam is hiring three AEs. Teams at that stage usually feel list decay first…
Every draft names its evidence for "why now." No merge-field personalization, no blank prompt.
Drafts wait in a review queue. Approved mail enters your Instantly campaign and Instantly sends on its schedule. Replies come back onto the record.
The account record is the CRM. Signals, touches, replies, meetings, and deals sit on one timeline the whole team can see — no re-entry, no sync jobs, no second system of truth.
Process
Three steps from a URL to a live, reviewed campaign — and a CRM that fills itself.
Paste your website and see a drafted ICP, then a shortlist of who moved. Self-serve and reversible.
Connect Apollo and Instantly with your own keys. Review the first drafts from live accounts.
Approved mail enters Instantly. Every reply, meeting, and deal lands back on the account record — the CRM fills itself.
Review queue · this week
Approved mail → Instantly → replies, meetings, and deals back on the record.
How we compare
The honest differences: who does the work, who remembers the account, and who approves the send.
| Capability | Agency | Sequencer + data | AI SDR bot | Old CRM | Canvass |
|---|---|---|---|---|---|
| Who does the work | Their callers | You, inside their UI | The bot, unsupervised | Your reps, after the fact | You, from a drafted queue |
| Knows why now | Their callers decide | Cadences start from a list | Hidden in a prompt | Fields, not triggers | Every draft names the trigger |
| Remembers the account | In their CRM, not yours | In a spreadsheet | Until the session ends | Whatever reps type in | One living record per account |
| Acts on the account | Calls, sometimes | Sends steps | Sends, blindly | No — it only stores | Drafts, with your approval |
| You can inspect why | No | Partly | No | No | Signal, score, draft, outcome |
Email is the shipping delivery channel today. Social, ad, and landing-page content can be authored, but full channel delivery and learning adapters are future work.
Control
Every pass records the signal, the judgment, the draft, the meeting, and the deal. You can see why an account made the shortlist — and what happened after.
Suppression, caps, proof, and scoped grants sit on the campaign, not in a prompt.
Signals, verdicts, drafts, sends, and outcomes form an inspectable trail. You can answer who did what, and why.
Long-running work can pause mid-pass and resume without losing the account or the draft.
FAQ
Yes, minus the usual parts. It keeps the account record of a CRM, watches and drafts like an outbound tool, and skips the unsupervised sending of an AI SDR bot. One memory per account, human-approved sends.
No. Drafts sit in a review queue until a person approves them. Approved mail enters your Instantly campaign, and Instantly sends on its schedule. Suppression lists and caps sit on the campaign, not in a prompt.
Canvass is the account record for the go-to-market motion: signals, touches, drafts, replies, meetings, and deals on one timeline the whole team can see. Lightfield meetings come back onto the same record. You stop copying context between a CRM and a sequencer.
An agency runs outbound in their systems and hands you meetings. Canvass runs in your workspace: the account memory, the drafts, and the audit trail belong to you, and you approve every send. It is self-serve software — no retainer, no implementation engagement.
A website. Canvass reads your public homepage and drafts the ICP for you to edit. Connect Apollo and Instantly with your own keys when you are ready to send.
Organization data and sealed vendor credentials are tenant-scoped. The active deployment uses Lakebase for operational memory and keeps model and storage providers behind explicit boundaries.
Email is the shipping delivery channel. The artifact model can author social, ad, and landing-page content, but full channel sensing, publication, outcome, and learning adapters are future work.
Open the workspace, inspect the accounts that moved, and watch outcomes land on the record.