Sensing
Notice what happened. Capture a signed agreement or a job that finished.
The Business Nervous System
A business can own excellent software and still run on the owner’s memory.
Accounting knows the money. The CRM knows sales. Email holds conversations. People know the gaps between them. Somebody still has to make the whole thing work.
The invisible operating work
The owner becomes the integration layer.
A job is complete, but billing finds out later. The most current customer status lives in a salesperson’s head. An automation stops quietly. A recurring responsibility exists because one person remembers it.
The company gets through the day because capable people compensate. Over time, the owner becomes the person who can reconcile every version of what is happening.
That dependence has an architectural cause. The business needs a deliberate way to connect an event to useful context, an accountable decision and a verified result.
The Business Nervous System is that operating layer across the company’s software and human work.
The functional model
Five things the business must be able to do.
These functions describe the health of the whole system. Each workflow can involve all five.
Signaling
Get it to the right place. Operations gets the agreement and the context it needs.
Processing
Make the information useful. Required details are checked against the work being promised.
Deciding
Give the next move an owner. A clear rule handles the routine case; a person owns the exception.
Regulating
Check that it actually finished. The project is ready for delivery, or the missing piece is visible.
The implementation architecture
Six layers working together.
Systems of record
The software that knows its part.
Business memory
A shared picture of the operating work.
Integration
Information moves between systems.
Processing
Events become useful context.
Interface
Each person can see and do their part.
Control
Failures and unfinished work become visible.
01 · Systems of record
The software that knows its part.
Accounting stays in QuickBooks when QuickBooks is the right authority. The CRM, scheduling and job software retain their appropriate responsibilities.
02 · Business memory
A shared picture of the operating work.
Notion often holds customers, projects, commitments, responsibilities, decisions and their relationships. Each important fact has a defined home.
03 · Integration
Information moves between systems.
Zapier, APIs, webhooks and scheduled processes propagate the state changes the business actually needs.
04 · Processing
Events become useful context.
Rules, calculations and transformations handle predictable work. Selective AI can assist with information that needs interpretation.
05 · Interface
Each person can see and do their part.
Notion views, forms, Slack, email, owner briefings and purpose-built tools expose the next useful action.
06 · Control
Failures and unfinished work become visible.
Monitoring, reconciliation, completion states and escalation reveal whether the intended result happened.
Where Notion fits
Give the business a useful memory.
Notion is often where I give the business a shared operating memory: customers, projects, commitments, responsibilities and the relationships between them.
A project view can point to the authoritative customer record and expose what operations needs next. Accounting data stays in the accounting system when that is its proper home. Copies have a defined purpose and an update rule.
Useful views reduce the amount people have to remember. The architecture also needs connections, processing and controls around those views.
Inspect published Notion systemsHuman accountability
Decide what deserves a person.
A familiar calculation can follow a rule. A material change to a customer promise needs a person with the context and authority to decide. The system should make that decision easier to reach and easier to carry out.
AI can help extract details, classify incoming information or prepare a first pass. Where an error has consequences, the design specifies review, failure behavior and escalation. A reliable rule is often the better tool for repetitive work.
Something started. Did it finish?
An automation run marked “successful” might only mean an API accepted a request. It does not establish that the project is ready, the customer received the right information or the job was billed.
Important processes need a completion state and evidence of reaching it. Missing owners, stale states and mismatched records should surface when they matter. That is how an operating layer earns trust.
A small piece of the larger system
From signed agreement to ready project.
Before · carried by people
A customer signs.
- The agreement lands in an inbox.
- Someone copies the customer details into the CRM and creates a project.
- Operations gets an email and makes the folder and tasks.
- A required detail is missing. Sales has to ask the customer.
- Someone remembers to check again Thursday.
The process moves when a person carries it.
After · a designed operating layer
The signature starts the work.
- The customer and project state update in their appropriate systems.
- Documents are filed and routine tasks appear with owners.
- Operations receives the information needed to begin.
- Missing details create an exception with an accountable person.
- A completion check confirms the handoff is ready.
People handle judgment. The system carries the routine work and checks the handoff.
Illustrative workflow design. The exact tools, checks and exceptions follow the business.
Installation
Build the first useful operating layer.
We agree the problem, systems of record, human decisions and finish line. I build the connections and working surfaces, test normal and exception cases with the team, and document the result.
As little as one week, starting at $5,000. Timing depends on the agreed scope and required access.
See what an Installation includesContinuing 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.
A structure that can outlive its builder
Ownership stays with the business.
Client-controlled accounts, an operating map, an automation inventory and current documentation make the system transferable. Another competent operator should be able to understand what exists and assume custody.
Read the Architecture & Stewardship StandardBegin with what you can see
A workflow is enough to start.
If the problem is systemic or unclear, the $999 Read provides the architecture recommendation before a build is scoped.