n8n + GHL + Twilio + Claude / synthetic pipeline lab
The lead is not a send.
A safe insurance lead workflow earns each next state: intake, dedupe, region, consent, qualification, action, and receipt. Replay the seams before a message, CRM write, or human handoff is allowed.
RomeoApps-owned synthetic proof. No insurance client data, GHL account, Twilio send, carrier approval, credentials, or production write is involved. Replay makes zero external API or integration requests.
Fit first / proposed Phase 1
A small paid first unit with a visible stop rule.
The public lab shows the method. A real engagement would map one approved-redacted path and leave a buyer with an acceptance-ready handoff.
What arrives
- One n8n/GHL/Twilio/Claude Phase 1 state map and failure ledger.
- Deterministic fixtures for new, duplicate, wrong-region, opt-out, retry, and missing-approval paths.
- Acceptance checklist for routing, consent, handoff, CRM write, and retry behavior.
- Written evidence receipt with the smallest safe next build step.
Commercial boundary
- The USD 900 is a proposal shape, not a payment request or acceptance.
- Work starts only after written scope, named acceptance owner, protected payment, and safe staging boundary.
- No live calls, customer records, credentials, carrier/A2P claims, or unpaid implementation.
- All outputs are written-first and inspectable before private access.
01 / replay the pipeline
Select the seam that could falsify the lead.
The fixture is intentionally synthetic. It shows which state is earned, where the route holds, and why the next action is or is not permitted.
New lead → qualified route
A redacted lead arrives from an approved source, matches the NC/SC service region, carries consent evidence, and can be routed to a qualified next action.
- The trace will record input, gate decision, stop rule, and receipt in order.
02 / acceptance matrix
A webhook response is not permission.
The pipeline only advances when the evidence required by that gate exists. A lead-shaped payload, a 200 response, or an attempted send cannot stand in for it.
| Case | Falsifying seam | Terminal state | Writes | Evidence |
|---|---|---|---|---|
| New lead | none | PASS qualified route | 0 / synthetic | consent + stable receipt |
| Duplicate | same lead key | DEDUPE no second send | 0 | existing claim reused |
| Wrong region | outside NC / SC | HOLD before action | 0 | region reason |
| Opt-out | do-not-contact marker | HOLD human-safe route | 0 | opt-out timestamp |
| Retry replay | same event id | DEDUPE idempotent receipt | 0 | event key + prior result |
| Missing approval | consent proof absent | HOLD no message | 0 | missing-evidence reason |
03 / truth boundary
The page stops before private access begins.
A buyer can inspect the state machine and acceptance logic without handing over keys, records, accounts, or carrier assumptions.
Verified by this page
- Seven local gates from intake to decision receipt.
- New, duplicate, wrong-region, opt-out, retry, and missing-approval fixtures.
- Explicit hold rules before message, CRM, or human action.
- Zero external API or integration requests during replay; no credentials, customer data, or production writes.
Not claimed
- Client implementation, insurance advice, or customer outcomes.
- GHL, Twilio, carrier, A2P, n8n, or Claude production behavior.
- Compliance approval, deliverability, uptime, or legal sufficiency.
- Buyer selection, acceptance, payment, or settled revenue.
written fit / proposed USD 900 first unit
Bring one lead path that must earn its next action.
Send the public or approved-redacted workflow, desired outcome, service region, consent evidence, safe test boundary, legal payer, and named acceptance owner. Work begins only after written scope and protected payment.
Request a written fit