SALES

Weekly MAP buyer progress recap with next-step asks

Each week it pulls a deal's mutual action plan from Salesforce, summarizes what is done, on track, and overdue, and sends the buyer champion a recap email naming the specific…

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionRead MAP milestones and close date from SalesforceSalesforce
  • LogicBucket milestones and isolate buyer-owned next steps
  • ActionDraft progress recap with next-step asksOpenAI
  • OutputSend recap email to champion via GmailGmailGmail

What it does

Sends the buyer a clean weekly heartbeat on the shared plan. It rolls up every milestone into done, on-track, and overdue buckets, then writes a friendly recap that explicitly lists the items the buyer side owes and how each connects to hitting the agreed close date.

When to use it

Use it on later-stage deals where you want to maintain steady momentum and keep the buyer accountable without a manual status email every Friday. It is the proactive cousin of the slip detector: it nudges on cadence, not just on failure.

How it works

  1. 1A weekly schedule triggers the recap.
  2. 2It reads the opportunity's MAP milestones, owners, statuses, and close date from Salesforce.
  3. 3A logic step sorts milestones into completed, on track, and overdue, and isolates the buyer-owned next steps.
  4. 4An OpenAI step drafts a warm, specific recap email leading with progress and ending with the buyer's concrete asks.
  5. 5The recap is sent to the champion via Gmail, with the rep copied for visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SalesforceAccounts, opportunities, cases.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  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.