Input
Webhook, form, email, spreadsheet row, CRM lead, uploaded CSV, or scheduled report trigger.
Concrete sample deliverable
What one paid workflow slice looks like after Petaflo ships it.
This sample shows the shape of a small AI automation delivery: one trigger, one business path, controlled AI usage, fallback states, test evidence, and a handoff note your team can maintain.
Sample scope
The point is not to build the whole operating system first. The point is to ship one useful path with enough guardrails that an agency or internal team can trust it and decide whether to expand.
Processing
Field cleanup, enrichment, AI classification/drafting/summarization, API calls, and routing logic.
Output
CRM update, email draft, Slack alert, report file, Google Sheet row, client handoff note, or next-step task.
Sample implementation notes
A real delivery would use the client's stack. This sample keeps the pattern visible without exposing client credentials or private business data.
{
"workflow": "lead-triage-v1",
"trigger": "new_form_submission",
"steps": [
"validate_required_fields",
"normalize_contact_and_company",
"classify_intent_with_llm",
"route_by_urgency_and_fit",
"draft_human_review_reply",
"write_log_record",
"notify_owner"
],
"approval_gate": {
"required_for": ["external_email_send", "low_confidence", "pricing_discussion"],
"fallback": "queue_for_manual_review"
},
"test_records": 5,
"handoff": ["runbook", "field_map", "failure_modes", "next_scope"]
}
What gets handed off
Build evidence
- Workflow diagram or node list
- Sample input and output records
- Test cases and observed results
- Known limits and assumptions
Operating note
- How to run or trigger the workflow
- Where logs and failures appear
- Which actions require human approval
- What to build next if the slice proves useful
Send one workflow that is stuck.
Include the trigger, tools/accounts, sample input, expected output, current blocker, and timeline. Petaflo will reply with one fixed first-slice scope.