Multi-site program
A procurement page, not a maturity claim.
We do not claim that the software is enterprise-ready. We start with one paid pilot, and we scope a program only after the journey and the boundaries are agreed.
Browser, process, and network isolation for authorized runs is open work, not a deployed control. We state the current status in the agreement.
Discuss multi-site monitoringRead the security page
Our test sessions declare AgentJourneyLab/0.1. Site owners can stop a public test: read the research boundary or write to research@agentjourneylab.com.
Workflow
The workflow
- One paid pilotOne site and one journey, at $199.
- Agreed scopeWe agree the journeys, the sites, and the completion criteria.
- Written authorizationYou confirm your authority for each domain in writing.
- Data termsWe agree data handling, retention, and deletion.
- Scheduled runsWe run the agreed journeys on the agreed dates.
- ReviewWe review the records with you and we agree the next period.
Procurement facts
Procurement facts
| Delivery model | Operator-led. A person runs each test and sends the record by email. |
|---|---|
| Engagement start | A written scope, then payment. No work starts before both. |
| Authorization | You confirm domain authority in writing. A third-party platform needs its own permission. |
| Test data | Synthetic data only. No real customer record, no health data, and no payment card. |
| Access | No access to your systems. We use the public journey unless the scope states more. |
| Evidence storage | Records are held outside the public website and sent to you by email. |
| Retention | Enquiry email for about 12 months after the last message. Paid-work records as long as tax and accounting rules require. |
| Processors | An email provider and a web host. We sell no data and we share none for advertising. |
| Publication | Results stay private. We publish nothing about a named site without written permission. |
| Price basis | $199 for the pilot. $199 per site each month for optional monitoring. A multi-site program is priced in the agreement. |
Readiness
Readiness, stated plainly
Enterprise use is conditional on our readiness gates and on the written scope. Today we deliver the work by hand. Browser, process, and network isolation for authorized runs is open work, not a deployed control. We state the current status in the agreement.
Fit
Fit
A good fit
- You hold many sites or locations with one journey model.
- You can authorize tests for the group in one document.
- You want a dated record for each site.
Not a fit yet
- You need a certification or a compliance report.
- You need an availability commitment.
- You need a self-service product with accounts.
Next step