Public intake
LiveAccepted inquiries receive a unique reference and a durable record.
Operating record · Payment status updated September 23, 2026
Meridian uses the controls it recommends.
This is a dated, redacted record of Meridian’s own operating system. It demonstrates working controls—not client results, testimonials, or promised outcomes.
Control snapshot
What operates today.
Each state below reflects a working Meridian control or an explicitly disclosed boundary. The distinction matters more than a polished claim.
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-partyAnonymous session steps are counted without ad pixels or inquiry content.
Service terms
RecordedThe accepted terms version and time must exist before review checkout can open.
Evidence chain
One inquiry. Separate proof at every important handoff.
- 01
Arrival is recorded
The public form validates the request, limits automated abuse, and returns a unique reference without treating the visitor as a customer or collecting payment.
- 02
Messages have their own state
Owner alerts and customer acknowledgements are tracked separately. Provider acceptance, delivery, delays, bounces, and complaints do not collapse into a generic “sent” label.
- 03
A person chooses the next move
The private ledger requires classification and records a provisional cause, recommended engagement, safety boundary, and follow-up deadline before the team makes a promise.
- 04
Payment truth stays exact
A saved inquiry is not a payment. Scheduling remains locked until the processor confirms the exact transaction. Refunds and negative adjustments remain visible exceptions.
- 05
The funnel can be improved
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
Operating proof is not outcome proof.
This record proves that Meridian can operate its own intake, delivery, triage, payment-safety, and measurement controls. It does not prove revenue lift, ranking gains, faster client response, team adoption, or customer satisfaction.
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.
Bring one recurring problem. Keep the first step controlled.
Meridian will tell you whether the evidence supports a review, a repair, a larger build, or no engagement at all.