SALES
Weekly Multi-Thread Coverage Ledger with Trend Tracking
Weekly, it scores every high-value Salesforce deal on contact coverage, writes each score to a Postgres ledger to track week-over-week trends.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull high-value open opps and contact roles from SalesforceSalesforce
- LogicCompute coverage score per deal
- ActionWrite scores and timestamp to Postgres coverage ledgerPostgres
- LogicCompare to prior week and keep stuck or declining deals
- OutputPost deteriorating-coverage watchlist with deltas to SlackSlack
What it does
It builds a persistent coverage ledger so you can see not just which deals are single-threaded today but which ones are getting worse. Every week it computes a coverage score per deal, stores it, compares against last week, and surfaces deteriorating or stagnant deals.
When to use it
Use this when a one-time snapshot isn't enough and you want trend data for pipeline reviews. Good for RevOps teams who want defensible coverage metrics and managers who care about momentum, not just a static list.
How it works
- 1A weekly scheduled trigger fires.
- 2The flow pulls open Salesforce opportunities above the threshold with their contact roles.
- 3It computes a coverage score per deal from distinct engaged contacts and roles filled.
- 4It writes each deal's score and timestamp to a Postgres coverage ledger.
- 5A query compares the new score to the prior week's row.
- 6A filter keeps deals stuck at one contact or trending down.
- 7It posts the watchlist with deltas and suggested contacts to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
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.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.