Sample delivery handoff.

A paid sprint should not end with a vague "it's done." This sample shows the kind of scope summary, QA evidence, artifacts, and acceptance checks WorkflowPatch ships with.

Start Async Fit Check View Agency Overflow QA View CRM Sync Demo View Webhook Demo Reference Patterns

This is a sample handoff, not a client case study. It uses synthetic CRM sync details to show the operating standard before a buyer shares real data or pays for a sprint; agency overflow readers can also inspect the synthetic QA ledger.

Where This Shape Fits

Client Workflow Overflow

Lead, order, or form event -> validation and routing decision -> CRM, Monday, or Sheet update with an error log and handoff.

Agency Overflow QA

One approved client slice -> internal QA evidence -> approval queue, blocked scope, and handoff before anything client-visible ships.

Document Or Email Pilot

Approved document, email, or CRM export -> extraction or classification -> human review queue with accepted, blocked, and hard-error rows.

Webhook Reliability Slice

One inbound webhook -> idempotency and match policy -> accepted ledger, conflict queue, retry path, and operator runbook.

Confirmed Scope

Source

Close appointment webhook and redacted GHL contact-change sample.

Transformation

Normalize contact keys, apply match policy, prevent duplicate sync loops, and classify conflicts.

Destination

Review-ready sync ledger, conflict queue, hard error log, and operator runbook.

QA Evidence Matrix

Check	Evidence	Result	Buyer Action
Valid Close appointment creates GHL-ready row	Mock event APPT-1001 produced sync ledger row with contact key and appointment timestamp.	Passed	Approve field mapping before live write.
Duplicate webhook does not create duplicate side effect	Replay of APPT-1001 was blocked by idempotency key and written to the run log.	Passed	No action unless duplicate rate spikes.
Missing email or phone is held for review	Contact sample GHL-2004 routed to conflict queue with reason missing_match_key.	Passed	Decide whether manual match or ignore is correct.
API rejection stays visible	Mock destination 400 response produced hard error row with endpoint, payload id, and retry note.	Blocked safely	Fix credential/field issue, then rerun from ledger.

Artifacts Delivered

Operator Files

Sync ledger CSV
Conflict queue CSV
Error log CSV
Short runbook

Implementation Notes

Match key policy
Replay and retry path
Known exclusions
Access cleanup reminder

Acceptance Checks

Buyer confirms sample outputs
Blocked cases are understandable
Runbook is enough for first operator use
Care plan decision is explicit

Closeout Message Shape

Subject: WorkflowPatch sprint delivery - CRM sync proof

Hi Buyer,

The first CRM sync proof is ready for review.

Delivered:
- accepted sync ledger
- conflict queue
- hard error log
- operator runbook
- QA evidence matrix

Please review the three sample paths:
1. accepted appointment update
2. duplicate webhook blocked by idempotency key
3. contact held for manual review because the match key is missing

If those outputs match the agreed scope, reply "accepted" and I will close the sprint. If you want monthly care, I can send the care link after acceptance.