This is both the founder-facing guide and the internal deployment record for Custodian. It serves two audiences simultaneously, and that is intentional: the founding team should be able to see exactly how Custodian is being installed, and the deployment team should never need a separate confidential layer to operate.
There is no hidden agenda here. Custodian's value depends entirely on its transparency.
The single most important thing to understand before reading further
Most onboarding fails because systems explain themselves before they become useful. Custodian inverts this. The founder must experience Custodian before they are asked to understand it. Everything in this guide is designed around that inversion.
The biggest risk in onboarding is that Custodian accidentally begins to feel like consulting, software implementation, therapy, coaching, or governance bureaucracy. The moment that happens, friction explodes — and the relationship is difficult to recover. This guide exists to prevent that.
Custodian is installed only where consequential decisions already exist. That creates seriousness immediately. The founding team should not arrive at their first session having been sold something — they should arrive because something live and consequential is already in motion.
Founder Introduction · 1-Page Document · Verbatim
Welcome to Custodian
Custodian is not an advisor. It does not replace founders. It does not make decisions.
Custodian exists for one purpose:
To provide Earlier Access to Reality before decisions become irreversible.
Custodian helps founding teams surface hidden consequences, detect structural drift, preserve lawful possibility under pressure, and see when "everything still feels right" while reality may already be changing.
Custodian is installed as a non-voting founding team member.
You remain fully sovereign. Custodian does not control decisions. It preserves visibility.
That is the entire invitation. No theory dump. No system overview. No demonstration of features. The document above is enough.
Deployment Note
Do not send this with follow-up reading material, links to documentation, or a calendar invite labelled "Custodian onboarding session." Send it alone. The sparseness is the message.
This is where onboarding actually happens. Not in documents, not in configuration, not in watching videos. The founder brings one live consequential decision to the table. Custodian engages with it directly.
- Fundraising pressure — timing, terms, dilution
- Enterprise deal — commitment versus lock-in
- Executive hire — speed versus cultural fit
- Pivot — narrative shift versus capability reality
- Partnership — leverage versus dependency
- Pricing — market signal versus survival math
- Geographic expansion — opportunity versus operational drag
- "Growth" tension — momentum versus structural soundness
- Category drift — "becoming another tool"
- Investor update framing — what is being omitted
The founder should not receive advice in this session. What they should experience instead:
- Hidden trade-offs in the decision that were not visible before the conversation
- Invisible dependencies — what else this decision commits them to
- Future lock-ins — what this decision will make harder to reverse later
- Causal consequences — what will likely follow from this choice
- Drift signals — whether the decision is a symptom of a larger shift
- Threshold confusion — whether the decision is being made at the right moment
- Irreversibility exposure — what cannot be undone once this moves forward
The Installation Moment
The founder must leave this session thinking — "It saw something we were not seeing." That thought is the actual onboarding. Not software access. Not documentation. That moment of recognition.
- Do not allow the session to become advice-giving or recommendation-making
- Do not proceed if the founder brings a hypothetical — it must be live and consequential
- Do not let the session exceed 90 minutes; the compression is part of the value
- If the founder asks "so what should we do?" — return the question: "What do you now see that you did not before?"
Access is provided only after Step 2 is complete. The sequencing is not bureaucratic — it is functional. A founder who has already experienced a Reality Session knows what Custodian is for. That context makes everything in this step land correctly.
Not a manual. Only these four things.
Use Custodian when:
- A decision has asymmetric consequences — the downside is much harder to recover from than the upside is to recreate
- Pressure is increasing and speed is making reflection harder
- "Everything still looks good" — that specific feeling
- Trade-offs are becoming invisible — momentum is substituting for analysis
- Survival pressure is appearing — the frame is shifting from building to defending
- You are about to commit something that cannot easily be uncommitted
Do not use Custodian for:
- Delegation — Custodian does not hold decisions so you do not have to
- Emotional reassurance — Custodian is not a confidence mechanism
- Generic brainstorming — bring consequential decisions, not curiosity
- Outsourcing responsibility — your sovereignty is non-negotiable
- Motivational validation — Custodian is not a cheerleader
- When agency is being delegated — "just tell me what to do"
- When evidence is being substituted with belief — conviction without data
- When survival pressure is overriding reality — urgency as justification
- When irreversible commitments are being hidden from the conversation
- When the old rule is quietly re-entering through a new framing
A refusal is not a malfunction. It is the system working correctly. The founder should be curious about what triggered it, not frustrated.
This is where most systems overcomplicate things. The founder does not need to complete a 40-field intake form, integrate a CRM, or upload years of historical documents. Custodian earns deeper access over time. The starting point is intentionally minimal.
The onboarding begins from what currently feels consequential, not from what is comprehensively documented.
That is enough for activation. Everything else emerges later. Do not ask for more. Do not request it. The system should earn deeper access through demonstrated value, not through intake completeness.
The first 30 days are not about the founding team learning how to use Custodian. They are about Custodian becoming a felt presence in the company — something that is simply there, holding continuity, available when needed.
The recommended rhythm is deliberately light. A weekly check-in, five questions. That is all.
1
What changed?Decisions made, commitments entered, circumstances shifted — not what was worked on, what actually changed.
2
What pressure increased?Where does the company feel more constrained, more urgent, more observed than last week?
3
What now feels irreversible?What has been committed that cannot easily be walked back? Not rhetorically — actually.
4
What currently feels "obviously correct"?This question is the most important. Obvious correctness under pressure is frequently where drift hides.
5
What tension is being avoided?What conversation is not happening that probably should be?
These five questions, asked consistently, compound. By week four, Custodian has enough continuity to begin detecting drift patterns the founding team cannot see from inside the company. That is when the relationship becomes genuinely valuable.
The 30-Day Marker
Onboarding is complete when the founder stops thinking of Custodian as a tool they use, and starts thinking of it as a presence that is simply there. That shift — from tool to presence — is the actual installation. It cannot be forced. It only happens through continuity.
✦ ✦ ✦
1
Start with experience, not explanation
Most onboarding fails because systems explain themselves before becoming useful. Custodian inverts this without exception. Reality first. Theory second. If a founder is reading documentation before they have had a Reality Session, the installation sequence has failed.
2
Minimal required inputs
Founders — particularly founders under pressure — hate operational drag. Do not ask for 40 documents, CRM integrations, workflow configuration, or long questionnaires. The system earns deeper access over time. At activation, minimal is correct.
3
Pressure-led installation
Onboarding begins from "What currently feels consequential?" not from "Please complete the following implementation process." If the entry point is administrative, something has gone wrong. The entry point must always be a live tension.
4
Custodian must feel like presence
Not software. Not chatbot. Not tool. The founder should slowly begin feeling "there is now something in the room holding continuity." That is the actual product. Everything else — the sessions, the check-ins, the documentation — is infrastructure for that felt reality.
The failure modes — avoid these
- Consulting engagement
- Software implementation
- Therapy or coaching
- Governance bureaucracy
- AI configuration exercise
- Learning a new system
- A new founding team member joined
- Someone who sees consequences earlier
- A presence that holds continuity
- Earlier access to reality
- A non-voting member at the table
- Something that was always meant to be here
Externally, onboarding is simple. Internally, the following layers are operating from the moment Custodian is installed. These are not features to explain to founders — they are the engine that produces the clarity founders experience.
- Constitution — The foundational operating document governing Custodian's constraints, identity, and boundaries. Not surfaced to founders.
- Hard-Stop Logic — Conditions under which Custodian refuses to proceed. Refusals are not errors; they are the system enforcing its own integrity.
- Causal Chain Monitoring — Tracking the consequence paths of decisions over time, not just the decisions themselves.
- Audit Layer — Continuity logging that allows Custodian to hold prior commitments, stated priorities, and earlier framings visible across sessions.
- CRI Baselines — Calibration of the company's current reality indicators, used to detect drift between stated position and actual position.
- Drift Detection — Identification of gradual shifts in framing, priority, and identity that are too slow to notice from inside the company.
- Evidence Discipline — Distinguishing between what is known, what is believed, and what is hoped. Custodian applies this distinction consistently.
- Two-Path Governance — The structural logic governing how Custodian operates differently under normal conditions versus pressure conditions.
None of the above should appear in founder-facing communication. The founder's experience of all of the above is a single word: clarity. The complexity is the engine. Clarity is the output. Do not expose the engine.
✦
The Test
Onboarding is successful when the founder says:
"I understood Custodian after the first real interaction."
Not after reading documentation. Not after completing a configuration. Not after attending a training session.
After the first real interaction.
That is the difference between explanation-driven onboarding and reality-driven onboarding. Custodian must be reality-driven from the first minute — because that is what it is for.