Q2See

Buyer & pain

Revenue Systems Engineer / Salesforce BSA / RevOps Architect — quote-to-cash is the highest-stakes RevOps seam. When it breaks, real dollars disappear: un-invoiced contracts, un-billed renewals, amount mismatches that got paid at the wrong number. Nobody renders the full chain — Opportunity → Quote → Contract → Invoice → Renewal — as a navigable, per-record graph where you can click a broken handoff and get a structured, system-attributed diagnosis.

Problem

Salesforce CPQ surfaces quote state. Ironclad surfaces signature state. Stripe surfaces invoice state. No native join confirms the contract-exec trigger fired into billing. Orphaned contracts are invisible. The failure manifests as: "we have 12 signed contracts that did not trigger invoicing — find them." That's a custom SOQL query + a CSV + a meeting. Q2See replaces that meeting.

What the 30-second demo proves

1. Object-level Q2C architecture — Contract, Quote, Invoice, and Renewal are modeled as distinct objects with their own owners, states, and linking keys. Not interchangeable nouns.
2. Handoff-level diagnosis, not dashboard-level reporting — each broken edge names the owning system (CPQ / CLM / Workato / Zapier), the exact trigger that failed, and the step-numbered fix.
3. System thinking, not record-tailing — the six planted breaks are the actual production failure modes: orphaned contract, amount mismatch from race condition, term gap, orphaned quote, currency mismatch, null renewal owner.
4. Engineering, not configuration — HandoffEdge is a first-class type; rules are pure functions; dagre layout + React Flow custom nodes. This is built, not clicked together.

How it works

1. Flow graph — 40 synthetic opportunities threading through five node columns (Opportunity → Quote → Contract → Invoice → Renewal). Edges color-coded by handoff health: healthy muted green, warning amber, broken red-orange, at-risk orange. Graph centers on the most critical finding (B-01, Crestline Digital) on load.
2. Inspector panel — clicking any node opens the inspector: object type, linked records, system owner, verbatim "What Broke / Which System Owns It / The Fix" structured finding for flagged nodes.
3. Six planted handoff breaks — B-01 orphaned contract ($48k, Workato paused), B-02 amount mismatch ($2,400 delta, race condition), B-03 term gap (14-day billing window), B-04 orphaned quote (rep created two), B-05 currency mismatch (Canadian entity added mid-deal), B-06 null renewal owner (CSM departed, never reassigned).
4. Findings rail — all active anomalies pinned to the bottom with "Jump to node" links that center the graph and open the inspector.
5. Import your data (real backend) — upload a CSV export of your own pipeline (one row per opportunity, lifecycle columns inline). A Cloudflare Pages Function (POST /demos/q2see/analyze) parses it server-side into the same five-object flow and runs the broken-handoff detection rules against your rows — orphaned contracts, amount/currency mismatches, approved-quote-no-contract, unowned renewals, overdue AR. The graph, inspector, and findings rail then render your data, with the banner switching to a "your data" boundary notice.

Integration surface

Static Astro site with a vanilla-TS inline-SVG flow graph. Two data paths: (1) a synthetic JSON fixture set that ships with the demo, and (2) a real Cloudflare Pages Function backend (/demos/q2see/analyze) that inspects an uploaded CSV/JSON export server-side. The detection rules are real; the boundary is honest — it analyzes a point-in-time export you provide, not a live Salesforce/Stripe OAuth connection, and stores nothing. No secrets. Deploys as a Cloudflare Pages subpath.

• Astro 5
• Vanilla TS + inline SVG
• Cloudflare Pages Functions
• TypeScript
• Synthetic default + real CSV import
• Unit-tested rules engine