v1.1 (DRAFT) — CEO causality correction.
v1.0 described the CRM as the trigger surface for deal progression. That was wrong. The correct model: handshakes drive deals, engine drives money, CRM observes. v1.0 superseded same day. See the change log for the full correction record.
Flip360 Enterprise Architecture · v1.1 DRAFT
How the business hangs together
This is the business architecture of Flip360 — not the technical specification. It tells you, in plain English, what each tool does, who owns it, how they talk to each other, and how one dollar of commission travels from a real-world handshake to a partner getting paid. There are four levels of zoom. Start at L1 and drill in as you need to.
Level 1 · 30 sec
Business on a Page
Five-layer stack. Real-world signatures cause everything.
Level 2 · 3 min
Who Owns What
Eight tool cards. CRM marked OBSERVER ONLY.
Level 3 · 5 min
How They Talk
Eight seams. S1: Real World → Chain → Engine.
Level 4 · 10 min
Follow the Dollar
$120k deal, H1 to bank statement, 13 steps.
The picture, at a glance
L1 rendered inline. Read bottom-up: real signatures cause; observers reflect.
▲ rolls up via S5 · Variance → Cascade
Interpretation layer
"What does the ledger mean to me?"
▲ reads via S3 Ledger→Journal · S4 Ledger→Variance
System of record · THE HUB
Commission Ledger + Deal Lifecycle State
One writer (the Engine). Many readers.
Idempotent
Cryptographically signed
Observation layer · READ ONLY
Renders state for human eyes. Does NOT originate state changes.
▲ observers read via S6 Chain→Render (pure reads, no writes)
Causal layer · WHERE DEALS ACTUALLY HAPPEN
Handshake Chain + Legal Entitlements
14 signed event types. 4 handshakes per deal. Cryptographically bound to device keys.
Handshake Chain
H1 → H2 → H3a → H3b → H4
Pine Lawyers Legal
Introducer · Client-Referral · Affiliate
▲ signed by humans on hardware-bound keys (Secure Enclave / StrongBox / WebAuthn)
The real world
Referrer signs H1 · Customer signs H2 + H4 · Partner signs H3a + H3b
Five real signatures by three real parties. These are the only things that cause deals to advance.
The three rules that hold this together
The architectural constitution. Rule 1 is the most important sentence in the entire document.
1
Handshakes drive deals. Engine drives money. CRM observes.
Deal lifecycle is not a salesperson UX flow. A deal advances stage if and only if a corresponding real-world handshake is signed and captured by the chain (H1 → H2 → H3a → H3b → H4). The commission engine consumes those signed events, advances the deal’s lifecycle state, and writes the ledger. The CRM renders that progression for human eyes — it never originates it.
Why it matters: This is what makes Flip360 fundamentally different from Salesforce/HubSpot/Pipedrive. In those tools the salesperson clicks "Move to Won" and the deal is Won. In Flip360, a deal is Won because the customer signed H4 — and nobody, including the salesperson, can make a deal Won without that signature. The handshake chain IS the source of truth. Without it, no $248M exit thesis.
2
Every conversation is a named handshake (a seam)
When two tools talk, they use a named, repeatable, idempotent seam (S1–S8). Each one has a contract: producer, consumer, payload, failure mode. New features can’t just "call into" another part — they go through a known seam.
Why it matters: This is what stops the system getting messy as we scale. The EA function (Claude under delegation) enforces this.
3
Court-defensible beats convenient
Whenever "easier UX" fights with "preserves audit trail," audit trail wins. Always. The handshake chain isn’t decoration — it’s why this thing survives disputes, regulator queries, and exit due-diligence.
Why it matters: Flip360 is a regulated money system (FASEA, ATO RCTI, Pine Lawyers) built for a $248M exit. Trade audit trail for UX once = destroy the exit thesis.
Audience: Steer Co (Matt, Carla, Corrina) + future hires + auditors. Source of truth:
docs/ENTERPRISE_ARCHITECTURE.md (version controlled). EA function: Claude under delegated authority from CEO Matt.