Sales
Operating
System
An operating system for the whole sales motion: four layers, working together, from the account universe to what happens next.
The Outcome
One enriched account becomes a personalized Pitch Card today, generated as a PDF and a microsite together. The outreach email and a coordinated physical mailer are the designed next step.
The Philosophy
Generating the asset is the easy part; delivering it with presence is where the value lives. Build the operation, not the assistant: systems that act, remember, and compound.
The System
Four layers: Accounts (the universe) · Knowledge (what the system learns) · Outputs (what it makes) · Workflow (what to do next).
The four layers, the whole system
The operating system for the sales motion, one compound system: the account universe, what the system learns about it (the pipeline is on the Vault), what it makes from it (the live catalog is on Work Flows), and what to do next. The pitch card is one thing the system makes, not the center.
01
Layer One
ACCOUNTS
The universe: every prospect and customer in one structured database.
  • Identity, hierarchy, geography, stage
  • About 3,200 accounts today
  • Built to scale nationally
02
Layer Two
KNOWLEDGE
What the system learns.
  • Every meeting, note, file, or link gets captured, structured, and stored per account
  • Audio also gets a tone read
  • Live today; turning that intel into automatic follow-up tasks is planned, not built
03
Layer Three
OUTPUTS
What it makes: Account Story → Modules → Formats.
  • One story, reused across the Pitch Card (its PDF and its microsite), the outreach email, and the physical mailer
  • Digital is live today; physical is designed, not built
04
Layer Four
WORKFLOW
What to do next.
  • Per-account tasks and follow-ups
  • The strategy turned into action: send a proposal, book a meeting, chase a renewal
↻
Knowledge makes Outputs sharper
Every transcript and research note feeds the Account Story, so the next card and microsite are more specific than the last.
↻
Knowledge is designed to generate Workflow
What the system learns lands as structured decisions, action items, and risks, ready to become follow-up work.
↻
Doing the work feeds Knowledge back
Outcomes return to the account record, so every account makes the next one sharper.
How it runs
Three capabilities power the four layers: agents that act, context that keeps the AI grounded, and memory that compounds.
Agents act

The AI layer monitors, decides, and executes: new meetings and notes ingest on a schedule, and an account-data change renders a card and microsite in one click. Routine steps run unattended; judgment calls stay human.

Context keeps it grounded

Identical prompts produce different results depending on what surrounds them. The system architects what the AI sees at each step: identity (the non-negotiable rules), live data (fetched fresh, never stale), signal (the right things in the right order), and memory (what was decided before).

Memory compounds

Every campaign and outcome is captured, connected to its result, and retrieved on the next run. The system is infrastructure that appreciates: each batch of accounts runs sharper than the last.

The outputs
Outputs are not just the five account-facing deliverables (the Pitch Card, in its PDF and microsite formats, plus the outreach email, the handwritten note, the print card, and the swag). The same account data also drives internal outputs: management reporting, strategy reports, and CRM updates. This is not narrow, account-by-account production. It is the strategy layer for the whole territory.
The full external-outputs catalog is on Work Flows; the internal side (reporting, CRM read/write status) is on Strategy & Pipeline. What it costs versus a manual team is on Economics.
Built on
Claude
The reasoning engine: writes, structures, and verifies every output.
Airtable
The system of record for accounts, content, and rules.
Playwright
Renders pixel-perfect PDF cards from plain HTML.
GitHub
Pipeline, hosting, and audit trail; every change is tracked.
Cloudflare
The secure edge backend that gates every write.
AssemblyAI
Transcribes meetings and separates speakers.
Google Drive
The raw archive, and where finished files land.
Obsidian
Where every Vault note lives: linked, searchable, plain-text markdown.
System status

Data health

Checking…

Skills

Keys & access

🔑 GitHub Key