The loop is not a project plan with an end. It is a rhythm. A new team starts with an assessment, equips the cheapest gaps first, and keeps engaging while it improves. The same loop is repeated for each domain, and several domains can be in different phases at once.

1. Assess

See yourself as agents see you: what they find, what they get wrong and what they fail to do.

Look at yourself the way agents do, using the same tools they use. Test with real prompts, read your own logs and score each domain against the Maturity Model. Write down what you find, including what you could not measure.

How often: A full baseline once, then every quarter. A light check of the core metrics every month.

DomainAssess in practice
DiscoverTest which agents reach you and which get blocked. List the sources agents use for your sector and check them.
DescribeCompare your facts across the site, markup, feeds and external sources. Note every mismatch.
ConverseAsk the questions customers ask, through the channels agents use. Record what comes back and how long it takes.
TransactWalk each customer task as an agent would. Note where a person must step in.
TrustReview who can reach what, what logs exist, and whether a policy is written and enforced.
MeasureEstablish the baseline for each core metric and note which ones you cannot yet count.

2. Equip

Give agents what they need: access, facts, answers and actions, in the standards they speak.

Close the gaps found in assessment. Start with the cheapest fixes that unlock the most: access, facts and answers come before actions. Use open standards, and give each project an owner and a finish date.

How often: Continuous, in projects of four to twelve weeks per domain, ordered by the assessment.

DomainEquip in practice
DiscoverFix access rules, publish the sitemap and an agent guide, correct listings and register agent-facing services.
DescribeCreate the fact register, add structured data, publish feeds and write policies in plain language.
ConverseStand up the question endpoint, connect live data and publish the handoff route.
TransactExpose the first actions with limits, then add checkout, changes and disputes.
TrustWrite the agent policy, add scoped permissions, signature verification and logging.
MeasureClassify agent traffic, add interaction logging, build the prompt panel and the monthly report.

3. Engage

Answer, transact and, increasingly, reach out: run the relationship day to day.

Run the relationship. Answer questions, complete transactions, hand off to people and keep promises. As the practice matures, begin reaching out to the agents and people you want to serve, under the same rules of honesty and consent.

How often: Always on. Daily operations, with a weekly review of exceptions.

DomainEngage in practice
DiscoverKeep listings and registries current, and respond to blocks and crawl errors the day they occur.
DescribeUpdate the source of truth the moment something changes, and republish everywhere.
ConverseStaff the handoff route, review unanswered questions and keep answers current.
TransactProcess agent-created orders and requests as you do any others, and resolve disputes.
TrustVerify agents on arrival, enforce limits and respond to abuse and incidents.
MeasureCollect the data continuously, and flag anomalies when they happen.

4. Improve

Measure outcomes, fix what failed and raise the level, one domain at a time.

Close the loop. Review the core metrics, find the largest cause of failed tasks, fix it and test again. Once a year, re-score maturity, drop what no longer matters and choose the next level to reach in each domain.

How often: A monthly review of metrics and failures. An annual re-assessment of maturity and a review of the plan.

DomainImprove in practice
DiscoverReview which agents and sources brought outcomes, and adjust access and listings.
DescribeRetire stale facts, widen markup coverage and add the formats agents have begun to use.
ConverseTurn the most common failed questions into better answers or new endpoints.
TransactFix the top causes of failed actions, then extend the actions available.
TrustReview incidents and near misses, update the policy and raise the verification bar.
MeasureRefine definitions only with a version change, and compare against peers in the Index.