| A new trial signup lands in the CRM or a signup notification reaches the shared inbox. |
Matches the signup to its company record, notes plan, seat count and any questions already asked in Intercom or email, and adds the account to the morning brief with the trial end date and the last human touch. |
The founder or head of customer success decides which trials get a personal note and edits the draft before sending it from their own Gmail. |
Every open trial has a named owner and a next step, and silent ones are listed as silent instead of disappearing. |
| A demo call ends and the recording or meeting notes are saved. |
Pulls the stated objections, the promised items and the agreed next date out of the notes, drafts the recap email, and proposes the matching task and deal update for HubSpot. |
The person who ran the demo checks the recap against what was actually said, removes anything that reads like a roadmap commitment, and sends it. |
The prospect gets an accurate recap the same day, and the deal record carries the same promises as the email. |
| An account opens a repeat ticket on the same issue, or a ticket stays unanswered past the window the team has set. |
Groups the related conversations, links the Linear issue if one exists, checks the renewal date from the billing export, and flags the account as at risk in the brief with the evidence beside it. |
The head of customer success chooses whether to call, write or wait, and an engineer decides the fix and its release timing. |
At-risk accounts are visible with reasons attached before the renewal conversation, not after the cancellation. |
| A failed payment or downgrade appears in the Stripe export. |
Lists the affected accounts in a Google Sheet with plan, last contact and open tickets, and drafts a plain, non-pushy note for each one. |
The founder approves each message and personally makes any plan change, refund or credit inside the billing system. |
Billing exceptions are worked from one list, and nothing in the customer's account changes without a person doing it. |
| A customer asks when a feature or fix will ship, by email or in the support desk. |
Finds the related Linear issue and its current status, drafts a reply that states what is known today, and marks the question as needing an engineering answer where the status is unclear. |
An engineer confirms what can be said about timing; the support lead sends the reply. |
Customers get a straight answer that matches the issue tracker, with no dates invented on the team's behalf. |
| The weekly review meeting appears on Google Calendar. |
Assembles a one-page summary in Slack or email: trials opened and expired, demos awaiting follow-up, at-risk accounts, unanswered tickets and items that have waited longest for an approval. |
The founder reads it, reassigns stuck items and decides what the team drops. |
The meeting begins from a shared list of open handoffs instead of each person's recollection. |