AI AGENTS
RFP Competitor Positioning Brief
On request, researches the likely competing vendors for an RFP and produces a positioning brief in Notion that highlights how to differentiate each response section.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run with agency and RFP scope
- ActionRead RFP requirements and contextNotion
- ActionResearch likely competitorsExa
- ActionGather competitor public messagingBrave Search
- ActionSynthesize differentiation anglesOpenAI
- OutputCreate positioning brief in NotionNotion
What it does
Given an RFP and the buying agency, the agent researches probable competitors and their public positioning, then writes a strategy brief mapping each major requirement to a differentiation angle. The brief lands as a structured Notion page the team can pull from while drafting.
When to use it
Use it at proposal kickoff when you want a fast competitive read to shape win themes, rather than commissioning a manual market scan that takes days.
How it works
- 1A team member triggers the workflow manually with the agency name and RFP scope.
- 2The agent reads the RFP requirements and context from the source Notion page.
- 3Exa and Brave Search gather public information on likely competing vendors and their messaging.
- 4OpenAI synthesizes competitor strengths, weaknesses, and a per-requirement differentiation angle.
- 5The finished positioning brief is created as a new Notion page linked to the RFP workspace.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect ExaNeural search across the web.
- 3Connect Brave SearchWeb, news, image, video search.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
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.