How AiSDR turns a discovery call into a proposal the same day
The exact workflow AiSDR's sales team runs after every discovery call: paste the Fathom link, review the AI draft, send a branded page before the prospect's next meeting.
In short: AiSDR's sales team sends a branded proposal in the same sitting as the discovery call. The routine has five steps: paste the Fathom link (or pick the call), link the HubSpot deal, review the AI draft section by section, fix pricing and add a Stripe payment link, publish and send the live page. It works because the prompt, FAQs and case studies are AiSDR's own, so the draft quotes facts instead of inventing them.
The problem with "I'll send a proposal by Friday"
Every sales team knows the shape of this failure: the discovery call goes well, the rep promises a proposal, and three days later a document arrives that reads like a template. By then the prospect has had two more meetings and half the urgency is gone.
AiSDR, an AI-powered outbound platform, had the same problem at a larger scale. Their reps run a high volume of discovery calls, and every one of them ended with the same manual chore: re-listen to the recording, copy notes into a deck, chase someone for pricing, export a PDF.
The workflow they run now
AiSDR's team standardized on a single post-call routine. It takes one sitting and happens while the call is still fresh.
1. Paste the call
The rep opens proposal.here, clicks New proposal, and either picks the call from the Fathom list or pastes the Fathom share link. proposal.here pulls the transcript through Fathom's MCP server; nothing is uploaded by hand.
2. Link the deal
The HubSpot deal is selected from a search box. The proposal inherits the company, the contact and the deal context, so the finished document lands in the right place in the pipeline.
3. Review the draft
Within a couple of minutes the AI has written every section the team configured: executive summary, where the prospect is today, what success looks like, the proposed solution, scope, timeline, investment, why AiSDR, and next steps. The rep's job is to read it like an editor, not write it like an author.
Two things make the draft usable instead of generic:
- The prompt is AiSDR's prompt. Their sales lead tuned it in the AI chat ("always quote the prospect's own words for pains", "never promise integrations we don't have") and reviews it quarterly.
- The FAQs and assets are AiSDR's. Pricing rules, security answers, integration lists and case studies live in the knowledge base, so the AI quotes facts instead of inventing them.
4. Fix pricing, add the payment link
If pricing came up on the call, it is already in the pricing table. If not, the rep fills it in. With Stripe connected, one click turns the table into a payment link, so a prospect can accept and pay from the same page.
5. Publish and send
The proposal is published to a page that uses AiSDR's colors, fonts and logo. The rep sends the link in the follow-up email, usually before the prospect's next internal meeting.
What changes when the proposal arrives the same day
The team noticed three things:
- Fewer "quick clarification" calls. The proposal restates the prospect's situation in their own words, which catches misunderstandings early.
- Better follow-ups. Engagement tracking shows who opened the proposal, which sections they read and how long they spent. Reps follow up on the section the prospect lingered on, not with a generic "any thoughts?".
- Forwardable documents. Because the page is branded and readable on a phone, champions forward it internally without reformatting.
Try the same routine
The routine is not specific to AiSDR. Any team with a call recorder and a CRM can run it: connect the tools once, tune the prompt once, keep the knowledge base current, and let reps spend their time on the parts of selling that are actually hard.