Public intake
LiveAccepted inquiries receive a unique reference and a durable record.
Operating record · Controls reviewed November 2, 2026
See how Meridian records its own enquiries, separates delivery and payment evidence, and keeps a person responsible for the next step. Client outcomes are measured separately.
Control snapshot
Each state below reflects a working Meridian control or an explicitly disclosed boundary. The distinction matters more than a polished claim.
Public intake
LiveAccepted inquiries receive a unique reference and a durable record.
Email evidence
LiveOwner and customer messages have separate provider and delivery states.
Human triage
LiveCause, starting engagement, safety boundary, and follow-up deadline require owner review.
Payment safety
Review checkout openThe $950 Business Process Review checkout is open. Live unpaid session creation, expiry, and duplicate-event handling were verified September 21; sandbox paid success and failure were also verified. A successful live payment, paid notices, scheduling path, and payout remain unproven. A person confirms scheduling after payment.
Funnel measurement
First-partyBest-effort anonymous session steps are counted without ad pixels or inquiry content. A checkout redirect attempt is not a payment.
Service terms
RecordedThe accepted terms version and time must exist before review checkout can open.
Evidence chain
The public form validates the request, limits automated abuse, and returns a unique reference without treating the visitor as a customer or collecting payment.
Owner alerts and customer acknowledgements are tracked separately. Provider acceptance, delivery, delays, bounces, and complaints do not collapse into a generic “sent” label.
The private ledger requires classification and records a provisional cause, recommended engagement, safety boundary, and follow-up deadline before the team makes a promise.
A saved inquiry is not a payment. Scheduling remains locked until the processor confirms the exact transaction. Refunds and negative adjustments remain visible exceptions.
Meridian counts anonymous first-party steps from visit to inquiry, while keeping names, email addresses, and problem details out of the funnel record.
What this does not prove
These controls describe Meridian's own intake and follow-through. Revenue lift, ranking gains, faster client response, team adoption and customer satisfaction each need their own evidence.
A client outcome will be published only with permission, an agreed baseline, a documented repair, enough operating time to compare the same measure, and client approval of the final artifact.
Meridian will tell you whether the evidence supports a review, a repair, a larger build, or no engagement at all.