Health
Monitor the operating layer.
Maintain the automation inventory and review health and surfaced exceptions at the cadence we agree. A failed connection has a visible route to attention.
Business Nervous System Stewardship · $2,000/month
The system has a custodian.
Once the operating layer is in use, I take continuing responsibility for keeping it healthy as software, staff and the business change.
What custody looks like
Someone knows what is running—and what needs attention.
Repair
Fix ordinary failures.
Repair broken connections, references and ordinary defects in the installed workflows. Record meaningful changes and their downstream effects.
Memory & interfaces
Keep Notion useful.
Maintain the installed databases, relationships, views, templates and operating notes so the shared model still helps people do their work.
Change
Adjust the system as work changes.
Adjust an existing field, view, routing rule or workflow when the change fits the installed architecture. Recalibrate the architecture periodically as the business evolves.
What the fee protects
Healthy infrastructure can have a quiet month.
$2,000/month
Thousands of routine actions might happen correctly while I need to intervene for twenty minutes. That can be an excellent month.
You are paying for the operating layer to remain dependable and for someone to know when it needs attention. My work follows what the system needs.
You can see what is under custody through the operating map, automation inventory, exceptions and recorded changes.
A practical boundary
What belongs in Stewardship?
| Within Stewardship | Separately scoped Installation |
|---|---|
| Repair an existing CRM-to-project connection. | Replace the CRM and migrate its data. |
| Adjust the current onboarding task and escalation rules. | Design a materially different onboarding architecture. |
| Update Notion views and existing fields as responsibilities change. | Add a department with a substantial new data model. |
| Maintain completion checks and exception routing. | Build a new application or a substantial unrelated workflow. |
We agree the boundary before a major change begins.
How custody begins
Make the responsibility explicit.
Stewardship follows Installation. We identify the systems and workflows under custody, their owners and dependencies, monitoring cadence, escalation routes and the process for requesting changes.
For an existing operating layer, I first need to understand what is running and what condition it is in. Any stabilization or substantial rebuilding receives its own scope before I assume ongoing custody.
We agree how often I review system health, how issues reach me and when you can expect a response. Development stays within the installed workflows; substantial new work is scoped separately.
A responsible handoff in either direction.
Documentation stays useful for continuity. If custody changes, you receive a current operating map, automation inventory, ownership notes and reasonable transition information. The business retains control of its data and environments.
Inspect the stewardship standardDiscuss Stewardship
What operating layer needs a custodian?
Tell me whether we are discussing an installation together or a system already in use. Stewardship is $2,000/month once the scope and condition are established.