Deal Thread pilot terms
Terms
These pilot terms set expectations for early Deal Thread workflow builds. A signed order form, invoice, or written pilot agreement may add commercial details such as scope, price, timing, and support commitments.
Pilot scope
A first-workflow pilot focuses on one real workflow, the connected tools needed for that workflow, five reviewed test handoffs, and a go/no-go reliability readout. Additional workflows, custom integrations, and brokerage-wide rollout are separate scopes.
Customer responsibilities
The customer is responsible for confirming tool access, reviewing workflow maps, approving test results, and deciding when a workflow can run against live traffic. Deal Thread should not be treated as a broker of record, legal advisor, compliance reviewer, or transaction coordinator.
Reliability expectations
Automation is useful only when failures are visible. Pilots should include logging, review states, retries, and replay paths, but no workflow can guarantee that third-party tools, APIs, inboxes, calendars, or document systems will always be available.
Commercial terms
Published pricing is an offer framework, not a binding quote. Payment terms, cancellation, refunds, service levels, and production support are defined in the accepted pilot agreement or subscription order.