Candidate GTM Decision Workbench
The first screen after login is the next move, already ranked. One sentence per pursuit: what to do, and why now.
signed-in only read-only against core Blazor Server hosting · Azure App ServiceSystem & data
01 · Data model
PostgreSQL data model
Signal → pursuit → engagement → conversation: one Marketing lifecycle, built as a real PostgreSQL schema.
- Production schema
- 27 tables · 21 foreign keys · 6 version-controlled SQL views
- Shown here
- 7 tables · 9 foreign keys
02 · System design
System architecture
One system of record. One decision workbench. One governed operating loop.
Agent Skills · Postgres · SQL · Blazor · Telerik · Azure
Decision workbench
read-only SQL
Data & measurement
Supabase Postgres + SQL views
The single source of truth — evidence tables and version-controlled SQL views; every published metric is computed here.
schema · see 01 abovereads evidence
writes only after release
Operating loop
Johanna
Sets the brief; reads the funnel, diagnoses the constraint, redirects the next move.
Agent Skills
Recurring judgments, packaged as reusable skills — an expert lens, prior decisions, lessons written back.
Verify the system
Deployed workbench
admin.johannafan.com ↗
A deployed, sign-in-only workbench; its operating surface remains private.Versioned method
candidate-gtm-pipeline ↗
The method, the failure log, and the evidence ledger — open, version-controlled, file by file.
Public schema slice
7 tables · 9 foreign keys ↑
A public ERD generated from production PostgreSQL metadata — inspect it in 01.