Push live status to the team

Claude reads the current programme data, writes a concise status update, and posts it straight to your #programme-status Slack channel.

AI Programme Assistant

Ask anything — Claude reasons across the programme data in real time.

Predictive Risk Engine

Risks the AI surfaced that are not yet in the register — found in the white space between workstreams.

AI Inbox Triage

Claude reads your unread email, summarises each one, suggests what to do, and drafts replies — you create the draft in Gmail with one click.

Delivery Analytics — Azure DevOps

Starts at programme level. The engine reads your live work items, works out how your board is actually organised — however many levels deep it goes — and computes the delivery view in code: velocity trend, story & build completion, open P1 defects and ADO hygiene. Open any workstream to see the same figures for the work beneath it. Claude narrates the figures it is handed; it is never given the work items.

Sample delivery data (demo setup)

Populates Azure DevOps with ~38 work items — user stories, bugs, tasks and builds — across four markets (APAC · LATAM · NA · EU) as Area Paths, over seven sprints (five completed · current · future) with story points, so the per-market analytics above are real. Re-seeding? Clear first to avoid duplicates.

AI Cutover & Deployment Commander

Go-live readiness

Pick a market — cutover is a per-market event. A weighted go-live confidence is computed from that market's live ADO defects, test progress, risk posture and milestone health, with a decisive go / no-go call. Rollback is shown as readiness states, not a fabricated probability.

Market

Plan & Replan

AI proposes the shape. Code computes the dates.

Describe a programme in your own words and the AI drafts its shape — workstreams, phases, how long each takes and what waits for what. Every date is then worked back from your go-live by the scheduler, never supplied by the model. When a go-live moves, replanning recomputes every date and shows you each change, and why, before anything is saved.

Draft a plan from a description

A paragraph, a goal and a date, or just a list of deliverables. Uses your organisation's own Anthropic key.

Link or import a plan from Excel

Use the plan template, or your own plan in your own format. You will see exactly what was read — and can correct any column — before anything is saved.

Replan a programme against a new go-live

Pick a programme and the date it now has to land on. You will see every date that would move, by how much, and the dependency that fixed it. Nothing changes until you apply.

Resourcing · Utilisation and Capacity

Resource Utilisation & Capacity

Two questions in one view: are people correctly loaded — who is booked beyond their hours, whose capacity is sitting idle — and is the work left achievable with the people assigned, at the rate each workstream is actually going. Every figure is computed in code from the resourcing and delivery records; the AI writes the narrative only. Demo runs on embedded fictional data shaped like a real resourcing export.

Can the work left be finished by the people assigned?

Each workstream's own velocity against the work remaining and the sprints left. Needed is the rate the remaining sprints demand; where that is above actual velocity, the workstream cannot land on its current dates without more people or less scope.

Utilisation by person

Hours booked against hours available this sprint. Red is booked beyond capacity; amber is capacity nobody is using.

By workstream

By role

Where a role is over-subscribed in one workstream and idle in another, that is a reallocation rather than a hire.

Financials · Budget vs Actuals vs Forecast

Financial Command Centre

One view across both finance sources: period spend (planned vs actual, CapEx/OpEx — the ServiceNow lens) and the market money picture (budget, committed, actuals, balance — the leadership workbook lens). Every figure on this page is computed in code from the underlying records; the AI writes the narrative only. Demo runs on embedded fictional data shaped exactly like both production sources.

Planned vs Actual · cumulative spend (S-curve)

Solid orange = actuals to date · dotted orange = run-rate forecast · navy = phased plan · vertical line = current period.

Markets · budget / committed / actuals / balance

Click a market row to drill in. RAG is computed: red = run-rate forecast exceeds budget · amber = runway or contract-coverage flag.

Signals · computed early warnings

ServiceNow · System of Record

Closed loop with ServiceNow

Projects live in ServiceNow — the PMO's system of record. The app reads them live over OAuth, and publishes status back: it computes the five RAG categories from real programme data, Claude writes the narrative, it writes that onto the record, and pings the PM on Slack. Authenticated exactly as we'd connect to a production instance — registered OAuth app, no stored password in the calls.

AI Reporting Automation

