Dossiers // All files
19 systems. Zero client pixels.
Every file below is a real, running system. Client names are withheld under NDA, and every interface you’ll see is redrawn as an exhibit — never a screenshot. I’m happy to walk through specifics on a call.
01 // Systems index
19 files · client names withheld under NDA
CS-010 LEADS LEFT WAITINGAI Booking ConciergeLocal martial-arts academy0 LEADS LEFT WAITINGTopologyTriggerAny inbound SMS or email, day or nightWhat got doneConversation AI answers and qualifies every lead · Deterministic routing into 5 age-segmented calendars · Human handover on medical, billing & hostile edge casesRead dossier →CS-02100% OF DEAD LIST WORKED AUTOMATICALLYDead-Lead Reactivation EngineLocal service business with a cold lead list100% OF DEAD LIST WORKED AUTOMATICALLYTopologyTriggerA cold list import — hundreds of unworked leadsWhat got doneBuilt a one-shot 30-day drip — 7 SMS and 8 emails on a paced schedule — that works the entire cold list end-to-end with no manual effort · Ran AI intent detection on every reply, pulling positive-intent leads out of the drip and handing them to the AI booking concierge to close · Wired an automatic booking-exit so a booking on any calendar removes the lead from the campaign and tags the winRead dossier →CS-0322.6K CONTACTS AUDITEDCRM Systems Audit & CleanupHigh-ticket education business22.6K CONTACTS AUDITEDTopologyTriggerA read-only teardown of the entire accountWhat got done22,616 contacts and 8,608 opportunities mapped · All 172 workflows documented, step by step · Revenue-attribution model: source → rep → verified revenueRead dossier →CS-041 SITTING BLANK PAGE → FINISHED SUMMARYAI Book-Summary WriterAuthor-coaching program1 SITTING BLANK PAGE → FINISHED SUMMARYTopologyTriggerAn author sits down to start their book summaryWhat got doneDesigned and built a standalone Next.js app — App Router, React, Tailwind, and the Vercel AI SDK with OpenAI — branded to feel native to the client's main product · Built an AI interviewer that asks one question at a time, with separate paths for teaching-style books and memoirs · Streamed a paste-ready structured summary — 5 paragraphs, expandable to 10 — the author can drop straight into the main platformRead dossier →CS-05+40% RE-ENGAGEMENTAI Accountability PlatformSubscription accountability app+40% RE-ENGAGEMENTTopologyTriggerA member goes silent, or a trial nears its first billingWhat got doneTiered SMS journeys fire off real member behavior · Decision AI branches crisis-recovery vs motivational flows · Stripe lifecycle triggers catch lapsing trials pre-billingRead dossier →CS-06+35% RETENTIONSubscription FunnelRecurring membership offer+35% RETENTIONTopologyTriggerA payment fails, or a member hits a tier boundaryWhat got doneBuilt a conditional-access funnel for the three membership tiers, gating content by active subscription state · Added dynamic pricing tables and one-click upsells so members could move up a tier without leaving the flow · Wired Stripe-triggered dunning — failed-payment retries and recovery messaging — so churn revenue recovered itself instead of walking out the doorRead dossier →CS-07+28% QUOTE-TO-BOOKLocal SEO & ConversionLocal service business+28% QUOTE-TO-BOOKTopologyTriggerA lead lands from Google, Facebook, or the websiteWhat got doneBuilt service-area landing pages mirrored to the Google Business Profile so local searches landed on matching, conversion-focused pages · Fed every channel into one unified CRM with call tracking and source attribution, so each booking traced back to the campaign that earned it · Automated quote follow-ups on a fixed cadence so no lead went cold between quote and decisionRead dossier →CS-08−70% MANUAL FOLLOW-UPSService Business PlatformService business (website + booking)−70% MANUAL FOLLOW-UPSTopologyTriggerA new inquiry hits the rebuilt websiteWhat got doneRebuilt the website with lead-capture forms wired directly into GoHighLevel, so every inquiry became a tracked contact instantly · Automated the booking calendar with instant confirmations and reminders, cutting the back-and-forth to schedule a quote · Added automatic follow-ups on any unanswered inquiry so none went cold while the owner was out on a jobRead dossier →CS-09100% TRAININGS AUTOMATEDTraining & Onboarding AutomationCoach running weekly live trainings100% TRAININGS AUTOMATEDTopologyTriggerA registration for the weekly live trainingWhat got doneBuilt a full journey — registration → confirmation → Zoom-integrated reminders — so each session ran itself from signup to seat · Automated tutorial-video delivery through Vimeo, drip-sequenced so new users onboarded in order instead of stalling · Added no-show recovery flows that re-booked missed sessions automatically instead of losing the attendeeRead dossier →CS-109 CLIENT BUILDS IN 5.5 WEEKSWhite-label agency deliveryMarketing agency · nine clinic builds9 CLIENT BUILDS IN 5.5 WEEKSTopologyTriggerAn agency selling campaigns faster than it could build the systems behind themWhat got doneStandardised a repeatable build blueprint — 8-stage pipeline, ~17-workflow set, AI receptionist with knowledge base, booking calendar, deposit mechanism, landing page — diverging per client with a written record of every deviation, never silently · Wrote a 13-to-36-document spec and design pack per client, so copy and architecture were approved before anything touched a live sub-account · Made verification its own phase: read every write back from the live account, ran up to five audit passes per build, and treated "the API returned success" as unprovenRead dossier →CS-115 SILENT FAULTS FIXED IN A "FINISHED" BUILDLive launch & fault triageAesthetics clinic · via agency5 SILENT FAULTS FIXED IN A "FINISHED" BUILDTopologyTriggerA paid campaign about to go live on a system nobody had provenWhat got doneCleared the send window on the four workflows where speed to lead decides the outcome, so an overnight enquiry is answered on arrival · Upgraded the AI receptionist from link-sending to real calendar actions — live availability, booking, rescheduling, and cancelling only on an explicit confirmed yes · Built a 9-message, 12-day sequence for leads who never reply — each message answering a distinct hesitation, not repeating the nudge — plus a second track for reply-then-quietRead dossier →CS-1224H SLOT HOLD — CONFIRMED NOW MEANS PAIDDeposit-gated booking architectureAesthetics clinic · single-treatment programme, via agency24H SLOT HOLD — CONFIRMED NOW MEANS PAIDTopologyTriggerA diary full of confirmed bookings nobody had paid forWhat got doneRedefined the states: a slot is written the instant the patient books but as unconfirmed; confirmed thereafter means only that the deposit is paid, with a 24-hour hold · Added two keyed, idempotent endpoints to the booking worker — one that marks the slot paid and confirmed, one that frees an unpaid hold — and wired them into the deposit workflows · Repointed four workflow triggers in one cutover, leaving nothing keyed on the confirmed state that could re-enrol a patientRead dossier →CS-130 COORDINATOR MESSAGES POSSIBLE — COMPLIANCE BY STRUCTURERegulated-market lead engineHome-care agency · multi-county footprint, three payer lanes0 COORDINATOR MESSAGES POSSIBLE — COMPLIANCE BY STRUCTURETopologyTriggerAn empty account, and a referral channel where one wrong message is a felonyWhat got doneCaptured all eleven account surfaces read-only before designing anything, so the build started from live state, not assumption · Made the felony-risk constraint structural, not policy: a coordinator-tag guard that ends the run sits at step one of nine workflows; the tenth carries the inverse guard and zero outbound sends · Reverse-engineered the platform’s form renderer to recover the real field-mapping schema, and proved the fix with a browser accessibility snapshot rather than a 200 responseRead dossier →CS-1448/57 TICKETS SCANNED AT THE DOOR — NONE COUNTED BY HANDEvent ticketing & door check-inHigh-ticket education business · sibling of CS-0348/57 TICKETS SCANNED AT THE DOOR — NONE COUNTED BY HANDTopologyTriggerA workshop purchase — or a walk-in at the doorWhat got doneSigned, single-use, non-forgeable QR tickets generated on purchase or registration and emailed under the client’s branding · A door scanner that runs on any phone — with a software-decode fallback added after the native scanner failed on every iPhone on event day · Walk-in registration issuing a ticket and QR on the spotRead dossier →CS-1513 PURPOSE-BUILT SCREENS, LIVE ON THE CLIENT’S DOMAINAds & sales reporting dashboardHigh-ticket education business · sibling of CS-0313 PURPOSE-BUILT SCREENS, LIVE ON THE CLIENT’S DOMAINTopologyTrigger“Which spend produced which enrollment?” — and numbers nobody trustedWhat got doneDeployed single-tenant — its own database, hosting, token and domain — so no client’s data can ever reach another’s · Six scheduled edge functions with lease/lock, retry and audit rails, so an outage leaves a recoverable gap instead of a permanent hole · Enforced data honesty in code: a judgement floor before any ad is flagged, a refusal to total non-additive metrics, a freshness signal for the re-attribution windowRead dossier →CS-16~390 AUTOMATED TESTS GREEN BEFORE STORE SUBMISSIONNewborn-care companion appConsumer app founder · via agency partner~390 AUTOMATED TESTS GREEN BEFORE STORE SUBMISSIONTopologyTriggerA folder of flat mockups, a store deadline, and 3am logging on bad wifiWhat got doneMined the client’s own mockups and PDFs for embedded full-resolution artwork — recovering ~60 native assets including six mascot states, so the logo is the client’s logo, exactly · Rebuilt 25 screens on shared design tokens — a global change is one edit, not twenty-five — then extended to the screens the mockups never covered · Built an insert-only offline outbox on client-generated ids with duplicate-ignoring writes, so replaying a queue after a crash cannot double-log a feedRead dossier →CS-17100 API ENDPOINTS ACROSS THE PRODUCT’S TWO SERVICESAI book-writing applicationDigital publishing product · sibling of CS-04100 API ENDPOINTS ACROSS THE PRODUCT’S TWO SERVICESTopologyTriggerA customer signs up to write their first bookWhat got doneStructured the web front end as 14 page routes and 37 API handlers acting as a backend-for-frontend, so the browser never talks to the Python service directly · Extracted business rules into eight framework-free logic modules, each with a colocated unit test — trial phases, offer selection, tutorial staging, timezone and phone normalization · Diagnosed the invisible-tutorial regression to a two-step interaction — a popup marking itself seen before a routing rewrite destroyed it — fixed it by moving one write from open-time to close-time, then reproduced the failure live to prove the fixRead dossier →CS-1821 REPLICATION DOCS — ONE LIVE SITE, BUILT TO BE FORKEDReplicable studio website + CRM templateMartial-arts academy · same client as CS-01, via agency21 REPLICATION DOCS — ONE LIVE SITE, BUILT TO BE FORKEDTopologyTriggerAn ad click — or the agency signing its next studioWhat got doneBuilt 26 pages and 17 endpoints server-rendered, including six channel-specific ad landers so paid traffic lands on copy matched to its source · Funnelled every CRM call through a single orchestration module — rate limiting, idempotency, webhook secrets and signed tokens as dedicated helpers, not scattered calls · Kept every staff-editable setting in the CRM rather than in env vars — staff change deadlines and copy from the CRM, and the site follows without a redeployRead dossier →CS-199 POINT SCORECARD, LIVE INSIDE EVERY CLIENT’S CRM DASHBOARDAgency onboarding platform + client scorecardMarketing agency · the agency behind CS-01 and CS-189 POINT SCORECARD, LIVE INSIDE EVERY CLIENT’S CRM DASHBOARDTopologyTriggerA studio signs — and onboarding used to be a 90-minute manual checklistWhat got doneOne deployment, two hosts: agency admin and client portal split by host-based routing in middleware, default-deny, so a portal request can never reach an admin handler · Onboarding modelled in eight Postgres tables — including a dedicated corrections table so a studio can amend a submitted intake without the agency re-keying it · The scorecard built as a signed widget route, iframe-embedded in each studio’s CRM dashboard — the agency edits once, every dashboard reflects it, no re-pushRead dossier →CS-20SLOT OPENPending assignmentCould be your operationSLOT OPENTRIGGER: a founder read nine files and recognized their own bottleneck. BUILD: unwritten. → BOOK
02 // Work order
How an engagement runs — and where it starts
WORK ORDER — Nº 001Intro call // free · 30 min
- 01Intro callFree, 30 minutes. We map what's leaking and whether automation even fits. Not a fit? I say so — no charge.
- 02Audit & blueprintA fixed-scope teardown of your client journey. You get a written blueprint you can act on — with or without me.
- 03Build & testBuilt on GoHighLevel + Stripe, documented as it ships, QA'd against real scenarios before go-live.
- 04HandoverLive walkthrough, full documentation, complete ownership. Your accounts, your IP — no dependency on me.
Most builds ship in 3–6 weeksYou’ll hear back within one business day
Book the intro callWhite — client (withheld under NDA) · Yellow — operator · Pink — file ← you are reading the file copy