Three client-ready deliverables from a single workflow run: an owner-facing report, a developer remediation brief, and a schema-valid AICV node seed — plus a saved workflow that can now run against any valley business.
Wilma Frieda's came off the top of the restaurant prospect list and went straight into the entity workflow. The audit looks at how a business appears to AI agents — not just Google — across web visibility, structured data, citation patterns, and discoverability signals. Two audiences, two documents: the owner report (~1,500 words) stays non-technical and actionable; the developer brief (~6,272 words) goes deep on what's broken and how to fix it. A schema-valid AICV node seed came out as a third artifact, ready to add the business to the intelligence corpus.
The first run was a one-off — 16 agents, built inline, no reusability. It worked well enough to warrant formalizing. The second run was a smoke test of the structured workflow: 20 agents, same outputs, same quality, but now parameterized and saved to .claude/workflows/cv-agent-audit.js. It's also registered as a skill, so any future audit starts with a single command and a business slug. The pre-flight failed fast on the first attempt — a script issue caught in under a second before any agent spend — which is exactly what pre-flights are for.