⬡ Overview
📋 Brief
⚡ Trigger
↻ Steps
🔧 Tools
▶ Simulate
📊 Metric
🔄 Full Loop
◇ Check
★ Results
0 / 6
Hands-On Lab · Module 11 · BAA 11.0

Process
Automation Plan

You'll design a complete automation for a daily sales lead qualification workflow — from the trigger that starts it, to the 7 agent steps that run it, to the metric that proves it works. Then you'll run the full agentic loop live.

The Agentic Pipeline You'll Design
⚡
Trigger
→
🔍
Dedup
→
✉️
Verify
→
🏢
Enrich
→
📊
Score
→
🔀
Route
→
📝
Draft
→
📋
Log
Lab Roadmap
—
Read the Brief — understand the manual problem you're replacing
Apex Revenue Co. · 40–120 leads/day · 2-hour manual bottleneck
1
Design the Trigger
Choose the right trigger architecture and configure dedup logic
2
Assemble the 7-Step Pipeline
Place steps in correct order — some options are decoys
3
Map the Tool Stack
Assign the right tool to each of the 7 steps
4
Simulate 5 Live Leads
Run the agent — watch it qualify, disqualify, and flag in real time
5
Select the Efficiency Metric
Choose the one KPI that proves this automation is generating business value
6
Observe the Full Agent Loop
Watch Perceive → Reason → Act → Observe animate step by step on a new lead
—
Knowledge Check · 7 questions · 70% to pass
The Problem to Solve

Apex Revenue Co. — The Manual Nightmare

Before you design the automation, understand exactly what you're replacing — and where the 2 hours per day disappears.

Current State — Apex Revenue Co.

Apex is a B2B SaaS company with a 6-person sales team. Every morning, 40–120 new leads arrive from three sources: their website contact form, LinkedIn lead-gen ads, and a data provider (ZoomInfo). Each lead requires the same 7-step manual checklist before a rep can touch it:

① Check CRM for duplicates — to prevent embarrassing double-outreach
② Verify the email — bounced mail burns domain reputation with ISPs
③ Enrich company data — employee count, funding stage, industry from a third-party API
④ Score against ICP — job title, company size, industry, funding stage, intent signals
⑤ Route to the right rep — by territory (region) and vertical (industry)
⑥ Draft personalized outreach — reference recent company news and job posting signals
⑦ Log everything to Salesforce — score, routing decision, draft email attached

The SDR team lead does steps ①–④ every morning. It takes 90–120 minutes. Research shows leads older than 4 hours have a 5× lower response rate. By the time they're processed, most leads are cold.

😤 Current State
⏱ Time to outreach: 2–4 hours
📉 Response rate after 4h: 5× lower
💸 SDR admin time: 90–120 min/day
🔴 Duplicate outreach: ~3 incidents/week
📊 Throughput cap: one SDR's bandwidth
🎯 Agent Target State
⏱ Time to outreach: < 8 minutes
📈 Leads contacted while warm: 100%
💚 SDR admin time: <10 min/day (review only)
🟢 Duplicate outreach: 0 (automated CRM check)
📊 Throughput: unlimited — no bottleneck
⚠️ Human-in-the-loop boundary: The agent qualifies, scores, routes, and drafts the outreach email — but a human rep reviews and sends the final email. The agent never directly contacts a lead. Your automation plan must respect this boundary.
Section 01 · Design Activity

Design the Trigger

The trigger is the event that fires the agent. It determines lead freshness, duplicate risk, and whether the automation actually solves the response-time problem. Choose the right architecture — then answer two configuration questions.

💡 Trigger principle: Match the cadence of the trigger to the urgency of the process. A workflow built around a 4-hour response-time problem cannot run on a nightly batch.
Step 1 — Pick the Trigger Architecture
Section 02 · Build Activity

Assemble the Agent Steps

Below are 10 candidate steps. Your pipeline needs exactly 7 — in the right order. Click a step from the library, then click a numbered slot to place it. Three options are decoys that violate the human-in-the-loop boundary or don't belong in this workflow.

Design constraint: The agent drafts the outreach email but never sends it. Any step where the agent directly contacts a lead is out of scope.
Step Library — click to select, then click a slot below
Your 7-Step Pipeline
Section 03 · Design Activity

Tool Stack Assignment

Each of the 7 pipeline steps needs a specific tool. Match the right tool to each step. Two tools appear more than once — that's intentional. Two listed tools are decoys that don't belong in any step.

Section 04 · Live Simulation

Run the Agent

Five leads just arrived. Click Run All to process each one through your 7-step pipeline. Watch the step-by-step reasoning trace, then see the final verdict for each lead.

💡 Apex ICP: Company 50–500 employees · Series A–C · Title VP+/Director+ in Sales/Marketing/RevOps/Growth · Industry: SaaS/FinTech/HealthTech · Email deliverable · Not already in CRM
Section 05 · Design Activity

The Efficiency Metric

Your agent is running. Now you need to prove it's working. Choose the one key efficiency metric you'd track — the one that maps directly to the business outcome this automation was built to deliver.

🔮 The trap: Most people choose a volume metric (leads processed/day). Volume proves the agent is alive — not that it's valuable. The right metric measures the outcome the business actually cares about.
Section 06 · Capstone

The Full Agent Loop

Watch the complete Perceive → Reason → Act → Observe cycle run on one final lead. This is the conceptual architecture behind every autonomous agent — not a linear script, but a loop that evaluates and adapts.

💡 Loop vs. script: A script runs once and stops. An agent loops — it observes the result of its actions and decides whether to act again. The OBSERVE phase is where agent intelligence lives.
Knowledge Check

7 Questions

Drawn from every section of this lab. 70% to pass.

Question 1 of 7Score: 0 / 0
Lab Debrief

Automation Plan Complete