ITMedic · Green IT Consulting
Most businesses are bolting AI onto a structure that was designed before AI existed. It makes the structure faster. It does not make it better, and in the places where the structure was already weak, faster is worse.
These nine pages are what we learned re-engineering our own company instead — the order we did it in, the parts we got wrong, and what the same shift looks like in a fire district, a city hall, a contracting shop and a professional practice.
Why we wrote it
A small consulting business with one owner, a major surgery on the calendar, and a recurring client leaving. The back office had to keep running whether or not the owner could open a laptop. So we stopped adding AI features to how we already worked, and re-engineered the work around what an agent can actually hold: a written job, a body of context, and a standing routine.
Twenty agents now run that back office. You can read their job descriptions, click through the dashboard, and watch a piece of information move between them with its chain of custody intact. This series is the argument underneath all three.
Every number in these pages is one we measured or one we do not print. There are fewer statistics here than you are used to, on purpose.
The nine
One to three name the problem and the missing asset. Four to six build the structure, in dependency order. Seven and eight govern the decisions. Nine puts it on a calendar.
Why bolting AI onto an old structure makes things worse rather than better — and the exact shift that gets you out. It is a change of unit, not a change of tool.
Read chapter 1 › Chapter 2Lead Generation, Sales, Delivery, Operations, Finance, Team, Owner — retrofitter versus AI-first builder, side by side, with the one observable tell that places your own business in each.
Read chapter 2 › Chapter 3The most important AI asset a business can build, and why almost nobody builds it correctly. Hint: it is not a folder of documents.
Read chapter 3 › Chapter 4Context, Skills, Routines — the structural foundation every AI-first company runs on, and why keeping the three apart is the whole trick.
Read chapter 4 › Chapter 5How a drawer of disconnected tools becomes a connected, compounding system — and the two roles most agent teams are missing.
Read chapter 5 › Chapter 6The connective tissue that lets your AI stack reach your CRM, your books, your calendar and your line-of-business systems — with your permissions, in your tenant, on your audit trail.
Read chapter 6 › Chapter 7A decision matrix that stops tool-chasing and produces choices that still look right in six months. Including the one everyone forgets is a decision.
Read chapter 7 › Chapter 8Where to start, where you earn the right to expand, and why the sequence is not a style preference. Autonomy is granted per act, never per agent.
Read chapter 8 › Chapter 9Ninety days, one year, three years — in the right order, with the gate that has to close before each stage starts.
Read chapter 9 ›Who it is written for
Every chapter ends by translating itself into the four worlds we work in. The words change completely; the structure underneath does not.
Records, reporting, grant windows and the statutory clocks. The admin load that has nothing to do with the response and consumes the officer anyway.
Council packets, public-records requests, permits and utility billing — run by a handful of people wearing six hats each.
Quoting, scheduling, job costing and the callback. The business that stops when the owner is on a roof.
Proposals, delivery, utilisation and renewals. Everything is in somebody's head, and that somebody is billable.
The offer
There is no gated PDF at the end of this. If one of the nine describes your business well enough to be uncomfortable, the useful next step is a short conversation about which three things in your organisation are currently held together by one person remembering them.