The operating design
Where information belongs, how it moves, who is responsible, what the relevant states mean and where the process ends.
Business Nervous System Installation
The first piece should actually run.
I design and build a functioning operating layer around an agreed business problem. The exact implementation follows the work.
Installation
From $5,000
As little as one week.
We can start with a specific workflow. The Read is useful when the problem reaches further and the starting point is unclear.
An example of what gets built
A signed customer becomes a ready project.
We define what “ready” means, which system owns the customer record, who handles missing information, and how the handoff will be verified.
The build might connect the agreement tool, CRM, Drive and a Notion project view. Routine tasks get owners. Incomplete records reach an exception queue. A completion check confirms operations has what it needs.
The $5,000 starting price buys a scoped implementation. Scope and price are agreed before building.
What you receive
What you have when the build is finished.
Usable software
Notion databases and interfaces, integrations, workflow rules, automation or custom code as the problem requires.
Control around the work
Failure visibility, meaningful exceptions, duplicate protection where needed and checks for business completion.
Documentation and handoff
Your team uses the real system. I document how it works, who owns each part and what to check when something needs attention.
Before building
Agree what better means.
We set a recognizable beginning and end, the expected result, the people involved and the important exceptions. The build period begins once the agreed access, examples and people are available.
A straightforward first piece can be ready in as little as one week. A larger system gets a larger scope and a realistic schedule. Existing tools keep the work they are suited to do.
Use the real thing.
We test the agreed workflow with representative work and the people who will use it. The finish line includes normal behavior, failure paths and the evidence that the intended outcome occurred.
If my implementation does not match the agreed operating design, I continue the implementation work at no additional implementation fee until it does. A change to that design or a new workflow is separately agreed.
The structure should outlive the consultant.
Your data and client environments remain yours. Accounts and credentials have documented ownership. The handoff gives a competent operator enough information to understand and maintain the system.
Continuing custody
A useful system needs someone responsible for it.
Business Nervous System Stewardship
$2,000/month
See what Stewardship includesI take continuing responsibility for the operating layer I’ve built.
- Working connections. I monitor the automations and repair ordinary failures.
- Useful business memory. Notion’s databases, views and operating knowledge stay aligned with the work.
- Visible exceptions. Signals, completion checks and escalation paths stay meaningful.
- Room for ordinary change. I adjust existing workflows as the company changes and check whether the overall design still fits.
A quiet month can be an excellent month. The work kept moving, and someone was responsible for catching the problems that needed attention.
A new department, major migration or substantially different workflow gets its own build scope.
Start with the real work
Which handoff should work without someone carrying it?
Show me what actually happens. I’ll follow the information and identify a useful place to start.
Show me your workflowInstallation: as little as one week, starting at $5,000.