Phase 2: Adoption

Phase 2 is where your organization finds the use cases worth deploying, and takes them into production in each department. It begins once Phase 1: Implementation is complete—kick-off, security walkthrough, admin walkthrough and platform walkthrough—and the platform is ready to use.

Where use cases come from

Use cases reach production from two directions:

• Picked from what already exists. Intric’s Solutions are processes Intric has already delivered for municipalities and public authorities, such as contract review, meeting transcription and redaction before public release. The community assistants in the Library are assistants other organizations have built and shared. Both give a department a proven starting point instead of a blank page.
• Identified by your AI Ambassadors. The Ambassadors taking part in the pilot know where their own work is slow, repetitive or error-prone. In the AI Lab they turn that knowledge into use cases specific to your organization.

Most departments end up with a mix: one or two proven solutions for early value, and their own use cases for what is unique to them.

Three tracks

Phase 2 is built around one main track, Pilot to production, which runs from start to finish. Depending on the scope of the pilot, you also establish an AI Council, an AI Lab, or both, running in parallel with it:

Track	What it covers	Rhythm
Track 1: Pilot to production	One to five assistants built with Intric and taken into daily use	Throughout the pilot
Track 2: The AI Council	Governance, sensitive data, integrations and progress	Every 1–2 weeks, if the scope calls for it
Track 3: The AI Lab	Ambassadors learning, finding use cases and building	Every 2–4 weeks, if the scope calls for it

Throughout Phase 2, as in Phase 1, a check-in every week or every two weeks goes through the status of the work with Intric.

Why three tracks

Adoption stalls in three different places, and each track is there to keep one of them moving:

• Without dedicated delivery, a promising pilot never becomes something people use every day. Pilot to production takes a small number of assistants all the way through integration, compliance and handover, which is why it drives the phase.
• Without governance, use cases stop at the questions nobody owns: who maintains an assistant, whether it may touch sensitive data, how it connects to your systems. Where the pilot raises those questions, the AI Council answers them before a use case reaches them.
• Without hands-on learning, people never get good enough at AI to see where it fits in their own work. Where the pilot is meant to build that competence, the AI Lab does it, and use cases come out of it.

Running the tracks in parallel means none of them waits for the others. The AI Lab can start on open, public information while the AI Council is still preparing the path to more sensitive data, and what the Lab finds feeds directly into what Pilot to production builds.

Alongside the tracks, Intric offers a toolbox of workshops, PT Sessions and materials you can draw on whenever your organization needs them.

How each use case moves from idea to production

All three tracks are built around the same iterative cycle—the Lifecycle of an Assistant. Every use case follows four steps. Once the cycle is complete, you take the next step up the Staircase and repeat at a higher level.

1. Find use cases — Map processes and identify where AI adds the most value
2. Build — Create an assistant adapted to your context and needs
3. Test & iterate — Evaluate, gather feedback, and improve
4. Roll out — Share in the library so others can use and be inspired

The key principle: start small and concrete. Organizations that try to solve entire processes at once consistently stall. Those that build methodically, step by step, go furthest.

In practice, this means:

• Begin with something small and concrete—not with redesigning an entire process at once
• Celebrate early wins and communicate them actively upward
• Use each result as the case for the next investment

Strategic meetings

Alongside the tracks, a recurring strategic meeting brings the project sponsor or owner together with the admin group and Intric. The cadence is up to you, but Intric suggests meeting every month or every two months at first. The purpose is to zoom out and take stock:

• Where are we on the Staircase?
• What’s working, and what isn’t?
• What are the next priorities?
• What’s coming in the Intric product roadmap?

The first strategic meeting is scheduled at contract signing.