← Back to library

Review a teammate's Clay build by questioning a coding agent

Petra Hajal, who reviews her team's GTM engineering builds, wrote on LinkedIn that checking a Clay workbook used to take her a day or two. Now Claude Code reads the build through Clay's CLI and she questions it about bugs, edge cases and test examples, after first asking the builder to explain their reasoning. We make it repeatable.

  • OutcomeBefore you review an automation a teammate built in Clay, ask them to explain the decisions and assumptions behind it, then point a coding agent at the build through Clay's command-line tool and question it about logic, edge cases and sample records, so you can give specific feedback in minutes instead of clicking through every column yourself.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditPetra Hajal
View original
Works with
Claude CodeCustom agent

Published Nov 9, 2026Updated Nov 9, 2026AI dry run on sample input: passed Nov 9, 2026Source verified Nov 9, 2026

When should you use it?

  • You lead a GTM, RevOps or growth team and review enrichment or outbound builds before they go live
  • Reviews pile up because each workbook has dozens of columns, formulas and waterfall steps to trace
  • You want feedback that coaches the builder, not just a pass or fail

Not for: Teams without access to Clay's CLI, or builds that live only in screenshots and exported CSVs; Small one-table builds you can read in a few minutes yourself; Final sign-off on anything that sends email or spends credits, which still needs a human check of a live sample

What do you need, and what do you get?

You need

  • Claude Code or another terminal coding agent with Clay's CLI installed and authorized
  • The workbook or table to review and a short note on what it is supposed to deliver
  • The builder's own explanation of the choices and assumptions they made
  • Two or three real-looking test records, including an awkward one

You get

  • A plain description of what the build does, step by step
  • A list of assumptions the build relies on, marked confirmed or unconfirmed
  • Edge cases and failure points found by walking test records through it
  • Feedback notes you can share with the builder

How does it work, step by step?

  1. Ask the builder firstHave them explain how they approached the problem and which decisions they made. Many problems show up here, before you open anything.
  2. Let the agent read the buildPoint the coding agent at the workbook through Clay's CLI and ask it to describe each step and the data each column depends on.
  3. List the assumptionsAsk the agent which inputs or rules the build takes for granted, then check each one against what the stakeholder actually asked for.
  4. Walk test records throughGive it a few sample companies or contacts, including a messy one, and ask what each step would produce and where it would break.
  5. Write the feedbackTurn the findings into specific notes for the builder, and keep the strongest questions as a checklist for future reviews.

The prompt

Our own prompt, inspired by Petra Hajal and written to work in Claude Code and Custom agent. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
Use the Clay CLI with read-only access to open {workbook_or_table}. Do not edit or run anything.
The builder says the goal is: {goal}. Their notes on decisions and assumptions: {builder_notes}.
1. Describe each step in order and which columns or inputs it depends on.
2. List every assumption the build makes, and mark whether the builder's notes confirm it.
3. Walk these test records through the build and say what each step would output and where it could fail: {test_records}.
4. End with up to five specific, kind feedback points I can share with the builder.

Inspired by Petra Hajal: LinkedIn post: reviewing a Clay build with a coding agent. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • The agent explains the build as written. It cannot know a requirement nobody wrote down, which is why the builder conversation comes first.
  • Simulated records are not live runs. Before launch, still run a small real batch and look at the output yourself.
  • Read-only access is enough for review. Do not give the agent permission to edit or run tables that spend credits during the review.
  • A clean agent summary can feel like approval. Treat it as a map for your questions, not as sign-off.

Our take

Code review has had tooling for decades, but reviewing a no-code build usually means clicking through it cell by cell, which is why it gets skipped or rushed. Petra Hajal's approach gives the reviewer the same advantage a developer has: something that can read the whole build at once and answer questions about it. The part we think matters most is the one she says has not changed. Asking the builder how they reasoned about the problem catches the most expensive error, an assumption nobody checked with the stakeholder, before any tool is involved. The agent then does what it is good at, tracing dependencies and walking sample records through each step. We would keep the agent on read-only access during review and still run a small live batch before launch, because a simulated record cannot reveal a provider returning odd data. In our dry run with a fictional enrichment table for a software reseller, the agent traced the steps, flagged an unconfirmed assumption about company size and found a record that fell through an empty fallback.

Where the time goes back: The reviewer stops tracing columns by hand and spends the time on questions, so a review that took a day becomes a short conversation plus a list of specific fixes.

FAQ

Does this only work with Clay?
The post is about Clay builds read through Clay's CLI. The same review pattern works for any automation tool that can export or expose its workflow definition to a coding agent.
Which agent did she use?
Claude Code. Any terminal coding agent that can run a CLI and answer questions about what it reads would fit the same role.
How much time does it save?
She reports reviews dropping from one or two days to roughly ten minutes, and says coaching her team became easier as a side effect.

Source and credit

Inspired by Petra Hajal. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
LinkedIn post: reviewing a Clay build with a coding agent
Creator
Petra Hajal
Published on
LinkedIn
Original date
Nov 2, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Nov 9, 2026: passed. Dry-run tested by our AI test agent on sample input. Steps traced, one unconfirmed size assumption flagged, one record caught falling through an empty fallback, read-only.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 9, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Sales

All 59 Sales playbooks →

Related playbooks

SalesWorkflow✓ AI dry run

Audit an outbound campaign before it launches

Before an outbound campaign goes live, an agent checks inboxes, email validity, recipient email providers, copy, settings, AI variables and spintax, and fixes what it can.

Credit: Dan Rosenthal (@dan__rosenthal)

An afternoon+
SalesWorkflow✓ AI dry run

Gap-check an RFP response against every requirement

Compare your draft proposal with the RFP line by line and get a list of unmet, weak and missing requirements before you submit.

Credit: u/Motor-Draft8124 on r/replit

Under an hour
SalesWorkflow✓ AI dry run

Score inbound leads only when enrichment data arrives

Capture every web-form lead, enrich it, and let AI score and label it only when company data came back; otherwise save it as not scored, tell the team why, and never let a guessed score reach sales.

Credit: Yana1

An afternoon+
Operations & AdminSkill✓ AI dry run

Stress-test an idea with an honest devil's advocate

Get an AI to argue against your plan one serious objection at a time, offer real alternatives with tradeoffs, and openly mark each concern as resolved, narrowed or still open, so you end with a stronger plan or a better one.

Credit: u/wtfzambo on r/ChatGPTPromptGenius

Minutes