Pick a deck type, select markets, choose extras — generate a branded slide deck per market or as a full programme pack. Download or save to Gmail.

Deck type

Markets to include

Each selected market generates its own set of slides — Project Overview (with its milestones), Weekly Summary and workstream detail. Markets are never combined on a slide. De-select any market not relevant for this audience.

Include (optional)

Programme Setup

Configure your programme

Point at your own plan, map your columns once, and set how reporting works — no code, no developer. The dashboard adapts to your configuration.

① Connect a data source & map your columns

Have a project schedule? Import it on Plan & Replan. This section is for a sheet with one row per workstream or RAID item.

Every plan names its columns differently. Instead of rebuilding the tool for each one, you map your columns to the fields needs — once, on this screen. then reads your live plan through that mapping, and everything downstream (RAG, risk sizing, decks) keeps working unchanged.

Data source

1Upload your plan

No file to hand? Load a sample sheet · or paste column headers

Map your board to

Connect your tools

Connect your organisation's own tools. Your keys are encrypted at rest and used only for your workspace — they're never shown back to anyone or shared across organisations.

Activity log

Every change made in your organisation — who made it and when. Visible to your organisation's admins only, and never to anyone outside your organisation. Credentials are never recorded: a connection entry says what was connected, never the key.

People

Everyone who can sign in to your workspace, and the roles they hold. Invite a colleague and gives you a one-time link to send them — they set their own password, and nobody but your organisation's admins can see or change this list. Viewers are free and do not count toward your seat limit.

Your plan

What your organisation is on, and what happens next. Every figure here is one the server computed from your own record — the days left and the dates are the same ones the product itself reads, so this screen and what does can never disagree.

Your data

Download everything your organisation holds in : programmes, plans, risks, people and the activity log. It is one JSON file, a format made for other software rather than for reading, and it works even when the workspace is read-only. Stored keys and passwords are not included.

Your invoices

’s record of what was agreed with you — the number, the amount and the dates. Visible to your organisation’s admins only. does not take payment through this product, so nothing here is a request to pay.

AI usage

What the AI has cost your organisation — every call, which capability made it, and which of your people made it. Each figure is a total the server computed from rows written as the calls happened; no model is involved in this screen. Visible to your organisation's admins only. No prompt, no reply and no programme content is ever recorded.

AI spend across every organisation

What each customer costs to serve, and whether their people are actually using it. Counts only — no individual appears on this screen, by design, because this view reads across every customer. Licensed is people who can sign in; Active is people who did something in the window. (this deployment) is this installation's own spend: the demo login and the scheduled runs, on this deployment's own key, never added into a customer's figure.

Accounts and invite codes

Nobody can create an account without a code from here. Each code works once, lasts 14 days, and is shown only at the moment you make it. A new account gets a 30-day trial for up to 10 people. The trial dates are recorded, not yet enforced.

What customers owe

Each customer's plan, what they agreed to pay, the seats they hold against the band they bought, and the invoices you raised in your accounting tool. records invoices — it does not raise them, take payments or produce invoice documents. Nothing here reaches a customer, and nothing automatic acts on an unpaid invoice.

Demo logins · what they did

Each sign-in and each action by a demo login, so a login you hand to someone can be looked at later. Only who, when and which action are recorded, never what was typed or shown. Your own operator login is not recorded here, and neither is any customer account.

Money · your financial year

How your organisation divides its year into periods. then shows a programme's money in the periods your finance team uses — calendar months, 4-4-5 weeks, 13 four-week periods, or your own period table.

Money · currency and exchange rates

The currency your organisation reports in. Each programme keeps the currency its money arrived in; converts it at rates the European Central Bank publishes or your finance team enters — never at a rate an AI produced.

Money · who sees and changes it

One of three presets for your whole organisation, chosen by your admin. What a role may not see is removed by the server before it reaches anyone's screen, and a file carrying money its sender may not change is saved without that money.

Money · closed periods, dimensions and internal staff

Whether a closed period locks, the lists your money is broken down by, and whether each programme's cost includes your own staff.

③ Connect your tools

Select which tools are active for this programme. The AI reads from and writes to each connected tool automatically.