The Revenue AI Report

Bardeen + Make.com personal workflow agents (L2)

Equip every IC with a personal automation stack: Bardeen for browser-side capture (scrape, save to Notion, route emails), Make.com or n8n for cross-tool flows (HubSpot \→ Slack \→ Sheets). Saves 30\,60 min/IC/day on the long tail of admin nobody owns.

WORKFLOW1Pick the team's automatio… duoBardeen2Run a 1-hour "automate yo…r top 3 chores" workshopManual3Showcase + libraryNotion4Watch for shadow-IT riskManual
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 2.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L2 Assisted. Running it above your level is how pilots stall.
Measures of successhours saved per IC per week; # of personal flows running; # of repeated tasks eliminatedPROVE IT WORKEDhours saved per IC per week# of personal flows running# of repeated tasks eliminated

The steps

  1. 01

    Pick the team's automation duo

    Tool: Bardeen

    Bardeen = browser actions (scrape this LinkedIn, save to CRM, draft email). Make/n8n = behind-the-scenes integrations between tools. Most teams need both; pick one of each, don't add Zapier on top unless you already have it. Owner: Ops. Time: 1 week eval. DoD: licenses provisioned for everyone who self-identifies as a power-user.

  2. 02

    Run a 1-hour "automate your top 3 chores" workshop

    Tool: Manual

    Each IC lists their 3 most-repeated weekly admin tasks (timesheet, weekly status update, lead-list cleanup, etc.). In the workshop, an ops person pairs to build the first flow in 20 minutes. People who build one flow build 5 more on their own; people who never build one never start. Owner: Ops. Pitfall: "give them docs and hope", the first flow is the bottleneck. Pair on it. DoD: every attendee leaves with 1 live automation.

  3. 03

    Showcase + library

    Tool: Notion

    Create a Notion gallery: "100 automations my team runs." Each entry: name, who built it, what it saves, how to clone. Update monthly. Most-used automations become candidates for centralized RevOps versions. Owner: Ops. DoD: gallery has >30 entries in 3 months.

  4. 04

    Watch for shadow-IT risk

    Tool: Manual

    Personal automations can leak data (customer PII into Sheets, credentials in unencrypted Make scenarios). Quarterly: ops reviews the top 20 most-used flows for data-handling risk. Kill the dangerous ones, replace with governed versions. Owner: Ops + Security. DoD: documented quarterly review with a decision log per high-risk flow.

Tools in this playbook

Building the team behind this workflow?

Post a job

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.