Ship one real workflow before funding a larger system.

What is included

• One approved trigger from a form, message, webhook, CRM event, or similar source
• One bounded qualification, transformation, or routing path
• One calendar, CRM, spreadsheet, inbox, or API destination
• One human escalation or exception path
• Test cases, launch QA, and concise handoff notes
• One focused revision round inside the agreed scope

What to send

Name the trigger, current tools, required destination, broken handoff, expected volume, urgency, and who should take over when the automation should stop.

How acceptance works

Before payment, both sides agree the sample input, expected output, permissions, edge cases, and observable pass criteria. Expansion is quoted only after this slice is accepted.

What it is not

The pilot is not a complete omnichannel agent, unrestricted scraping or platform bypass, a full CRM migration, a multi-location rollout, or an unsupported revenue guarantee. Those require separate discovery and scope.

Timing and access

The three-business-day window begins after payment, complete access, approved data, and written scope confirmation. Vendor review, missing credentials, policy limits, or delayed feedback pause delivery.

Best first slices

Lead-to-calendar routing, Instagram or WhatsApp qualification, missed-enquiry recovery, CRM field mapping, booking notifications, owner summaries, and failing n8n or webhook workflow repair.