Business Diagnostic: The Intake Layer
The Business Diagnostic is the intake layer of the Systems hub. It sits upstream of every system on the hub and does not score anything. It reads a situation described in plain language, names the operational pattern behind it, and routes the owner to the system whose instrument should run first. The systems score, and the ratified routing inside each system begins only after that score exists.
Every system on the Systems hub opens with an instrument. The VWCG Operating System opens with the Vision Canvas, the Leadership DNA Radar, and the AI Readiness Index. Twelve scored dimensions open the INTELLIGENCE Readiness System. Twenty scored competencies open the leadership system.
An instrument needs a decision before it runs. Someone has to decide which instrument fits the situation at hand. Owners rarely arrive with that decision made. They arrive with a symptom, described in their own words, and a sense that something structural sits underneath it.
The Business Diagnostic exists for that moment. It is a reading step, not a scoring step. It converts a plain-language description into a named pattern and a direction, so the first instrument run is the right one.
Layer One: The Intake
The input is a description of the business situation written the way an owner would describe it to a trusted peer. No data upload, no account, no email address. Nothing typed into the instrument is stored. The live instrument runs at businessconsultant.services and returns an operational brief in the same sitting.
The description does the work that a scored questionnaire cannot do at this stage. A questionnaire presumes the owner already knows which dimensions matter. A description lets the pattern surface from the words the owner chose, including the words that reveal what the owner has stopped noticing.
The intake reads for six operational patterns: founder dependency, reactive operations, growth without structure, a talent and retention crisis, a sales and revenue plateau, and strategic confusion. Each pattern is defined on the diagnostic methodology page, which is the source for this list. The intake does not define them again here.
Compound Patterns
A single pattern is the simple case. The useful case is the compound one, where two patterns reinforce each other and the fix for one depends on the other being in place. Founder dependency alone and founder dependency sitting on top of reactive operations are different situations with different first moves.
The intake names the primary pattern first and then names the compound interaction where one exists. That order matters for routing. A compound read changes which instrument runs first, because one system has to produce the measurement the other system will delegate against.
Missing the compound pattern is the common way a sound engagement addresses a symptom and leaves the structure untouched. The intake layer is built to catch it before any system is engaged.
Layer Two: Routing Into the Systems
Routing at this layer is directional. It points at a system and at the module or instrument inside that system whose published purpose matches the pattern. It does not trigger that module.
Every ratified route in the VWCG Operating System begins with a scored dimension, and no score exists yet at intake. The table below is orientation for the owner, not a specification.
| Pattern read at intake | System to enter | Where the published purpose matches |
|---|---|---|
| Founder dependency | VWCG Operating System, entering through Module 01 | Leadership DNA Radar and Vision Canvas in Intelligent Foundations, then Core Execution |
| Reactive operations | VWCG Operating System, entering through Module 01 | KPI Precision Grid, the measurement and early-warning module |
| Growth without structure | VWCG Operating System, entering through Module 01 | SOP Codex, the process documentation module |
| Talent and retention crisis | SELECT · ADVANCE · GROWTH, then VWCG Operating System | People & Culture Analytics, with the leadership competency ladder for the executive layer |
| Sales and revenue plateau | VWCG Operating System, entering through Module 01 | Sales Velocity Engine and Client Success Loop |
| Strategic confusion | VWCG Operating System, entering through Module 01 | Vision Canvas, the strategic direction instrument |
| Any pattern with an AI deployment question attached | The INTELLIGENCE Readiness System | Twelve readiness dimensions, feeding the AI Deployment Canvas |
Module 01 appears in most rows because it is the routing layer of the operating system. Its instruments produce the scores that activate every downstream module. An owner who enters anywhere else skips the measurement the rest of the system depends on.
The leadership and intelligence systems are entered directly when the pattern lives in people or in technology adoption. Both systems route their own gaps into the operating system once their scores exist. The intake layer only decides the door.
What the Intake Layer Does Not Do
The intake does not score, weight, or rank. It does not produce a heat map and it does not open a playbook. Those belong to the systems, where the instruments are calibrated and the routes are ratified.
The intake does not replace diligence. A plain-language read is a first move, built to be fast and to be wrong in a visible way when the description is incomplete. The scored assessment exists for the owner who wants the read confirmed in numbers.
The intake does not recommend a vendor. It names the pattern, the compound effect, and the type of engagement that pattern calls for. Who performs the engagement is a separate decision that belongs to the owner.
Layer Three: Outputs
The output is an operational brief. It names the primary pattern and any compound pattern, then explains the downstream effects specific to the situation described. It states the engagement type the pattern calls for and gives one concrete step the owner can take this week.
The brief can be handed on. An owner can give it to a co-owner, a successor, or an advisor as the starting document for a conversation that would otherwise begin with a symptom. The one step this week is deliberate. It converts a diagnosis into a motion before the diagnosis goes stale.
The brief does not name a system. That is the work of the routing table above. An owner reads the pattern from the brief, finds its row, and enters the system that row names.
From a Read to a Score
The read is enough to choose a door. It is not enough to run the room behind it. The next step for an owner who wants measurement is the strategic assessment at vwcg.app. It scores leadership, operations, AI readiness, and execution, and returns a report with a prioritized action plan as a PDF. Access is by invitation.
The two instruments are built to sit in sequence. First the diagnostic reads and routes. Then the assessment scores and returns a prioritized action plan, and the operating system takes that score and runs its ratified routes from there.
An owner who skips the read and starts with the score loses nothing except the compound-pattern check. An owner who skips the score and acts on the read alone is acting on a direction, not a measurement. The sequence exists so neither mistake is forced.
Getting Started
Describe the situation at businessconsultant.services and read the brief. Read the methodology page if the pattern names are unfamiliar. Then enter the system the brief points at, starting with its instrument rather than its playbooks.
Every system on the Systems hub is maintained as a working specification. The intake layer is maintained the same way. When the pattern definitions change on the methodology page, the intake layer changes with them, and the routing table is reviewed against the current specification of each system.