Department Implementation

One department at a time,live every six weeks.

A repeatable cycle: Discover, Design, Build, Pilot, Launch, Optimize. Marketplace templates first, custom only where the work needs it. Two departments in parallel, always.

StageWk 1Wk 2Wk 3Wk 4Wk 5Wk 6Ongoing
DiscoverDepartment Opportunity Brief approved
DesignClone Design Spec + InfoSec approval
BuildAll test scenarios pass
PilotAccuracy and adoption above thresholds
LaunchDepartment live, baseline vs. actual tracked
OptimizeNext autonomy level when criteria are met
The cycle

Six stages. Clear exit criteria.

01

Discover

Department problem statements, workflow mapping, systems and data inventory, Champion named.

Exit: Department Opportunity Brief approved

02

Design

Clone roles defined (Marketplace template first, custom only where needed), skills map, knowledge design, approval rules, InfoSec sign-off.

Exit: Clone Design Spec + InfoSec approval

03

Build

Deploy Clones, load knowledge, connect systems, build or configure skills, test against realistic scenarios.

Exit: All test scenarios pass

04

Pilot

Champion plus 3–5 users, human in the loop, daily feedback and fixes.

Exit: Accuracy and adoption above thresholds

05

Launch

Department-wide training, internal communications, schedules and channels (Slack, Teams, phone).

Exit: Department live, baseline vs. actual tracked

06

Optimize

Health monitoring, Power Rating and autonomy promotion reviews.

Exit: Next autonomy level when criteria are met

Marketplace first

Start from proven. Customize what matters.

Most departments start from Marketplace Clone templates and existing skills, then get your knowledge, your systems and your rules. We build custom skills only where the work needs it.

That keeps rollouts fast, upgrades safe and maintenance light.

Marketplace templates

Role-ready Clones for common department work.

Custom skills

Built in SkillForge for your systems and processes.

A Champion per department

The named owner for adoption.

Baseline vs. actual

Tracked from launch day.

Across departments

Clones hand work to each other.

From Month 4, workflows cross department lines: Sales to Finance for billing, HR to IT for onboarding access, Support to Product for bug reports.

Sales → Finance: closed-won deal details sent for invoicing and contract setup, no re-keying.Support → Sales: expansion signals and renewal risks flagged to the account owner with context.Sales → Finance: closed deal terms arrive ready for invoice creation and revenue schedule setup.HR → IT & Security: accepted offers trigger account, device and access requests before day one.HR → IT & Security: new hire and leaver events trigger access provisioning and removal requests.Marketing → Sales: engaged leads handed to the SDR Clone with campaign context and content viewed.Sales → Legal: deal desk requests arrive with the contract, deal size and deadline attached.Operations → Customer Support: shipment delays pushed to Support with customer impact before tickets arrive.
FAQ

Questions, answered.

Why six weeks per department?

It's long enough to design properly, pilot with real users and launch with training, and short enough that every department sees results within a quarter. Two run in parallel on the Partnership tier.

Do you build every Clone from scratch?

No. We start from Marketplace templates and existing skills, and build custom only where the work needs it. That keeps rollouts fast and maintenance light.

What does a Champion do?

A Champion is the named internal owner for adoption in their department. They shape the design, lead the pilot, answer setup questions, publish proven workflows and bring feedback back to us.

When does a department count as live?

When department-wide training is done, Clones are working in the channels your people use, and baseline versus actual is being tracked on the adoption dashboard.

Pick a department. Live in six weeks.

Book a department diagnostic and we'll map the first rollout with you.