| Follow-up | Company | Contact | Notes | Status |
|---|---|---|---|---|
| Sep 8 | Cedarline Logistics | Dana Whitaker | Runs inbound, backlog at receiving | High intent |
| Aug 6 | Brookfield Transport | Ray Ames | Wants rates before booking | High intent |
| Aug 12 | Summit Freight Partners | Jaya Patel | Rescheduled twice, asked to | Demo |
| Aug 21 | Lakeshore Carriers | Marcus Reyes | Dispatch lead is the real | High intent |
| Aug 24 | Rivermont 3PL | Casey Roberts | Demo booked with the dock | Demo |
| Aug 31 | Calder Cold Chain | Christa Nolan | New ops director, worth | High intent |
| Sep 2 | Fairview Drayage | Renee Duquette | Sent the overview, asked to | Demo |
| Sep 3 | Portside Freight | Alan Voss | Asked for a reference before | Demo |
| Sep 4 | Granite State Logistics | Nina Bardot | Ops lead joins the next call | High intent |
| Sep 5 | Harborview Transit | Owen Clarke | Budget confirmed for Q4 | High intent |
Runs inbound, where the backlog starts. Wants it resolved before peak season and asked to include their transportation manager.
Before: the spreadsheet.
Most reps run their pipeline out of a sheet like this one. After every call there are five things to do by hand: log the contact, write down what was said, set the follow-up date, draft the email, and move the deal.
| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
| 1 | FOLLOW UPS - Q3 (use this one) | ||||||
| 2 | |||||||
| 3 | name | company | status | f/u | NOTES | last touch | owner |
| 4 | Dana Whitaker | Cedarline Logistics | high | next tues | peak starts oct | 8/1 | me |
| 5 | R. Ames | Brookfield Transport | ? | 6/12 | called back?? | me | |
| 6 | j patel | Summit Freight Partners | demo | 06/19/2025 | resched 2x | 7/30 | ask jenn |
| 7 | K. Oyelaran | Northbay Distributn | high | 8/3 | ##### | ||
| 8 | marcus (?) | Lakeshore | med | left vm, no last name, try the dispatch line again thurs | |||
| 9 | |||||||
| 10 | Lisa S | Rivermont | HIGH | aug | dupe of row 6? | 7/12 | |
| 11 | ashbury warehousing | ?? | who took this one | ||||
| 12 | #N/A | ||||||
| 13 | Christa | Calder Cold Chain | high intent | 8/31 | new ops director | 8/28 | me |
| 14 | T. Burch | Portside Freight | no show | 8/6 | 2nd one | ||
| 15 | TOTAL | 20 | dont delete this tab |
Drop the transcript in and the record writes itself.
Paste the call. BDR Desk reads it and fills in the name, company, phone, email, status, and next date, then writes a two-line summary. Anything it hears that has no field is kept with the record, not dropped.
The follow-up is written from what was actually said.
The draft quotes the call: the pain, the timing, the system they run, and the person they want on the next call. It stays a draft until the rep reads it and sends it.
Every contact comes with the people around them.
For each new contact, BDR Desk builds the decision hierarchy at that company: the peers who will be consulted, and the executives who sign. Names and titles come from Apollo, the sales intelligence platform the team already runs on.
“…include our transportation manager before anything moves.”
A calendar that works for the rep.
Follow-ups and demos land on the calendar with the notes from the call attached, so the next conversation starts where the last one ended. Click a demo to read its notes.
Runs inbound, where the backlog starts. Wants it resolved before peak season.
How it's built
One workflow, six systems, and a single body of sales context that all of them read.
| Call events | Nooks, the team's dialer, sends the transcript when a call ends. |
|---|---|
| Parsing and writing | Claude reads the transcript, fills the record, drafts the email, and maps the organisation. |
| The pipeline | Supabase holds contacts, notes, follow-ups, and the transcripts behind them. |
| CRM | HubSpot receives the record and stays matched to the account. |
| People data | Apollo supplies names, titles, and addresses for the decision hierarchy. |
| Interface | React. A queue, a calendar, and a drawer. No rollups and no team view, because nobody was going to read them. |