One action boundary
- Observed workflow and written scope
- Allowed, blocked, and review cases
- Implementation in the agreed environment
- Operating and recovery handoff
- Thirty days of stabilization
One action. Two weeks. Written acceptance.
A fixed engagement to place one consequential agent action behind the business approval that must still be current when it runs.
Fixed pilot
A narrow first production boundary.
$6,000$3,000 to begin · $3,000 after acceptance
01
Name the action
Choose one deployment, payment, export, or outbound communication with a clear business consequence.
02
Write the boundary
Identify the responsible person, the approval that must remain current, and the cases that must stop.
03
Implement and test
Connect the agreed action in the client's environment and demonstrate the written acceptance cases.
04
Hand off operations
Deliver test results, operating notes, recovery instructions, and thirty days of stabilization.
The pilot does not provide a compliance certification or authorize regulated actions.
Responsibilities and exclusions
A clear boundary on both sides.
The client remains responsible for the business decision, source approval, account access, and final acceptance.
Authority and access
- Named business owner and approver
- Accurate approval conditions
- Required systems and production accounts
- Legal, regulatory, and policy decisions
- Written acceptance decision
Work beyond the pilot
- Multiple unrelated actions
- Full workflow or platform replacement
- Compliance certification
- Regulated decision authority
- Unbounded product development
Discuss one action
Tell us what the agent is allowed to change.
Use the business consequence, not a technical specification. We will reply personally to decide whether the action is narrow enough for the pilot.
Pilot conversations are currently open