Implementation checklist
A step-by-step checklist to stand up Pytheus and produce a defensible first baseline.
Last updated September 22, 2026
Use this checklist to take Pytheus from empty account to a baseline you can defend in a leadership conversation. Work top to bottom; later steps depend on earlier ones.
Set the foundation
Confirm your organization profile, including sector and size, so cohort comparison uses relevant peers.
Identify your internal champion and the domain owners who will supply real input. See the internal champion guide.
Decide which CAMP domains are in scope for this round. Starting narrow and accurate beats starting wide and shallow.
Build the assessment
List the capabilities in scope for each chosen domain.
Score current maturity (0–5) honestly for each capability.
Set target maturity per capability based on where you actually need to be, not where you would like to be.
Assign criticality (1 nice-to-have, 2 core, 3 compliance-required). This drives priority, so be deliberate.
Review what Pytheus produces
Confirm your Org Score, Pytheus Score, and domain scores look consistent with your inputs.
Read the initial recommendations on the Decisions surface, which derive from CAMP priority and deterministic rules.
Check cohort comparison on the Pytheus Index and read each peer delta as a performance difference, not a gap.
Priority comes from the size of the gap and how critical the capability is. If a capability you consider urgent shows low priority, your target or criticality is probably understated.
Once the baseline holds up, move to the rollout checklist to bring the rest of your team in. For context on cadence, see what to expect.