The first governed pilot

# One workflow.A clear boundary.A measured result.

Start with real work, not another isolated experiment. Choose a CRM or marketing workflow, name its business owner, and give it a clear path from context to evidence.

A focused engagement

## €10,000

12 weeks · 1 use case

- One agreed workflow and owner

- Approved context and permission setup

- Authority tests and human review paths

- Evidence and a scale-or-refine decision

We agree the scope, access prerequisites and acceptance measures before kickoff. Results depend on the workflow and its starting baseline.

The 12-week approach

## A scoped path to a decision.

Establish business value and control acceptance together. These phases describe the proposed approach; the agreed workflow determines the detailed plan.

- 01 / Weeks 1–2Scope and baselineChoose one workflow and a named business owner. Agree the inputs, systems, authority boundaries and measures of success.

- 02 / Weeks 3–5Configure and connectAdapt the domain foundation, connect approved business context, and configure permissions and approval paths.

- 03 / Weeks 6–9Test and runExercise permitted and forbidden actions, review publish-gate results, and run the workflow with agreed human oversight.

- 04 / Weeks 10–12Review the evidenceCompare results with the baseline, review exceptions and effort, and decide whether to refine, expand or stop.

Evidence before expansion

## Agree what good looks like.Then measure it.

Define the baseline and acceptance criteria with the business owner. Compare the results, review the exceptions, and make a grounded decision about the next step.

- Task completion and output quality

- Time spent doing and reviewing the work

- Correct handling of forbidden actions

- Approval and escalation outcomes

- Recorded usage, cost and accounting gaps

- Business-owner acceptance

Before we start

## A few useful questions.

## What should we bring to the first conversation?

A workflow the team does today, the systems and data it uses, an accountable business owner, and a view of where a person must approve. We can help define the baseline and scope together.

## Do we need to know exactly which agent to build?

No. Explore the use case catalog for ideas, or start with a workflow and the outcome you want. For teams still choosing where to begin, the Agentic Readiness Blueprint covers workflow mapping, opportunity and risk review, and an initial rollout plan.

## What happens after the pilot?

Review the evidence with the business owner and decide whether to refine, expand or stop. A successful pilot can leave reusable context, permission patterns, tests and review responsibilities for the next team or business unit.

Beyond the first workflow

## Expand domain by domain.

Reuse the foundation that works. Adapt the context and governance to the next team, market or business unit.

### Agentic Readiness Blueprint

Choose a starting point through workflow mapping, opportunity and risk review, and an initial rollout plan.

### Agent Builder Implementation

Configure the platform, context sources, agent templates and governance process for the first production workflows.

### Center of Agentic Program

Develop a rollout and knowledge-governance model across domains, markets and business units.

The next step

## Bring one workflow to the conversation.

Tell us where agents could help, and where a person needs to stay in control. No account needed.

Source: https://centerofagentic.com/pilot

## Related pages

- [Discuss a pilot](https://centerofagentic.com/contact?intent=pilot)
- [Contact the CoA team](https://centerofagentic.com/contact?intent=pilot)
- [Prepare a use case brief](https://centerofagentic.com/use-cases)