Operating systems for owner-operated companies

Run the company on what it already knows.

I build an AI operating system inside the software your team already uses. It learns how your best people work, briefs the team every morning, drafts the follow-ups that slipped, and reports findings every Friday.

Morning brief · PM team06:40
01RFI 114 (level 2 steel) has waited 6 days on the architect. Reply drafted in your Outlook.
02The mechanical sub's pay app is missing its lien waiver. Request drafted.
03Closeout for the school addition: 4 of 11 documents received. List attached.
Source: project mailbox, SharePoint, Monday's cost export. Read 06:31.
Sample brief, made-up data.
01 / The problem

Right now, your operating system is a person.

Every company has one. The project manager who knows which sub needs a second reminder. The coordinator who knows how the owner likes a bill coded. When they are out, in a meeting or retired, the company slows down. Most AI tools do not fix this, because they know nothing about how your company works.

What it sounds like
"Ask Steve, he knows."

How the work gets done lives in a few heads and fourteen inboxes. New hires take a year to catch up.

What it costs
Things slip quietly.

The unanswered email, the missing document, the invoice nobody chased. Nobody sees it until it is a problem.

Why AI has not helped
The tool is the easy part.

A chatbot with no memory, no rules and no scoreboard is a toy. The work is teaching it your company.

02 / The system

Six layers. Most companies buy one.

An operating system for a company is built from the bottom up. Each layer depends on the one below it. I build all six, on the systems you already run, one department at a time.

Most AI pilots start at layer 4 and stop there. Rules, handoffs and the scoreboard are the layers that decide whether your team still uses it in month six.

03 / What your team sees

Nothing new to learn. It shows up where they work.

No new app and no new login. The system works inside Outlook and the tools your team opens every day. A person approves everything that leaves the building.

06:40 · Every morning

A brief that finds what slipped

It sweeps the mail, the files and the exports overnight, then tells each person the three things that need them today.

Unanswered 5+ days4 threads
Documents missing2 pay apps
Renewals inside 30 days3
All day · Outlook drafts

Replies already written

Follow-ups wait in Drafts, written the way your team writes. Edit it or send it. Every edit teaches the system.

Re: RFI 114, level 2 steelDraft
Lien waiver needed for OctoberDraft
Closeout documents, 7 outstandingSent
Any time · One place to ask

Answers that show their source

Anyone on the team can ask how you do something or where a job stands. Every answer names the report it came from and when it was read.

How do we handle a change order over $10K?
Two signatures: the PM and the division lead. Source: PM playbook, rule 14. Read 09:12.
Friday · The scoreboard

One page of findings

The department head gets a weekly page measured against a week-one baseline. It always includes what the system got wrong.

Drafts approved41 of 50
Hours returned23.5
What it got wrong2 items, both now rules

Screens show sample data.

04 / How it earns trust

It starts by watching. It gets promoted one task at a time.

Every task sits on a ladder. The system moves up a step only after it passes tests written from your own rules, and you can move it back down any day.

Step 1

Observe

Read-only. It learns how the work moves and changes nothing.

Step 2

Suggest

It flags what slipped and tells a person what it would do.

Step 3

Act with approval

It writes the draft. A person reads it and presses Send.

Step 4

Act alone

Only for tasks that have earned it, and only where you say so.

05 / The pilot

Ninety days. One department.

I start with one team and one workflow, on site. At day 90 you have a working system, a weekly record of findings, and a clear decision: expand to the next department, adjust, or stop.

Weeks 1 to 2

Audit and rules

  • On-site audit of how the work moves
  • Rules workshop, signed off by the department head
  • Week-one baseline for the scoreboard
Weeks 3 to 6

Brief and drafts

  • The morning brief goes live
  • First drafts land in Outlook
  • Weekly review with your champion
Weeks 7 to 12

Scoreboard and decision

  • Friday findings against the baseline
  • Tasks promoted as they pass their tests
  • Day-90 review with the sponsor
5 to 300people, owner-operated, with a team in the office
$1M+in revenue, with work that repeats every week
1system of record you already pay for (Procore, AppFolio, Sage, QuickBooks)
2 hrsa week from one champion on your team
06 / Three ways in

Start small. The scorecard is free.

Every engagement starts with an audit, so the price is set by what the audit finds. No hourly billing.

Free · 4 minutes

Operating System Scorecard

Twelve questions. See your score on all six layers the moment you finish, then a written report by email within 24 hours.

  • Your score on each of the six layers
  • What your three weakest cost in team hours
  • A 90-day plan for the department you pick
Start the scorecard ↗
One owner · Monthly

The Operating Partnership

For the owner who runs the company day to day. I work inside your business as your Operating Partner, like a fractional COO for AI and operations.

  • First system built and included
  • Your Workspace, with an AI partner built around your business
  • One new system every 90 days
Start with the scorecard ↗
One department · 90 days

The Department Operating System

For companies with a team. All six layers for one department, built in your tenant, then expanded department by department.

  • On-site audit and rules workshop
  • Brief, drafts, one place to ask, scoreboard
  • Team training included
Book a 20-minute call ↗
Nick Mombello, founder of Vector Group
07 / Who builds it

I'm an operations manager, not an AI consultant.

I'm Nick Mombello. I have spent my career building the systems that make operations run, first as a civil engineer and officer in the Coast Guard, then in product operations at Flock Safety. I started Vector because owner-operated companies have the same gaps I fix at work, and nobody builds for them.

I run Vector on this same system every day. I build yours on site, on the tools you already own, and I stay to run it with you.

Civil engineer · former U.S. Coast Guard officer
Product Operations, Flock Safety
Founder, Vector Group · Springfield, Illinois
Start here

Find out what your company already knows.

Twenty minutes on a call tells us both whether there is a fit. If you would like to start on your own, the free scorecard takes four minutes, scores you on all six layers, and the report is yours either way.