Concept

Systems

What it is

A system is a standing process that makes the same decision the same way every time so the operator does not have to think about it. Checklists, phase sequences, pay rules, green-light language, pre-written scopes, standing VA tasks, recurring calendar blocks. The opposite of a system is improvisation — deciding in the moment, from scratch, every time the situation comes up. Improvisation burns bandwidth; systems preserve it.

Why it matters

The operator’s bandwidth is the constraint. Every decision spends a token. You have maybe a hundred good decision-tokens per day and most people burn them on junk: what should I tell this contractor about next week, what order do I inspect these three jobs, how should I pay this invoice. A system turns each of those into a one-line rule you wrote once. Run the phase system. Pay fast on green-lighted work. Send the weekly PM report on Fridays. Walk every job at 5pm. The tokens you save go into the hard decisions — the acquisition, the exit, the fire, the pivot.

Ross prefers systems and vendors over employees. Employees need payroll, benefits, legal exposure, and constant management. Systems and vendors are pay-for-use, scalable, and replaceable. A written system plus a VA plus a depth chart of subs does what a four-person team does at a fraction of the overhead and with none of the payroll risk.

How it shows up

Shows up as every piece of paper with a number on it. The scope of work is a system. The ledger is a system. The jobs menu is a system. The pay schedule is a system. The 81-point checklist is a system. The green-light system is a system. When a new problem comes up the operator asks: what is the rule for this? If there isn’t one yet, write it, run it, and add it to the stack.

bandwidth, virtual assistant, depth chart, lazy pm, phases, green light system, scope of work, larossa system