Founding Journey Pilot
One site. One journey. $199.
This page states the exact scope, the deliverables, the exclusions, the authorization step, and the purchase steps. Read it before you email us.
You pay before the test starts. This site holds no checkout.
Start a $199 pilotSee an example record
Our test sessions declare AgentJourneyLab/0.1. Site owners can stop a public test: read the research boundary or write to research@agentjourneylab.com.
Scope
Scope
The baseline is three attempts with the primary configuration and one attempt with the secondary configuration.
The written scope names the first-delivery date, the four weekly monitoring dates, and the retest window. You read these dates before you pay.
| Item | Price | Basis | What it covers |
|---|---|---|---|
| Founding Journey Pilot | $199 | one time, one site, one journey |
|
| Journey Monitoring | $199 | per site, each month, optional |
|
| Multi-site Program | Scoped | after a pilot, per agreement |
|
Pilot facts
Pilot facts
These are the facts of the $199 pilot. Read them before you email us.
| Baseline protocol | The primary browser-agent configuration runs three times, each time in a fresh context. The secondary browser-agent configuration runs one time for breadth. We report completion as n of 3. |
|---|---|
| Identity | The written scope and every record name the provider, the model alias, the runner version, the prompt version, the browser version, the viewport, the locale, the timezone, the date, and the network vantage. We do not publish a provider as available before we approve it and enable it. |
| Schedule | The pilot includes four dated weekly monitoring records across one month. The written scope names the first-delivery date, the four monitoring dates, and the retest window. You read these dates before you pay. This is a written scope, not a general service level agreement. |
| Retests | The pilot includes up to two out-of-cycle retests after you fix an issue. |
| Clean outcome | A journey that completes still gives you a dated completion record. It carries the checkpoint evidence, the tested conditions, the limits, and a reference state for the weekly monitoring. |
| Boundary | A result applies only to the named configurations and the named dates. It is not a certificate and it is not a statement about every agent. |
Either outcome
You receive a useful record in either outcome
A record is useful when the journey stops and when the journey completes. These are the six results that a pilot can give you.
Reproduced stop
The stop repeats across the attempts. The record shows each checkpoint state and the observation at the stop.
Intermittent result
The journey completes in some attempts. The record gives n of 3 and the difference between the attempts.
Agent-specific variation
The two configurations disagree. The record labels the disagreement. It does not name your site as the cause.
Inconclusive result
The evidence disagrees. The record says Inconclusive and states what is necessary to decide it.
Scope boundary
The journey reaches a boundary that we agreed, for example a form field or a challenge page. The record states the boundary and stops there.
Consistent completion
The journey completes in every attempt. The record gives the completion evidence, the tested conditions, the limits, and a reference state for the weekly monitoring.
Each record names a likely fix owner and a verification step or a next step. A record does not include remediation work. We do not promise that a production change works before you ship it and a production retest observes the change. Not every record contains a fix.
Deliverables
Deliverables
Three primary attempts and one secondary attempt
Completion is reported as n of 3. The secondary configuration adds one breadth attempt.
One dated evidence record
Each checkpoint, the exact stop, and the observation that decided it.
A likely fix owner
Content, front end, platform, or policy. A likely owner is not a verdict.
A self-check
The steps that let your team repeat the stop in less than one minute.
Four dated weekly records
One dated record for each weekly run across one month, with what changed.
Up to two retest records
We repeat the journey after you fix an issue.
Exclusions
Exclusions
- Code changes on your site.
- A security test or a load test.
- A certificate, a score, or a badge.
- Any action outside the written scope.
- Use of real customer data.
- Publication of your results.
Authorization
Authorization
You confirm
- You hold authority for the domain.
- You accept the declared journey and the completion criterion.
- You state the limits for any data entry.
We confirm
- We keep to the written scope.
- We take no consequential action outside it.
- We keep your results private.
How you buy
How you buy
- You send the detailsEmail the site and the journey that you want us to test.
- We send a written scopeWe reply with the exact scope, the boundary, and payment instructions.
- You approve and payYou confirm the scope in writing, you confirm your authority for the domain, and you pay $199.
- Testing startsWe run the baseline attempts and we send the dated record.
No checkout exists on this site. We send payment instructions with the written scope.
Monitoring then runs for one month, with one dated record for each weekly run.
Optional renewal
Optional renewal
Monitoring after the pilot costs $199 per site each month. Stop it by email. It ends at the end of the paid month.
Next step