Skip to main content

Are We Dying?

How the business is doing, and where you're dropping the ball. One email a day, from whatever you're paid through, your own product, and the team's mail, calendar and code.

What it reads, what it makes, where it lands

One morning's email

What lands in the inbox, with made-up names and numbers.

From GBrain To the team Subject Are we dying? Tuesday, October 27

What everyone’s working on

Sam is finishing the phone app.

  • Seven test builds since Monday.
  • The sign-in screen works without a password.
  • Fixed the sync bug Marcus reported.

Priya is chasing the people who went quiet.

  • Emailed 6 paying customers to check in.
  • Recapped the Northwind call and sent Hana the setup guide.
  • Wrote the pricing page for the Team plan.

💵 Money

$9.2K MRR as of today
+14% MRR growth, month over month
4 new customers in the last 7 days · Team 3 · Solo 1
8% of Team buyers cancel within 30 days · Solo 0%
$2.1K software spend in the last 4 weeks

🥊 Where we’re dropping the ball

  • The call: Priya answers Marcus’s setup question today; he cancels 10/30.
  • $597/mo set to cancel; Lena ends Friday.
  • Devon wrote again 10/24; no reply since 10/16 (day 3). (Priya)
  • Sam: 14 code changes, zero customer emails since Monday (day 2).
  • What does the new plan earn before 11/15?

🆕 New customers

  • Hana Okafor (hana@northwind.example), Team.
  • Tomás Reyes (tomas@brightline.example), Solo.

⭐ Power users to talk to

  • Marcus Bell, 31 messages, 5 active days. Has it read his support inbox every morning and draft the replies.

📬 Follow-ups

Devon is waiting on a reply, 3 days. (Priya)
Lena cancels 10/30.

🚩 Flags

  • Tomás’s $49 payment bounced twice; his plan ends Friday unless it goes through.
A sample. The names and numbers are made up; yours come from your own accounts.

One email a day that says whether you’re still alive

Every morning, GBrain reads the money, the customers and the team’s work, and sends one email: what everyone worked on at the top, then the five money lines, the single call to make today, who signed up, who to call, and who is waiting on you. Names and numbers, no cheerleading.

Reads from

Stripe
Mercury
Brex
GitHub
Gmail
Google Calendar
Circleback
and more

Sends to

Gmail
Slack
and more

What it does

  • Reads whatever you’re paid through, read only: Stripe, Square or PayPal for subscriptions; Mercury, Brex or Ramp for the bank. Each source fills the money lines it can, and the email says which lines it could not.
  • Reads your own product when you add its server under Tools, so new signups and the power users worth a call come from your own data.
  • Reads each teammate’s connected mail, calendar, code and call notes, and groups the week’s effort by theme.
  • Asks the same hard question every day, “where is this team failing to move revenue?”, and answers with one call, three to five failures, and a question or two, each with the names and the number.
  • Keeps a customers file: who is owed a reply, who is set to cancel, who went quiet.

The reveal

The first email lands with the key numbers in the subject line and the team’s week at the top. The second one starts counting: a customer still unanswered is “day 2”, and stays until it’s done. Nobody on the team has to ask how the month is going, or pretend not to know who they’ve been avoiding.

Configuration

  • Your money: Stripe, Square, PayPal, or straight to the bank. Any mix. Accounts to leave out of the numbers (a founder’s own, a test account).
  • Your product: the server you added under Tools, and the two calls that list new signups and rank active users.
  • Your team: each teammate connects their own accounts to be included; the email covers whoever has, and grows as more do.
  • Who gets it: the whole team by default, from one connected mailbox; a Slack channel too, when one is connected under Messaging.
  • When it lands: weekday mornings at 6:30 in your timezone, or every day.

Triggers

Runs on demand, or every morning on a verified schedule, once at least one money source is connected and sending is approved.

Put Are We Dying? to work

How the business is doing, and where you're dropping the ball. One email a day, from whatever you're paid through, your own product, and the team's mail, calendar and code.