How It Works / Activation
Layer II — Activation

The agents exist.
Making them work in
your environment is the job.

We select the right marketplace agents for your specific environment — chosen by your Readiness Assessment — and implement them correctly from connector to go-live.

Milestone-based fees 12–16 weeks (Standard Track) PRISM-scoped Adoption runs in parallel
What Implementation Actually Means

Every marketplace agent
requires real technical work.
Here's what that work is.

The Moveworks AI Agent Marketplace has hundreds of pre-built agents. They look like instant value. In practice, every agent requires a real implementation sequence before it produces anything for your employees. This isn't a limitation of the platform — it's the nature of enterprise software integration.

The partner who skips this reality doesn't discover it until you're mid-program. We measure it upfront with PRISM, scope it explicitly, and price it honestly before you sign anything.

The marketplace agents exist. Connector authentication, system permissions, schema validation, exception handling, UAT — that is the implementation. That is what you are paying for.

1
Connector Authentication
OAuth flows, service account setup, API scope configuration for every system in scope. Creating service accounts with specific permission scopes, generating and validating tokens, confirming Moveworks can reach each system in your environment.
2
Permission Grants in Source Systems
Workday ISU configuration. Okta API scopes. Salesforce connected app setup. SharePoint Azure app registration. ServiceNow role configuration. Every system has been integrated before. Every system has its own specifics in your environment.
3
Schema Validation
Marketplace agent templates are built to a standard schema. Your data is not standard. We map your actual field structures, identify schema divergences — including custom fields and renamed fields common in enterprise deployments — and configure the transformations required.
4
Exception Handling
Every failure mode identified in your PRISM score gets a defined resolution path. Timeouts, missing records, auth failures, partial writes, escalation triggers. We build the exception logic, not just the happy path — because the happy path is 20% of the work.
5
UAT & Go-Live
Every agent is validated in a test environment against your real data before going to production. We do not go live until the agent performs correctly across its full expected input range, including edge cases identified in PRISM scoring.
Two Engagement Tracks

Your Readiness Assessment
determines the right track.
PRISM prices it honestly.

Recommended First Track
Standard Track
Fixed price 12–16 weeks Up to 10 agents
Up to ten marketplace agents, selected by your Readiness Assessment for your highest-impact, implementation-ready use cases. Configured, tested, and launched in your environment. Fixed price based on your PRISM scorecard. Milestone-based payment — each phase approved before the next begins.
Agent selection driven entirely by your PRISM scorecard — not a preset catalog
Adoption workstream runs in parallel throughout the build
Milestone 1: Connector authentication complete. Milestone 2: Schema validated. Milestone 3: UAT passed. Milestone 4: Go-live.
Full documentation and knowledge transfer at go-live
Bespoke Scope
Custom Track
PRISM-priced Timeline scoped per engagement
Any scope — marketplace agents, custom-built workflows, or both. Every item PRISM-scored before it's priced. Same delivery standards and milestone structure as the Standard Track. For organizations with specific requirements that extend beyond the marketplace catalog, or programs requiring more than ten agents in Phase 1.
Priced per Workflow Complexity Unit (WCU) from the PRISM scorecard
Includes custom workflow development where marketplace agents don't cover the use case
Timeline and milestones scoped in the SOW based on total WCU count
Same adoption workstream, same UAT standard, same go-live process
Adoption Runs in Parallel

A workflow nobody uses
produces zero ROI.

Throughout Activation, we run the adoption workstream in parallel with the technical build. Adoption isn't a go-live activity — it's a design decision made in week one. By the time agents go live, your employees are expecting them, your managers are briefed, and your communication plan has been executed.

The 67% first-month adoption rate we achieved with Meridian Financial wasn't an accident. It was the result of an adoption architecture built from the first week of the engagement — not the last.

Week 1
Stakeholder mapping and communication plan
Who needs to know, what they need to know, when they need to know it. Built alongside connector authentication.
Weeks 2–8
Manager enablement and department briefings
Managers brief their teams on what's coming. Runs in parallel with schema validation and exception handling.
Week before go-live
Go-live readiness check and employee FAQ
Employee-facing FAQ published to your intranet. Support channel standing by for the go-live week.
Go-live week
Phased rollout and adoption monitoring
Agents go live by department or use case. Usage monitored daily in the first two weeks. Adjustments made in real time.
$
Pricing

Standard Track pricing is determined by the PRISM scorecard produced in your Readiness Assessment. The scorecard tells us exactly what we're building and why. You see the score, you see the math, you approve the scope before any work begins. Milestone-based payment — you approve each milestone before the next phase begins.

Start with AIRO to scope your Activation

Ready to build a
live program?

AIRO shows you which agents are right for your environment and what track is appropriate for your scope. Four minutes, free, no commitment.

Start with AIRO →

Free · 4 minutes · No email required

Start with the Readiness Assessment →