04 — Operating System

The shared backend — what runs across both sites and what a buyer would inherit

The two public brands stay separate. The operations behind them don't have to. Both sites already share booking, payment, and document infrastructure. The pipeline layer — unified contacts, cross-site attribution, automated sequences — is what's missing.

For the broker

A buyer who wants both sites to operate independently to the public — same domains, same branding, same audiences — can do that. The backend infrastructure is already built to support it. The architecture diagram below shows what's live. The state table shows what's still manual.

Backend Architecture

One backend. Two public brands.

Both sites are deployed on Cloudflare Pages via GitHub. A central Cloudflare Worker receives events from both sites — form submissions, bookings, payment confirmations — and routes them to the appropriate downstream tools. Connie manages one set of credentials. A buyer inherits one documented operating infrastructure.

PUBLIC SITE A salesassessmenttesting.com Hiring managers · Pre-hire screening Contact form · Order path · Cal.com Cloudflare Pages · GitHub deploy SITE B exceptionalsales.com Salespeople · Coaching · Training · Speaking EKG form · Intake · Cal.com · Stripe Cloudflare Pages · GitHub deploy OWNER-CONTROLLED BACKEND events · forms events · forms CLOUDFLARE WORKER Receives all events · Tags source · Routes to downstream tools Fires automations · No vendor lock-in · Owner account CRM Supabase · unified records both sites · LTV tracking BOOKING Cal.com · all call types webhooks → CRM EMAIL Sequences · triggered by CRM events PAYMENTS Stripe · all products webhooks → CRM DOCUMENTS DocuSeal · agreements coaching · speaking ADMIN Connie's portal one view · both sites

System Modules

What runs underneath both brands

Six modules underpin the operating infrastructure. Each is either already in place or in specification. A buyer inherits the architecture and the tooling accounts.

Worker / Router

Single intake endpoint for both sites. Tags source, identifies client, routes event to correct downstream tool. All logic lives here.

Cloudflare Workers · Owner account

CRM

Unified contact record across both sites. Tracks source, product history, and LTV. Cross-sell triggers fire from here.

Supabase

Booking

All call types — discovery, coaching sessions, speaking consults — routed through one platform. Webhooks push to CRM on booking and completion.

Cal.com · Both sites

Email Sequences

Triggered by CRM events. Onboarding sequences, cross-sell drips, re-engagement. Not yet built — currently manual.

To be implemented

Payments

Stripe for all paid products. Assessment orders, coaching packages, workshop deposits. Webhooks push to CRM on payment confirmation.

Stripe · Both sites

Documents

Coaching agreements, speaking contracts, confidentiality forms. Sent and signed digitally. Stored in client record.

DocuSeal

Current State

What exists · What's manual · What's a gap

A broker reviewing this business is looking at two things: how much revenue is documented, and how much of the delivery depends on Connie personally. This table maps both.

Function Current State Status Buyer Implication
Website infrastructure Cloudflare Pages · GitHub deploy · Both sites live Live Transfers as-is. Buyer inherits both domains and deploy pipeline.
Booking system Cal.com · all call types · both sites Live Transfers. Cal.com account owns all booking history and link types.
Payment processing Stripe · coaching packages and assessment orders Live Transfers. Revenue history lives in Stripe account.
Document signing DocuSeal · coaching and speaking agreements Live Transfers. Signed agreements stored per client.
CRM / contact records Supabase structure in place · Client history being populated In progress Partially transfers. Buyer would complete population of client history.
Assessment order fulfillment Manual coordination by email — Connie receives order, sends link, delivers report Manual Needs automation. This is the highest-leverage operational gap.
Cross-site lead tracking No shared record — SAT buyers and ES clients are not linked Gap Requires CRM wiring. Enables the cross-sell paths shown on the Synergy page.
Email follow-up sequences None automated — all follow-up is Connie's personal outreach Gap Revenue currently stops when Connie isn't actively working. Sequences fix this.
Revenue documentation In progress — both sites being documented by product line In progress Required for due diligence. Completion improves exit multiple.
Coaching methodology Connie's 9-step method — in delivery, not yet written for transfer Gap Limits buyer's ability to hire a replacement coach. High priority for transfer value.