Clone Solutions
Template

6-Month Business Review

A midpoint executive review of value delivered, autonomy by department and adoption, ending in a reset roadmap for months 7–12.

What this is for

Six months in, the program has moved from proving to scaling. This review steps back from monthly steering to answer the bigger questions: is the value adding up across departments, where are Clones trusted to do more, where is adoption weak, and is the plan for the second half still right? It ends with a reset roadmap for the agentic phase (Months 7–9) and self-sufficiency (Months 10–12).

When to use it

At the end of Month 6, in place of that month's steering meeting. Use the same structure for the Month 9 quarterly business review, with a heavier focus on orchestration and the Center of Excellence.

Who's involved

  • Executive sponsor chairs.
  • Steering committee and all business owners of live departments attend.
  • InfoSec lead presents the governance view.
  • Solutions Partner prepares and facilitates.
  • CoE lead (or the person who will become it) attends to start owning the second half.

How to fill it in

  1. Roll up results across every live department against the Year-1 Success Metrics (section 2).
  2. Estimate value using the client's own cost rates and conventions, agreed with Finance. Show your method.
  3. Map autonomy level by department and workflow (section 3).
  4. Review adoption and Champion health (section 4) and call out departments below target.
  5. Review the governance record with InfoSec (section 5).
  6. Re-score the remaining opportunities with what you now know, and reset the roadmap (section 6).
  7. Agree the decisions in section 7 and record them in the portal.

The template

1. Summary

FieldEntry
Review date
Departments live / planned by Day 1805 / 5
Clones live14
Workflows at Execute with approval or higher9 of 22 (41%)
Governance incidents above agreed severity0
Champion coverage in live departments100%
Overall assessmentOn track for 7 departments by Day 365

2. Value delivered

DepartmentMetricBaselineMonth 6ChangeYear-1 targetOn track?
SupportFirst-response time9.5 hrs1.8 hrs−81%3 hrsAhead
FinanceDays to close96−3 days5On track
HRTime to provision new hire4 days3 days−1 day1 dayBehind

Value estimate (client's own method, agreed with Finance):

Value typeHow measuredMonth 1–6 totalAnnualized run rate
Hours given backTime study × volume
Cost avoidedClient's loaded cost rates; overtime and contractor spend avoided
Revenue protected or gainedE.g. faster lead response, fewer churned accounts
Risk reducedE.g. fewer late filings, audit findings

3. Autonomy map

DepartmentWorkflowAssistRecommendExecute w/ approvalExecute within limitsOrchestrate
SupportTicket routing●
SupportRefund recommendations●
FinanceAP invoice coding●

Promotions in the last quarter: _ approved, declined, demoted. Planned for next quarter: _

4. Adoption and Champions

DepartmentWeekly active %Avg Power RatingTrendChampion healthAction if below target
HR48%FlatChampion lost time to hiring pushManager to restore 3 hrs/week; office hours relaunched

5. Governance record

ItemMonths 1–6Comment
Connections approved
Audit log reviews completed
Overrides (count and rate)
Incidents by severity
Risk register: open / closed
Skill version changes through change control
Policy changes

InfoSec view (2–3 sentences):

6. Roadmap reset

Opportunity / departmentOriginal planNew scoreProposed timingChange
Procurement intakeMonth 53.6Month 8Moved later
Cross-department: Sales → Finance billing handoffNot planned4.4Month 7Added

Second-half priorities:

  • Proven workflows to move to Execute within limits:
  • Orchestration candidates for Commander:
  • Customer-facing Clones (support, intake, phone, SMS):
  • Integration work (see Integration Architecture):
  • Center of Excellence formation by Month 9:
  • Audit evidence needed for upcoming client audits:

7. Decisions

#DecisionRecommendationDecisionOwner
1Approve reset roadmap
2Name CoE lead
3Customer-facing Clone scope

Good looks like

  • Value uses the client's own numbers and method, signed off by Finance, not vendor estimates.
  • Departments behind target are named with a specific fix, not averaged away.
  • The autonomy map shows where people are still in the loop and why that is right for now.
  • The roadmap actually changes. Six months of evidence should move priorities.
  • The CoE lead is named here. Leaving it to Month 9 makes self-sufficiency late.
  • Common mistake: celebrating totals. Leaders need the uneven picture to make good second-half calls.

How Clone helps

The Project Clone compiles results, adoption and autonomy history across departments from the portal and drafts the review. The Solutions Architect Clone re-scores remaining opportunities with updated data from the Systems & Workflow Map. The GRC Clone prepares the governance record. The portal stores the reset roadmap and moves the program into the agentic stage once it is approved.

Sign-off

RoleNameDateDecision
Executive sponsorReset roadmap approved / changes requested
Finance leadValue method confirmed
InfoSec leadGovernance record confirmed
Solutions PartnerIssued