Use these to test the offer

Demo Problems

These examples let prospects test the report style without exposing private production systems.

Complex workflows are why we’re here. We work in bounded stages so the workflow becomes understandable before anyone jumps to a fix.

1. Cursor-based sync timeout

A scheduled job syncs records from Service A to Service B. The source API uses cursor pagination. Timeout and retry cause duplicates and missed records.

Try this demo

2. Queue worker with side effects

A queue worker writes invoice rows, updates balances, and sends emails. Retry after a partial failure sometimes charges twice or sends duplicate emails.

Try this demo

3. CSV import resume bug

A CSV import resumes from the last processed line number. Each line can create several related rows. Partial line failure leaves inconsistent data.

Try this demo

4. Multi-service onboarding

A signup workflow creates accounts, billing profiles, permissions, CRM records, and welcome messages. Timeout leaves users partially onboarded.

Try this demo

Good demo inputs

A good demo input has a workflow, a failure mode, at least one cycle, and some uncertainty about state, retries, handoffs, or side effects.

Good: “The job paginates records and retries after timeout.”
Good: “A queue worker fails after writing to one service but before marking the event complete.”
Less useful: “My app is broken.”
Less useful: “Here is my entire repository.”