Multi-site program
A procurement page, not a maturity claim.
This page tells a buying team how we work across many sites, what we need from you, and what we do not offer yet.
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.
Workflow
From one pilot to many sites
- One paid pilotWe test one journey on one site for $199. You see the record, the boundary, and the way we work.
- Agreed scope for the groupWe write the journey model, the completion criterion, the site list, and the stop rules. You approve the text.
- Written authorizationA person with authority for the domains signs the authorization. It names the domains, the journey, the test identity, the rate, and the action boundary.
- Data termsWe agree the data that a run may touch, the retention period, the deletion rule, and the subprocessor list before a provider-backed run.
- Scheduled runsWe run the journey on the agreed schedule. Each site gets a dated record, and the group gets a summary of the differences.
- ReviewWe hold a written review at the end of each period. You can stop the program at the end of a paid month.
Procurement facts
The answers that a buying team needs
These are current facts. We will change this page when a fact changes.
- Delivery model
- Operator-led. A person runs the work and reviews each record. There is no customer dashboard and no API today.
- Authorization
- Written, and signed by a person with authority for the named domains. We do not start without it.
- Test identity
- Our sessions declare a named user agent. You can allow it, and you can ask us to stop at any time.
- Data in a run
- Public page content, our own synthetic data, and the evidence that we record. We use no real customer data.
- Storage
- Records are stored outside the public web root. We agree the retention period and the deletion rule in writing.
- Subprocessors
- We name every provider that a run uses before the run. We agree the list with you first.
- Support
- Email support with the operator. We agree a response target in the written scope. We publish no SLA.
- Availability
- Enterprise use is conditional on our readiness gates and on the written scope. We state the current status in the agreement.
- Security
- See the security page for the deployed controls and the open work.
Fit
Where a program works, and where it does not
-
A good fit
- Many sites or locations share one journey model.
- One team can authorize a test for the whole group.
- You want the same evidence for each site.
- You accept operator-led delivery today.
-
Not a fit yet
- You need a compliance certificate before you buy.
- You need a self-service dashboard, an API, or a data feed.
- You need an uptime SLA or a contractual response time.
- You need us to make the fix on your site.
Talk to us about a group of sites.
Tell us how many sites share the journey. We reply with a written scope and the next step.