Explore Northstar, a fictional services business investigating why client handoffs get delayed. Select a view, open a source and follow the reasoning into a decision and delivery plan.
Explore the model. Select an entity to see its evidence and relationships.
Evidence, interpretation and proposals stay distinguishable.Fictional business data · no live connections
Studio
Client operations / Handoff investigation
Project context
MC
Why does client onboarding keep getting stuck?
ProcessScoutExample analysis
The delay starts before delivery accepts the work.
In the sample, 18 of 60 handoffs arrive without a delivery owner. The walkthrough describes a return-to-Sales loop, even though the checklist requires an owner before acceptance.
18 / 60Missing an owner
8.4 daysSample mean cycle
3 sourcesOpen to inspection
A practical next step
Move the readiness check earlier. Keep a named person responsible for exceptions and let Delivery make the acceptance decision.
The sources suggest a relationship, not proof that missing ownership causes every delay.
DRAFT OUTPUTHandoff investigation
Finding: ownership is checked late
Evidence: sample + team walkthrough
Next: compare a checklist with automation
MC
What could we change without replacing our systems?
ProcessScoutExample analysis
Start with the handoff, keep the systems you use.
The CRM already holds the scope and commercial owner. The project workspace already holds the delivery brief. A readiness check can connect the two, with a person handling incomplete records.
3 optionsSame business goal
6 weeksOption B estimate
$108kNet capacity / year
A practical next step
Compare a checklist change, an automated handoff and a wider client portal. The middle option is the preferred planning example, subject to a pilot.
The USD 108,000 annual value is modeled capacity after running costs. It is not a realized cash saving.
DRAFT OUTPUTOptions decision brief
Preferred: automate the readiness check
Condition: confirm fields and access
Pilot: measure 20 handoffs before rollout
Processes
Client onboarding / From agreed scope to delivery
6 steps
Baseline · example source records
Select a step to inspect its role, system and evidence.
Scenarios
One goal: a delivery-ready handoff with clear ownership.
Fictional scenarios. All values are planning assumptions in USD.
Decision fact
Implementation
$9k
$36k
$72k
Annual running cost
$2.1k
$9k
$20.4k
Capacity released / year
540 hours
1,800 hours
2,160 hours
Net modeled value / year
$33k
$108k
$120k
Simple payback
3.3 months
4.0 months
7.2 months
Delivery estimate
2 weeks
6 weeks
12 weeks
Change risk
Low
Medium
High
OPTION A / PLANNING CASE
Clarify the handoff
Make the checklist explicit, name an owner earlier and coach the team on acceptance.
Quick to introduce. Chasing and re-keying remain manual.
01Agree the checklist
02Coach account managers
03Review the first 20 handoffs
OPTION B / PLANNING CASE
Automate the handoff
Check readiness in the CRM, route exceptions to a person and prepare the delivery brief after acceptance.
Balances effort and potential value. Requires field mapping, access checks and a measured pilot.
01Confirm rules & access
02Build and test the handoff
03Pilot, measure & review
OPTION C / PLANNING CASE
Connect client onboarding
Extend the handoff into a client portal with shared requests, status and onboarding documents.
Broader change and a longer rollout. Needs client adoption and more integration work.
01Design the client experience
02Build portal & integrations
03Introduce the new service
Capacity value, not a committed cash saving. 720 handoffs/year × time released × USD 65/hour, less annual running cost. Simple payback uses that net value and excludes adoption ramp, tax and discounting.
Workflow design
Client handoff / Proposed automation
Draft · review required
Readiness check → delivery briefTarget: n8n
Missing information
Documents
Decisions, procedures and plans / Client operations
3 deliverables
Evidence → Selected direction → Reviewed deliverables
NORTHSTAR SERVICESDecision brief / v2
Reviewed
A clearer handoff. A practical next step.
Move the readiness check before the handoff. Prepare the delivery brief only when the scope, approval and owner are present. Keep the acceptance decision with Delivery.
01
What the evidence says
18 of 60 example handoffs arrive without a delivery owner. The team describes a clarification loop back to Sales.
02
The proposed change
Check the required fields, assign exceptions to the account manager and route complete work to the delivery lead.
03
How we will know
Pilot 20 handoffs. Compare cycle time and actual effort with the sample baseline before considering wider rollout.
Connected evidence
NORTHSTAR SERVICESOperating procedure / v1
In review
Every handoff has a person behind it.
A practical guide for Sales and Delivery: what must be present, who checks it and where incomplete work goes.
01
Check readiness
Confirm agreed scope, commercial approval and a delivery owner.
02
Handle the exception
Return incomplete requests to the named account manager, with the missing information clearly stated.
03
Accept and begin
The delivery lead accepts the complete handoff and confirms the next action in the project workspace.
Connected evidence
NORTHSTAR SERVICESDelivery plan / v1
Draft
From an agreed rule to a measured pilot.
Sequence the change around the people, systems and decisions it depends on. The dates and effort below are planning assumptions.
01
Weeks 1–2 · agree the rules
Confirm field mapping, system permissions, the exception owner and the pilot acceptance criteria.
02
Weeks 3–4 · build and test
Validate complete and incomplete handoffs, duplicate requests, access failures and recovery.
03
Weeks 5–6 · pilot and review
Observe 20 handoffs. Record actual cycle time, effort and exceptions; review with Maya Chen before rollout.
Connected evidence
Connect the whole picture.
Select an entity. Follow its evidence. See what a proposed change touches.
Ask a better question.
Investigate the handoff with source-backed analysis and a useful draft to take forward.
Make the work visible.
Compare today’s handoff with the proposed process. Inspect a step to see its owner and rule.
Give every option a fair hearing.
Compare investment, effort and modeled value. Select an option to inspect its assumptions.
Connect the design to execution.
Explore a proposed workflow, its exception route and the checks needed before release.
Turn the thinking into useful work.
Open a decision brief, operating procedure or delivery plan—with their evidence attached.
Interactive product illustration. Fictional data; figures are examples.
Connected evidence & value
Trace the business case
back to its basis.
Inspect the source, finding, decision and forecast. Adjust the example assumptions to see how the estimate changes. These are planning values, not customer results.
ProcessScout/Evidence to value
Fictional working example
NORTHSTAR SERVICES / CLIENT ONBOARDING
A better handoff. An explainable return.
01 / SOURCE REGISTER
Start with something you can inspect.
Source evidence
Intake-checklist.mdFictional source
Before delivery accepts the work, the handoff must contain an agreed scope, commercial approval and a named delivery owner. Incomplete handoffs return to the account manager.
4 sections · Maya Chen
Delivery-team-walkthrough.mdFictional source
“The scope is usually there. The delay starts when nobody is named to pick it up. We send it back to Sales, then create the project brief after someone accepts it.” — Jordan Lee, 04:12
12:40 · Jordan Lee
Handoff-records.csvFictional source
60handoffs in the sample
18missing a delivery owner
8.4 daysmean cycle time
First five records · September sample
Handoff
Delivery owner
Cycle time
NS-001
Not assigned
11.2 days
NS-002
Not assigned
11.2 days
NS-003
Not assigned
11.2 days
NS-004
Jordan Lee
7.2 days
NS-005
Sam Rivera
7.2 days
Systems-and-owners.csvFictional source
The customer CRM holds the scope and commercial owner. The project workspace holds the delivery brief. The team inbox carries exception requests. Alex Morgan owns integration access.
3 systems · Alex Morgan
Capacity-assumptions.csvPlanning estimates
Annual volume
720 / yearPlanning estimate
Automated handoff time released
2.5 hours / casePlanning estimate
Loaded labour rate
$65 / hourPlanning estimate
Adoption
100%Planning estimate
Implementation
$36,000Planning estimate
Annual running cost
$9,000 / yearPlanning estimate
Handoff-decision-brief.mdFictional source
Preferred option: automate the readiness check and route exceptions to the account manager. Retain delivery acceptance. Pilot with 20 handoffs before deciding on wider rollout.
Version 2 · Maya Chen
Source records support a finding. Financial estimates have their own documented basis.
02 / CONNECTED FINDING
The ownership check happens too late.
Inferred finding
18 / 60
handoffs arrive without a named delivery owner.
THE RECORDS
Incomplete handoffs return to Sales for clarification.
THE TEAM’S ACCOUNT
“The delay starts when nobody is named to pick it up.”
A specific question to investigate. Could checking ownership before the handoff reduce clarification and rework?
The sample shows a relationship to investigate; it does not establish causation.
03 / PROPOSED RESPONSE
A clearer handoff. The same business systems.
Proposed
CURRENT PROCESS
Sales submits the handoff
Delivery finds a missing owner
Return to Sales for clarification
PROPOSED PROCESS
Check scope, approval and owner
Route complete work to Delivery
A person accepts the handoff
Ownership stays explicit. Incomplete records return to the account manager. Delivery retains the acceptance decision.
Organization Brain