SALES

Send buyers a weekly mutual action plan health recap

Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.

CategorySales
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly recap schedule
  • ActionRead all MAP board cardsTrelloTrello
  • LogicBucket steps into done, on track, overdue
  • ActionEmail recap to buyer champion, CC AEGmailGmail
  • OutputPost summary to internal deal Slack channelSlack

What it does

Turns the shared Trello MAP into a weekly buyer-facing recap. It tallies steps that are done, on track, and overdue, then sends the buyer champion a clear email showing overall progress, what closed this week, and the steps due in the next seven days.

When to use it

Use it when you want buyers to stay accountable and feel the momentum without an awkward chase email written from scratch each Friday. Great for AEs running several active MAPs at once.

How it works

  1. 1A weekly schedule fires (for example, Friday afternoon).
  2. 2The flow reads every card on the MAP board with status, owner, and due date.
  3. 3A logic step buckets cards into done, on track, and overdue and counts each.
  4. 4It drafts a recap with a progress percentage, this week's wins, and next week's due steps.
  5. 5It emails the recap to the buyer champion and CCs the AE.
  6. 6It posts the same summary to the deal's internal Slack channel for the team.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect TrelloKanban boards for everything.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.