The Operator Console is a place, not a tool.
It is the place a residential business operates. Customer drill. Pipeline. Operations across crews and routes. Catalog. Billing. The day's attention. The strategic deliberation when a hard call has to be made. Many surfaces, one runtime — the operator opens it in the morning and works inside it through the evening. Inside it, walks happen. Quotes get written. Crews get briefed. Customers get answered. None of those are the Console. They are what the Console is for.
What's inside the place.
The Console composes seven surfaces. Each is a place inside the place — opened during the work it's for, set aside when it's not.
- 01Today — the day's attention. What needs eyes, what's moving, what's about to land. Pulls across the other six.
- 02Customers — the customer spine. History, properties, sentiment, the long-cycle relationship.
- 03Pipeline — opportunities through proposals through signed work. Lead-to-sold motion.
- 04Operations — crews, routes, walks, installs, recurring service. The field happening.
- 05Catalog — plants, materials, service tiers, the reference data the operator names work against.
- 06Billing — invoices, payments, follow-up. The close-cycle.
- 07Council — the deliberation surface. Where the operator consults voices when a decision is heavy.
Today is the rhythm-organizer; Council is the strategic seam; the other five are where the operator's work lives day-to-day. The Console is not Today and it is not any one of these surfaces. It is the place they compose into.
Today is attention, not a feed.
Today pulls from every surface. Yesterday's walks waiting on review. Proposals at the 48-hour gate. Customers who haven't responded. A margin variance that crossed a threshold overnight. A crew briefing that hasn't been read. A renewal cycle approaching. The Council deliberation that has been sitting since Wednesday.
The operator opens Today and the day organizes itself — not by chronology, by what needs eyes now. The Console knows the work because the work flowed through it. Today is what comes back out.
Four surfaces that also stand alone.
Four of the Console's surfaces also surface as standalone tiles in the residential matrix — discoverable as tools in their own right, even though they live inside the Console:
- Lead-to-Sold— the pipeline motion · opportunity through proposal through signed work
- The Watch— today's attention as its own surface
- Schedule & Visits— calendar, routes, visit captures
- Billing— invoice, payment, follow-up
They are not the Console. They are what the Console exposes when an operator wants to point at a piece without pointing at the whole. The Console is the integration — these four are the windows in.
AI is the cognition layer, not a feature.
The honest architectural read: a SaaS product with AI features bolted on is what most operators have seen called AI. The Console is being rebuilt to escape that — AI as the cognition layer, not the feature tier. Seven AI Layers compose the spine:
- 01Capture — Voice, photo, document, structured form → structured record. What enters becomes substrate.
- 02Triage — Structured record → routed and categorized. What needs which work, in which order.
- 03Synthesis — Multiple records → integrated read. The customer overview, the walk synthesis, the crew briefing.
- 04Surface — Integrated read → operator-facing artifact. What the operator sees, edits, approves, sends.
- 05Loop-back — Surface → operator decision → updated record. The 48-hour customer touch closes back into the spine.
- 06Council — Multi-perspective AI input → operator deliberation. The strategic seam.
- 07Audit — All of the above → first-class observability. Cost, confidence, cache, retry, invalidation — operator-legible, not just developer-legible.
Today the production Console runs Capture, Synthesis, Surface, Loop-back, and Audit at N=1. In design are the AI-Native rebuild that escapes the bolted-on architecture, plus the Council layer's full surfacing. The bio names both honestly — neither claims the rebuild is shipped nor hides that it is being built.
When the call is heavy, the Council sits.
Some decisions don't sort themselves with a single read. A renovation that's bigger than usual. A pricing call against a long-cycle customer. A capacity question that bumps into the season's edge. When the call is heavy enough that the operator wants more than one perspective before committing, the Operator Council sits — four AI voices, each reading the same situation through a different lens, none of them deciding.
For the residential landscape pro, the Council carries four voices:
Estimator voice
Reads scope, pricing, materials specifics, job economics. Asks: is this priced honestly, is materials substrate accurate, is scope appropriate.
Scheduler voice
Reads capacity, timing, seasonal fit. Asks: can we do this when the customer wants, what does it bump, what does the operator's week look like.
Customer-relationship voice
Reads history, sentiment, communication fit, long-term arc. Asks: what does this customer need from this artifact, what's the relationship history, what tone is right.
Margin voice
Reads profitability, cost substrate, risk-adjusted return. Asks: does this job pencil at our margins, what risks shrink margin, is this the right work for us.
The four voices speak in parallel. The operator reads, weighs, decides. None of the voices is the decision. The Council is the amplifier— the operator's deliberation gets louder, more honest, harder to fool — but the call stays with the operator. That is the whole point. Bulk yards, maintenance operators, and design-build shops get different voice sets calibrated to their persona; Council voices are configured per operator, not fixed.
Same Console. Four operator shapes.
The residential vertical is not one shape. The Console runs against four personas — same runtime, different chrome composition, different surfaces leading the day:
Landscape pro
Owner-operator. Walks properties, scopes jobs, captures during walks, produces customer overviews. Persona 1. N=1 substrate anchored at Rooney.
Bulk yard
Owner-led counter and delivery operation. Customer initiates by walk-in or quote form. Seasonal-rhythm-driven. Persona 2. N=1 substrate anchored at Lavin.
Maintenance
Recurring service operator. Large customer base. Renewal cycles, route discipline, retention as the work. Persona 3. Sketch-anchored; substrate fabricates with first engagement.
Design-build
Full-service design through install. Longer cycles, larger tickets, multi-role coordination. Persona 4. Sketch-anchored; substrate fabricates with first engagement.
The same Console serves all four. The persona configuration shapes which surfaces lead, which Council voices sit, which Today cards compose, and which Capture specialists fire. Persona is structural; what the Light-Mid-Heavy tier is, is the dial within persona.
What's true today. What's being built. What this won't claim.
The Console runs in production at N=1. The AI-Native architectural direction is being built underneath it. Some of what the bio describes is anchored against the production runtime; some is anchored against design substrate the operator has authored; some is honestly named as not-yet-built. Where a claim sits matters more than the claim's confidence.
Anchored
Multi-tenant runtime. Walk capture and synthesis. Today dashboard. Customer overview surface. Audit columns. 48-hour customer feedback loop. SectionEditDrawer. The Project Intake spine. Production at N=1 at Gambro; substrate ports forward; chrome rebuilds for residential.
Sketch-Anchored · In Design
Per-persona Console chrome composition. Operator Council layer (Reading A · per-persona voice sets · Persona 1 voices named above). Six-tier schema architecture. AI-Native dispatch substrate. Strategic Brief surface for cross-window deliberation.
What This Does Not Claim
That the AI-Native rebuild has shipped. That the Council layer is fully runtime-active across all four personas today. That cross-operator wisdom is in the Console — that is deferred behind a separate architectural decision. That every persona's voice set has been calibrated against deployed runtime — Personas 3 and 4 are sketch-anchored, and the calibration happens with the first engagement in each shape.
A place where attention belongs. A runtime where AI is the cognition layer, not the feature tier.
The Operator Console is what the residential business runs on. Not the tool that helps with one thing — the place where every thing happens, composed by AI work that the operator can read, audit, and override. Production today; rebuild in design. The operator who lands here is invited to see both honestly.
If a residential operator wants to see the Console at their own operation, the path is an engagement — pre-letter substrate work on isolated infrastructure, then migration at engagement-letter sign. This is the Demo Factory discipline; not a free trial, not a self-serve sign-up, not a demo gallery.