Tour follow-up agent
Qualify tour requests and draft fast venue replies with owner approval.
Generated from setupyour-workflow-products
Workflow Automation Sprint blueprint demo
This is the next sellable artifact after an Opportunity Map: a scoped automation sprint with phases, proof gates, approval boundaries, and explicit non-goals before deeper integrations are sold.
One useful path first.
Reply to qualified tour requests within one business day.
Generated blueprint
Sprint plan with proof gates.
The blueprint names what is not included yet, including write access to customer systems.
# Workflow Automation Sprint Blueprint: Mountain View Events Operator: Jim ## Recommended first workflow - Tour follow-up agent: Qualify tour requests and draft fast venue replies with owner approval. ## Current tools - Gmail, Google Calendar, Squarespace ## Success metric - Reply to qualified tour requests within one business day. ## Sprint phases 1. Workflow confirmation - Confirm the Tour follow-up agent workflow, source inputs, owner handoff, and failure modes. Proof: Signed-off workflow map and example input set. 2. Sprint scope and quote - Set the bounded v0 scope, price, timeline, and approval policy. Proof: Quote packet names included systems, non-goals, and human approval gates. 3. Deterministic path first - Create the intake, routing, summary, and operator-visible queue before adding AI drafting. Proof: Representative input creates the expected internal record or queue item. 4. AI assist with refusal paths - Add AI drafting or classification, then run high-value, ambiguous, and risky examples. Proof: Verification log shows useful outputs and safe escalation for risky examples. 5. Human-approved launch - Launch only the approved v0 path with visible errors and rollback instructions. Proof: Launch checklist names owner approval, monitoring, and rollback. 6. Monthly improvement loop - Review transcripts, stuck items, misses, and expansion candidates after launch. Proof: Monthly report shows volume, misses, fixes, and next recommended improvement. ## Human approval gates - Owner approves every outbound reply before anything is sent. - Jim reviews the first production examples before launch. - Customer approves any external send, customer-system write, payment-affecting action, or policy exception. ## Non-goals for v0 - No autonomous external sending in v0. - No CRM/calendar/email write access until the customer explicitly approves that integration path. - No migration of existing customer systems during the first sprint. ## Pricing anchor - One workflow starts around $5,000; multi-system work is scoped higher.