Source systems
The client record remains in its owners hands
Project, account and handover sources keep their existing ownership. The workflow does not create a second operating record.
Company Brain workflows
Client Delivery Brain / Founding workflow / 03
Hand over a client without handing over a mystery.
A transition brief for one live account. It gives the next owner the current state, commitments, open questions and sources behind the work.
What you buy
A 30-day implementation for one live workflow.
You are not buying a generic knowledge base, a software licence or open-ended advisory time. You are buying the configuration, evidence discipline and weekly operating loop for this defined work.
You receive
A workflow contract
One live workstream, an output format, evidence rules, a review cadence and an explicit stop or continuation decision.
A source and permission map
The approved source categories, their owners, intended use and exclusions for the specific workflow.
Four reviewable output cycles
A first artefact within seven days after complete setup, then three further weekly cycles that leave source links, uncertainty and an accountable next check.
You bring
One live workstream
An active account, pursuit or handover with enough work in the next 30 days to show whether the workflow helps.
A source authoriser and verifier
Someone who can approve the limited source boundary and someone who will review the weekly artefact against the live work.
A simple baseline
The current cost of reconstructing context, missed commitments, decision delay or rework so day-30 value is judged against a real starting point.
Day-30 value check
At day 30, the incoming or outgoing owner should be able to show that the brief removed context-recovery work, made an open question visible earlier, or prevented a handover miss.
We also check that the first output arrived after a complete setup, that the weekly output was reviewed and used, and that it has not created custom delivery work outside this workflow.
The operating problem
Start with work that already has a cost.
Client work loses momentum when ownership changes. The incoming person asks the same questions, reconstructs the account from disconnected tools and still misses the context behind a decision.
The workflow stack
The technology serves the workflow.
The first implementation uses the smallest approved source set. It is not a promise of a new platform, every connector, or blanket access to company data.
Context configuration
A shared definition of what must travel with the work
We define the current-state facts, commitments, questions, ownership rules and source references that the handover must include.
Human verifier
The outgoing or incoming owner reviews the transition
A named person checks the brief against the live account and records the gaps that still need an answer.
Weekly artefact
A current transition brief
The next owner gets a traceable view of the account and the work that needs checking, without pretending uncertainty has disappeared.
Approved source categories
Source 01
Client or project workspace
The live project state, milestones and open work that the new owner needs to see first.
Source 02
CRM or account history
The client record, stakeholders and commercial context needed to understand the relationship.
Source 03
Approved onboarding or handover material
Existing notes, decisions and client-safe reference material. The team selects the approved read-only sources.
How it starts
A bounded implementation, not an open-ended consulting project.
The page describes the workflow before any source is connected. We configure only the agreed scope, then decide from observed use instead of extending the work because it sounds interesting.
01
Choose the live work
Name one account or workstream, the recurring failure it creates and the outcome you will compare at day 30.
02
Configure the boundary
Agree the small read-only source set, exclusions, evidence rules and the person who can verify the result.
03
Use the weekly artefact
Receive the first output within seven days of a complete setup, then review four weekly cycles against live work.
04
Decide from evidence
At day 30, review use, reviewer time and at least one prevented miss, faster decision or reduced context-recovery time. Continue only if the work proved its value.
Technical setup
Technical detail, without a pretend platform.
You do not need to choose a new software stack to apply. The implementation starts by making the existing systems, permissions and human controls explicit for this workflow.
Source ownership stays put
The agreed CRM, delivery and document systems remain authoritative. This is not a migration or a replacement database.
Context is configured by policy
The setup defines allowed source use, evidence and uncertainty rules, a named audience, and the human review boundary before work begins.
Data handling is agreed before access
The project contract records the permitted processing and retention boundary for the client scope. This site never asks for credentials or private client records.
No autonomous external action
The starting workflow is read-only and produces reviewable outputs. People retain authority to message, commit, edit or approve consequential work.
The artefact
Client transition brief
The brief is reviewed weekly during the 30-day run so it follows the work instead of becoming a handover document that immediately goes stale.
Current state and source
Commitment or decision
Open question
Current owner
Next handover check
Scope boundary
Small enough to prove. Clear enough to trust.
- One active client account or transition workstream.
- Up to three approved read-only source types.
- One named verifier confirms the transition brief.
- No access beyond the selected sources and no automatic external actions.
Questions
Client Onboarding & Handover Desk, in practice.
Is this an onboarding portal?
No. The first scope is one operational transition brief for a live account. It is designed to improve one handover, not replace the company knowledge base.
Can a contractor use the brief?
Only if the client approves that audience and the source boundary permits it. The access decision stays with the source and workflow owners.
What happens when the handover is complete?
At day 30, the team reviews whether the brief was used, what it prevented or sped up, and whether it is worth continuing.
One bounded workflow
Describe the live work this should support.
Start with the account or workstream, the recurring failure, and the person who can verify the weekly output. Keep client credentials and private records out of the form.