Mandates

Start with one useful mandate.

One sponsor. One deliverable. One clear initial duration.

Pericles Systems is organised around a small number of entry points. Each starts with one sponsor, one deliverable, and a clear initial duration.

Clarify

Use Clarify when the first move is still under-structured.

When useful
Execution is slow, unclear, or fragmented.
First deliverable
A sponsor-owned diagnostic, 30/60/90 priorities, and an initial decision path.
Ideal sponsor
CEO / COO / GM
Typical duration
2–4 weeks

When useful
Leadership needs to revisit direction, prioritisation, or sequencing.
First deliverable
An executable roadmap, decision scenarios, and operating implications.
Ideal sponsor
CEO / GM / CFO
Typical duration
6–10 weeks

When useful
AI interest is real, but readiness and use-case order are unclear.
First deliverable
Prioritised use cases, prerequisites, governance, and a first implementation path.
Ideal sponsor
CEO / BU lead / transformation lead
Typical duration
3–6 weeks

Build

Use Build when the first system needs to be designed and delivered, not just scoped.

When useful
One first system or internal tool needs to be designed and delivered.
First deliverable
A working pilot, operating logic, and a rollout path.
Ideal sponsor
COO / operations lead / transformation owner
Typical duration
4-10 weeks

Typical build work stays close to delivery: tools, workflow logic, dashboards, and control layers that teams can actually use.

workflow systems and handoff logic

internal dashboards and decision surfaces

operating tools for live teams

AI-enabled internal systems

governance routines and control layers

reusable foundations for later delivery

Continue

Use Continue when the first system is live but sponsor control still needs active support.

When useful
Leadership needs continuity between strategy, prioritisation, and delivery.
What it includes
Sponsor cadence, governance, sequencing, and execution oversight.
Ideal sponsor
CEO / GM / CFO / COO
Format
Monthly retainer

Selection principles

Three rules keep the first move proportionate, sponsor-backed, and buildable.

Choose by bottleneck, not trend language.

Name one sponsor before approving scope.

Start with one deliverable and one clear initial duration.

Diagnostic call

Book one call to define the first move.

Use the call to decide: proceed, reframe, or pause.