Zapier Automation: Weekly POC Status Report and Blocker Escalation

What This Builds

Writing a weekly POC status update for the account executive and your manager means opening the tracker, rereading every active trial, and turning rows of notes into sentences someone can skim in ten seconds. This automation pulls every active POC from your tracker sheet once a week, drafts that narrative for you, and flags in the subject line how many trials have been blocked longer than a set number of days, so an escalation is visible before anyone has to open the email.

Prerequisites

• Professional plan ($29.99/month), the same plan used for the RFP intake automation above if you already built it
• A Google Sheets POC tracker (this guide sets up the columns it needs if you don't have one)
• Gmail for sending the report
• Total ongoing cost: $29.99/month. AI by Zapier steps can use more than one task per successful run, so watch your monthly task usage if you're close to your plan's limit

The Concept

Think of this as an assistant who reads your POC tracker every Monday morning and hands you a short written summary instead of a spreadsheet. The trick is that the assistant only writes well if the notes it's reading are already organized, so most of the setup here is making sure each row in your tracker already reads like a sentence before the AI step ever sees it.

Build It Step by Step

Part 1: Prepare Your POC Tracker Sheet

Set up (or extend) a Google Sheet with these columns: Account (POC name), Status (Active, Blocked, Closed-Won, Closed-Lost), Blocked Since (date, left blank unless Status is Blocked), Owner, and Notes (a short plain-language note on what's happening).

Add three helper columns that do their own math right in the sheet, so the Zap doesn't have to (adjust column letters to match your sheet: A for Account, B for Status, C for Blocked Since, E for Owner, F for Notes):

Days Blocked (column D, numeric): =IF(B2="Blocked", TODAY()-C2, "")

Open (column G, yes or no, this is what the Zap filters on): =IF(OR(B2="Active", B2="Blocked"), "yes", "no")

Status Line (column H, text, this is what the Zap actually reads): =IF(B2="Blocked", A2 & ": blocked " & D2 & " days (" & E2 & ") - " & F2, A2 & ": " & B2 & " - " & F2)

Paste all three formulas down every row. Now every row already reads as a finished sentence like "Acme Corp: blocked 8 days (Jane Lee) - waiting on customer's API credential," which is what makes the AI step's job small and reliable instead of guessing at meaning from raw fields.

Then add a second tab called Summary with the word blockers in cell A1 and this formula in B1, which counts the trials blocked for five days or more (change the 5 to whatever escalation threshold you want): =COUNTIFS(Tracker!B:B, "Blocked", Tracker!D:D, ">=5") (assuming the first tab is named Tracker). The count lives in the sheet, not in the Zap, so the Zap can read it in one step even when the answer is zero.

Part 2: Build the Zap

Trigger: Schedule by Zapier, Every Week. Set it for Monday morning.

Step 2, pull active and blocked POCs: Add a Google Sheets Lookup Spreadsheet Rows (Advanced) step on the Tracker tab, with one condition: the Open column equals "yes." Set it to return the Status Line column for every match. Because this filters by status and not by how recently something changed, a POC that's been blocked for three weeks keeps showing up every single Monday until its status actually changes, the same overdue-visibility approach as the RFP digest above. One Zapier rule to know: a lookup step that finds nothing halts the Zap right there (Zap History shows the run as Halted, not as an error, and a halted run uses no tasks). So in a week with zero open POCs, no report goes out at all. That is the intended behavior, and Part 3 shows you what it looks like.

Step 3, read the blocker count: Add a second Google Sheets Lookup Spreadsheet Rows (Advanced) step, this time on the Summary tab, with one condition: column A equals "blockers." It returns the B1 value, which is the count of trials blocked past your threshold. Because that row always exists, this step always finds a match, even when the count is 0, so it never halts the report on a good week.

Step 4, join the status lines: Add a Formatter by Zapier step, Utilities category, Line-item to Text, joining Step 2's Status Line results into one text block, one line per POC.

Step 5, draft the narrative: Add an AI by Zapier Analyze and Return Data step. This guide uses AI by Zapier's own built-in model, not the Bring-Your-Own-Key option. If you choose the Bring-Your-Own-Key Anthropic option inside AI by Zapier instead, that needs its own Anthropic API key with its own billing, separate from any Claude.ai subscription you already pay for. Use a prompt like:

You're helping a sales engineer summarize their active POC pipeline for their account executive and manager. Turn the following status lines into a short narrative, 3 to 5 sentences, in plain language. Name any blocked account specifically and how long it's been blocked.

Status lines:
[Step 4 output]

Step 6, send the report: Add a Gmail Send Email action to the account executive and your manager. Build the subject line from Step 3's count value, something like "Weekly POC Status, [Step 3 count] blocker(s) over 5 days." On a good week the subject reads "0 blocker(s) over 5 days," which is a real, useful subject line rather than something that looks broken. In the body, use Step 5's narrative, followed by a link to the full tracker sheet for anyone who wants the raw detail.

Turn the Zap on.

Part 3: Test and Refine

Add a test row to your tracker with Status "Blocked" and a Blocked Since date eight days in the past, then run the Zap manually from Zapier. Confirm the test account appears in the narrative, that the subject line's count includes it, and that the email actually lands in both recipients' inboxes. Then change that row's status to "Closed-Won" and run the Zap again. It should disappear from both the narrative and the count. Finally, if you can, set every row to a Closed status and run once more: Zap History should show that run as Halted at Step 2 with no email sent. That is what an empty pipeline looks like, and it is worth seeing once so you don't mistake it for a failure later.

Real Example: A Blocked Integration POC

Setup: The tracker has three active POCs. One, "Acme Logistics API Integration," has been Status "Blocked" for eight days waiting on a customer-side API credential. The other two are running on schedule.

Trigger: Monday morning, the Schedule step fires.

Output email:

Nothing is sent to the customer. This report goes only to the account executive and the SE manager; it is an internal status update, not customer communication.

Time saved: what used to be fifteen to twenty minutes of rereading tracker notes and writing a summary by hand happens automatically before the workweek starts.

What to Do When It Breaks

• The narrative reads generically or skips naming a blocked account → tighten Step 5's prompt with an explicit instruction like "always name every blocked account by name and how many days it's been blocked."
• The subject line always shows 0 blockers even when the sheet has an old blocker → check the Summary tab's COUNTIFS formula: the tab name must match your tracker tab exactly, the Status text must match ("Blocked" is not "blocked"), and the Days Blocked column must hold numbers, not text.
• Task usage climbs faster than expected → the AI by Zapier step can use more than one task per successful run. Check your task usage under your Zapier account if you're near your plan's monthly limit.
• Silent failure: Monday comes and no email arrives → open Zap History. A run marked Halted at Step 2 means the sheet had no rows with Open set to "yes," which is fine if your pipeline really is empty and a sign of a broken Open formula if it isn't. A run marked Error means a step failed (an expired Google connection is the usual cause). No run at all means the Zap is turned off, which Zapier does on its own after repeated errors and tells you by email, so make sure that email isn't filtered into a folder nobody checks.

Variations

• Simpler version: Skip Step 5 and send Step 4's raw joined status lines directly in the email body. No drafted narrative, but no AI by Zapier task usage either.
• Extended version: Add a second Gmail step sending a longer, unabridged version of the tracker to just the SE manager, while the account executive gets the shorter narrative.

What to Do Next

• This week: Set up the two helper columns on your real tracker sheet and confirm the formulas read correctly for a few rows.
• This month: Watch the escalation threshold for a few weeks and adjust it if five days is catching too much or too little.
• Advanced: Cross-reference a POC's success criteria from the discovery-to-POC prompt chain against its weekly status, so the report can eventually note when a POC is falling behind its own agreed criteria, not just its due date.

Advanced guide for sales engineer professionals. A POC tracker often contains customer environment or architecture detail. Keep the Notes column written in general terms (the type of issue, not internal IP addresses, drawing numbers, or exact system names) since that text flows through Zapier's Zap History and through whichever AI model processes Step 5, and check with your security team or the customer's NDA terms before including anything more specific.