← Back to Daily Builds

Daily build note · June 18, 2026

Agency AI Visibility Pilot Pack

A deterministic packaging layer over the Local AI Visibility Watchboard that turns generated local AI visibility packets into a productized agency consulting offer: one-pager, pilot offer...

Consulting Offers / Productized Services Build note published Public demo coming soon

What shipped

Built a standard-library Python CLI package named agency_ai_visibility_pilot_pack with three commands:

  • sample: creates a seeded Local AI Visibility Watchboard-compatible demo workspace.
  • pilot-pack: reads watchboard/watchboard.json and generates a complete sales-pack/.
  • validate-pilot-pack: validates required files, JSON, pricing, demo coverage, CSV shape, and compliance language.

The generated pack includes the required Markdown, CSV, and JSON artifacts for an agency-ready pilot offer, intake, outreach, discovery, pricing, SOW, and client handoff workflow.

Architecture

  • Standard library only: argparse, csv, json, pathlib, and datetime.
  • watchboard/watchboard.json is the primary contract, matching the parent Local AI Visibility Watchboard output shape.
  • The sample command mirrors the parent demo businesses (east-nashville-dentist, brentwood-hvac, and germantown-cafe) without importing or modifying the parent build.
  • Templates are deterministic Python renderers so the MVP is easy to inspect and change.
  • Validation is intentionally strict around required artifacts, price points, no-ranking-guarantee language, source freshness, human verification, and human approval.

Trimmed scope

Intentionally excluded:

  • Web UI
  • Database
  • Auth
  • Billing
  • CRM sync
  • Email sending
  • Google Business Profile API
  • OpenAI, Claude, Anthropic, OpenRouter, Gemini, or other provider calls
  • Scraping, browser automation, live ranking checks, or automated posting

Limitations

  • The pack is template-driven and deterministic; it does not infer new facts beyond supplied watchboard fields.
  • The sample data is realistic but synthetic.
  • Existing client workspaces must already provide a compatible watchboard/watchboard.json.
  • Validation checks text coverage and known forbidden phrases, not full legal or platform compliance.

Suggested next steps

  • Add optional support for reading more detail from parent Markdown files when watchboard.json is sparse.
  • Add a --client-name or --agency-name option for lightweight personalization.
  • Add tests around sparse or malformed watchboard payloads.
  • Add an export bundle command that zips sales-pack/ after validation.