Pilot terms

These terms keep the pilot useful and finite. They are a practical project boundary, not a promise that every submitted workflow can or should be automated.

One agreed workflow

Kevin will evaluate one workflow, may ask one focused clarification, and—if accepted—will request one five-minute recording. If targeted information is missing, one follow-up recording may be requested. Kevin may decline before or during solution design if the project is unsafe, unauthorized, unsuitable, or not reasonably implementable.

Cost and ownership

Kevin’s pilot implementation work costs $0. A working solution will most likely require software costing about $30/month, paid directly by the customer; the exact amount may vary. The customer owns or must obtain authorization for every workflow and system used.

Implementation and support

The customer stays signed in on their own computer and does not share passwords. The implementation session is capped at 60 minutes. After Kevin marks the launch successful, support covers defects against the approved scope for 5 business days. It excludes new features, new workflows, ongoing maintenance, and general consulting.

Human responsibility

Consequential financial, legal, health, employment, identity, safety, or customer-impacting decisions remain subject to human review. The customer is responsible for reviewing outputs, maintaining authorized access, and deciding whether to keep using the solution.