# Example: a small operations team's request handoff

This is fictional demonstration data, not a customer testimonial.

Problem: requests arrive in inconsistent formats; staff retype owner and due-date fields.
Target: validate requests and produce a consistent task draft, without automatically sending it.
Baseline: 200 requests/month x 6 minutes = 20 hours.
Scenario: automate 75% of handling, saving 15 hours valued at $20/hour = $300/month of time value.
Cash revenue: unknown. Initial and recurring local software cost: $0.

Example input: {"record_id":"demo-001","owner":"ops","request_type":"task","payload":{"title":"Review invoice","due":"2026-10-01"}}
Output: {"task_id":"demo-001","team":"ops","title":"Review invoice","due":"2026-10-01","state":"draft"}
Replay: the same input returns the same draft, without a second action.
Missing owner: {"state":"held","reason":"owner_required"}.

Before using a real integration, replace fictional values and run the included acceptance cases.
Start with draft creation; do not auto-send emails, publish records or process payments.