One call. A follow-up ready for review.
Explore a fictional discovery call and its example output. This interactive preview uses sample copy; it does not call AI, connect accounts, or send email.
Discovery call · Northstar Studio
Fictional transcript · meeting-demo-1042
Maya, client: We spend Friday afternoons copying HubSpot updates into Slack. We want a weekly digest with the pipeline changes.
Jordan, rep: Let’s start with one sales team. I’ll send an outline by Friday and include the reporting fields for you to review.
Maya: Sounds good. I’ll confirm the fields before we plan a pilot.
Contact email [email protected] matches a transcript participant.
Your weekly pipeline digest pilot
Hi Maya,
Thanks for walking me through your Friday reporting process. We discussed a weekly digest of HubSpot pipeline changes in Slack, starting with one sales team.
I’ll send an outline and proposed reporting fields by Friday. Please review the fields so we can plan the pilot.
Best,
Jordan
Rep review in Gmail: Check the recipient, recap, deadline, and commitments against the transcript. Edit the draft and send it yourself.
The workflow creates a draft, not a sent email. A missing recipient does not invent an address.
03 · Google Sheets call-log entry
| Meeting ID | Contact Email | Summary | Next Step | Status | Draft ID |
|---|---|---|---|---|---|
| meeting-demo-1042 | [email protected] | Weekly HubSpot pipeline digest in Slack for one team. | Jordan sends outline and reporting fields by Friday; Maya confirms fields. | draft_ready | draft-demo-1042 (fictional) |
The log links the call to its draft. Replayed completed meeting IDs skip draft creation; unresolved draft_pending executions require checking Gmail before retrying.
Your setup progress
Sign up to save this workflow and your setup progress. Downloads and the sample are available now.