1
Name every field
Use visible labels, autocomplete tokens, input types, required state, and instructions that remain available while typing.
Signup and lead generation
Let an agent start the right signup—without losing control.
Design signup and lead forms that agents can identify, fill with synthetic data, validate, and hand back with a clear next step.
Signup is often the first measurable conversion an agent attempts. The happy path is not enough: the agent must distinguish account creation from a newsletter, understand required fields, recover from validation, and know whether a submission happened. Keep sensitive or consequential steps behind clear authorization, and give both the person and the agent an honest receipt.
2
Expose the submit state
Use a real button with a specific accessible name, pending state, duplicate protection, and an explicit success or failure result.
3
Separate preview from commit
Let a test journey reach review with synthetic data; require intentional approval before creating an account or sending a lead.
4
Return a receipt
Report whether the request was accepted, what happens next, and a reference or recovery route without leaking private data.
Fields
Labels, descriptions, formats, autocomplete, errors, and focus are programmatically associated.
Boundaries
The agent can stop at a review screen and cannot silently submit a real record.
Outcome
Success, failure, duplicate, and uncertain network states are distinct and recoverable.
Evidence loop
Find the first failure. Fix the task. Verify the same task again.
A score is a summary. The useful artifact is the URL, control, state, assertion, and safe stopping point your team can hand to a coding agent. Scan a public URL to create that baseline, then rerun the journey after each fix.
Create your baselineQuestions teams ask first
Should I let an agent create an account automatically?
Only when the user, target, authorization, and consequence are clear. Start with a safe preview or review step and require explicit approval for identity, payment, or externally visible effects.
What makes a lead form agent-friendly?
Stable labels, clear consent language, useful validation, a distinct submit action, duplicate prevention, and a receipt that says whether the lead was accepted.
Can a public scan verify signup conversion?
No. A public diagnostic can observe form and safety signals, but it should not submit real leads or prove a private account journey without an authorized fixture.