Platform

One Platform From Discovery to Impact

Understand the client’s business, compare proposed changes, manage delivery and track results. Your team works from shared evidence in an environment dedicated to the client.

Request a demo

Simulations

Corrigan Freight · Working copy of 14 Oct

New simulation

Search all changesSort by: Estimated impact

All changesPromisingNeeds workRolling out

Hold disputes until the packet is completeProcess redesign

Simulated recovery rises from 56.2% to 62.9% across 18 months of disputes.

Rolling out4

Check packets as they arriveAutomation

In replay, flags 9 in 10 incomplete packets. Estimated saving: 22 hours a week.

Promising3

Move disputes into the ERP moduleNew software

Simulated recovery rises 2.1 points. Three carriers’ files fail to import.

Needs work2

Merge the two AP queuesTeam change

In simulation, removes 802 duplicate matches but delays close by two days.

Not recommended3

Pay carriers on proof of deliveryPolicy change

Projects 64% fewer early payments. Two carrier contracts need new terms.

With client5

Agent drafts dispute packetsAgent

Drafts 7 in 10 packets complete on the first pass. A reviewer checks each.

Running2

From Discovery to Impact

Keep the evidence, decisions and delivery connected throughout the engagement.

Discovery

Understand How Your Client Works

Turn connected systems, documents and interviews into a shared map of the client’s business, with sources your team can review.

Connected Sources. Read-only connections to warehouses, file stores and business apps, granted by the client and scoped to the engagement.
System Map. See the systems, datasets and data flows covered by the engagement, and how they connect.
Processes as They Run. See each process as it is written, as people describe it and as the data shows it actually runs.

Learn more about Discovery

Corrigan Freight/System mapMapped in 3 h 40 min

Systems and dataProcesses

Dispute records
Invoices
Deliveries
Payment queue
Policy documents
Carrier portal

Dispute filing
Invoice matching
Proof of delivery
Carrier payment
Exception approvalAsk
Month-end closeAsk

214 tables · 1,840 documentsSend 2 questions

Illustrative example · Sample data

Simulation

Test the Change Before the Commitment

Compare software, process and policy changes on a working model of the client’s business. Review the results, assumptions and trade-offs before deciding what to implement.

Working Copy. A working model built from the client’s data, rules and processes, separate from live operations.
Changes That Matter. Explore software, process, policy and agent changes using a model suited to the question.
Replayed on History. Run the change against months of real decisions and see where it would have done better or worse.

Learn more about Simulation

Working copy/Dispute recovery18 months replayed

Corrigan Freight · copy of 14 Oct

Which change recovers the most?

TodayAs it runs now
56.2%
Process redesignHold disputes until the packet is complete
62.9%
AutomationCheck packets as they arrive
61.4%
New softwareMove disputes into the ERP module
58.3%

+6.7 ptsHolding until complete recovers the mostPlan rollout

Illustrative example · Sample data

Rollout

Roll Out What Works

Put tested changes into practice, one approved stage at a time. Agents handle repetitive tasks while your team reviews progress and the client controls what goes live.

Staged Rollouts. Move from shadow to supervised to live, one team or site at a time.
Sponsor Approval. The client’s sponsor approves every stage. Nothing goes live without them.
Supervised Agents. Delegate repetitive implementation tasks to agents, with your team reviewing what ships.

Learn more about Rollout

Hold until complete/RolloutWave 2 of 3

63.1%recovered in Oakland, live

62.9%the simulation predicted

Team	Stage	Recovery
Oakland APLive since 3 Nov	Live	63.1%
Portland APSince 10 Nov	Supervised	61.7%
Reno APFrom 17 Nov	Shadow	Not yet

DWDana Whitfield approved wave 2Roll back

Illustrative example · Sample data

Impact

Measure the Impact

Measure results in the client’s systems against an agreed baseline. Use comparison groups where appropriate, explain uncertainty and bring the findings to the client for sign-off.

Baselines. Record where each measure stood before the change, from the client’s own systems.
Comparison Groups. Compare against regions, teams or periods the change didn’t touch.
Predicted and Actual. Set each result beside what the simulation predicted, and learn from the gap.

Learn more about Impact

Halsey Software/Impact statementConfirmed

$250,000a month, since the EMEA desk opened

$150k$250k$350k

Rhea OkoyeVP Revenue, Halsey Software

Signed 2 Oct

Illustrative example · Sample data

Clean by Design

Where client work happens, and where the most sensitive data stays.

Client Environments

A Clean Environment for Every Client

Give each client a dedicated environment, with access scoped to the engagement and a clear plan for handover and closure.

Starts Empty. Start each engagement without bringing across another client’s data or access.
One Client Only. An environment holds a single client’s data. It is never mixed with another client’s.
Ethical Walls. Restrict access to the people assigned to each client and engagement.

Learn more about Client Environments

Ashby & Vale/Client environments3 active

Corrigan FreightOpened 2 Oct · closes 31 Dec

Clean

Started empty, with nothing from another client
4 read-only connections, each granted by the clientERP history
6 people and 3 agents, walled off from rival clients
Handover and access closure planned for 31 Dec

HS
Halsey Software5 people · 2 agents
Walled off
BH
Brightwater Health3 people · 1 agent
Walled off

Illustrative example · Sample data

Data Rooms

Clean Data Rooms for Sensitive Work

Analyze sensitive data from multiple parties in a controlled room. Set who can work with it, what can be shared and who must approve each release.

Data From Every Party. Bring the relevant datasets together with access rules agreed by the participating parties.
Rules Agreed Up Front. Who can ask what, and what may leave, is set before any data arrives.
Named Clean Teams. Only the people and agents named for the room can work in it.

Learn more about Data Rooms

Clean data room/Corrigan × LarkspurClean team of 4

CFCorrigan Freight3 datasetsLFLarkspur Freight2 datasets

Raw records restricted · groups of 10 or more · counsel approves each release

Question	Result	Status
Carriers both companies use	41 carriers	Released
Rate gap by lane	212 lanes	Released
Savings from shared carriers	$4.1M–$6.3M	With counsel
Customer list, Oakland–Portland	Names customers	Held back

Illustrative example · Sample data

One Connected Engagement

Carry the sources, assumptions and approvals forward as the work moves from discovery to delivery.

Security Built for Client Work

Keep client work separate, scope access to the engagement and review sensitive results before sharing. Your team and the client stay in control of what goes live.

Explore security and controls

Clean Client EnvironmentsOne client per environment
Clean Data RoomsOnly approved results leave
Read-Only AccessGranted by the client
Sourced FindingsEvidence kept with the finding
Human ApprovalPeople approve what ships
Planned HandoverClear terms for access and data

Bring Imprimatur to Your Next Engagement

Request a demo