Keep the evidence attached
Stop reconstructing why a recommendation was made when a stakeholder challenges it weeks later — the source stays linked to the finding.
Capture client reality, review AI-assisted findings, create defensible recommendations and deliver governed outputs in one workspace.
Define the brief, stakeholders, evidence policy and sign-off path before any evidence lands.
Receive files, walkthroughs, questions, recordings and validated system evidence — with coverage and gaps visible as you go.
Validate process maps, systems, people, problems, confidence and gaps. AI prepares the structure; you own the conclusion.
Rank opportunities, state what to skip and define the first move — each carrying its evidence and reasoning.
Generate client-ready documents, summaries and controlled shares from the same evidence base.
Design, launch and monitor where the engagement includes implementation — without losing the chain of custody.
Stop reconstructing why a recommendation was made when a stakeholder challenges it weeks later — the source stays linked to the finding.
Templates and methodology speed the engagement; the client's own evidence still controls the conclusion.
AI organises, retrieves and drafts. Practitioners review, edit, approve and sign off.
Guided intake, questions, portals and shared summaries — without exposing analyst-grade complexity.
Here is what steps 02 through 05 look like on an actual engagement, with Northstar Services standing in for the client in front of you.
Sarah's guided intake means you are not the one chasing files from Northstar's finance team — she flags what is missing as it surfaces.
The finance lead uploads the approval policy; Sarah flags that no one has recorded how an invoice actually moves once it leaves the inbox.
The recording that fills that gap gets transcribed, timestamped and linked to the process step it evidences, so you or the client can jump straight to the moment a finding is based on instead of re-watching 18 minutes of video before a call.
From that evidence, you build the current-state map. Process mapping runs by scope today, and the unified Evidence Ledger view is limited availability — but every finding you draw from the evidence still carries its source, plus a read on risk and feasibility, because that is how the problem register works underneath it. Rank, skip and first move inherit that evidence automatically, instead of you reconstructing it in a memo afterward.
The engagement ends with a signed Trail Map report, exported with the evidence trail intact and shared under co-branding — limited availability, confirmed at setup — a client-ready deliverable you do not have to defend from memory when the client's CFO asks how you know.
This is what one analyst's week looks like across a live caseload. Running several clients side by side in one workspace is limited availability, the same as the Evidence Ledger — volume is confirmed before activation.
| Day | What happens | What does the work |
|---|---|---|
| Monday | Intake opens on a new client. Sarah asks the scoped questions while the evidence room fills with the signed engagement letter and last quarter's AP export. | Sarah guided intake, Evidence room |
| Midweek | An analyst clears the coverage gaps Sarah flagged Monday — usually a missing walkthrough or a system export that never arrived. | Evidence room coverage, Walkthroughs & recordings |
| Thursday | Opportunity ranking runs live on a call with the client, value and risk scored in front of them, and the skip list gets its reasons attached before the call ends. | Problems & opportunities, ROI, skip list & first move |
| Friday | The Trail Map report goes through internal review, then out for client signature, with the evidence trail intact. | Deliverables & client-ready outputs |
Most practices run this work across four or five tools that do not share a record. The point is not that those tools are bad — it is that the evidence chain breaks every time work moves between them.
We confirm workspace volume, user roles, usage, support and any co-branding requirements before activation — so what you request is what you can actually run.