CRM

Weekly Buying-Committee Coverage Report to Notion

Each week, audits every open deal's inferred role graph for gaps such as a missing economic buyer or unengaged blocker.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionRead role graph and contacts from AttioAttio
  • LogicDetect committee coverage gaps
  • ActionRank deals by risk and draft recommendationsOpenAI
  • OutputPublish coverage report to NotionNotionNotion

What it does

This workflow runs a weekly audit across all open deals and evaluates the completeness of each buying committee that prior role-mapping has built in Attio. It flags structural gaps, such as a missing economic buyer, an identified blocker who has never been engaged, or a deal that is still single-threaded, then ranks deals by coverage risk and publishes a clean report to Notion for the pipeline review meeting.

When to use it

Use it ahead of weekly forecast or pipeline calls when leadership needs to see relationship coverage, not just stage and amount. It suits RevOps and sales leaders who want committee gaps surfaced before deals slip.

How it works

  1. 1A weekly schedule kicks off the audit.
  2. 2The workflow reads the role graph and contacts for every open deal from Attio.
  3. 3A logic step detects committee gaps like a missing buyer or unworked blocker.
  4. 4An OpenAI step ranks deals by coverage risk and drafts plain-language recommendations.
  5. 5A formatted coverage report is published to a Notion database for pipeline review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AttioReal-time CRM with structured data + powerful views.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  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.