Built AI-first · Chapter 2 of 9
Every organisation runs seven zones, whatever it calls them: Lead Generation, Sales, Delivery, Operations, Finance, Team, and Owner. A retrofit and a re-engineering look identical from the outside in all seven. From the inside they differ in one observable way per zone.
Those seven observations are the useful part of this page. Read the table with your own organisation in mind and answer the tell honestly — nobody is watching, and the answer decides where chapter nine starts for you.
How to read it
The left column is not a straw man. It is what a capable, busy organisation does when it adopts AI sensibly and changes nothing structural — and most of the entries in it are things we did ourselves. The right column is not aspirational either; every row is something running somewhere, most of them on our own books.
The THE TELL line under each pair is the diagnostic. It is phrased as an observation rather than an opinion, so you cannot talk yourself into the right-hand column.
| Zone | ● Code red · the retrofitter | ● Code green · the AI-first builder |
|---|---|---|
| Lead Generation | More posts, more outreach, produced faster. Volume rises and nothing downstream moves. Because nobody can say who came toward the business this week, activity quietly becomes the metric. | One named owner for discovery, working a recorded map of every relationship, where position is decided by what the other person did — replied, booked, paid — never by what we sent. Our own rule, enforced in the database: our outreach never warms anyone. Two unanswered emails move a person into the nurture cycle and leave them cold, which is what stops a map flattering itself. THE TELL — Can you name who moved toward you last week and what they actually did? |
| Sales | AI drafts the proposal beautifully. The pipeline is still a spreadsheet, and what was promised in the room still lives in one person's sent items. | A pipeline an agent can read and write, offers assembled to signature-ready with the reasoning shown and the number left to the owner, and a promise made in a meeting recorded as a fact rather than a recollection. THE TELL — When a deal goes quiet, does anything notice before a human does? |
| Delivery | AI summarises the meeting. Everything that matters about the engagement still lives in the head of whoever attended it. | Delivery runs off written context — the client's facts, decisions and constraints, dated and sourced, read before anything is drafted. A different person gets the same answer, because they are reading the same library. THE TELL — If the person running your largest account vanished for a fortnight, what would a colleague read? |
| Operations | A drawer of automations bolted to individual tools, each able to break separately and silently. No single person owns the set. | Routines with a named owner, a cadence, and a written definition of "did not happen". Silence is treated as a failure rather than a pass — our own dashboard flags a scheduled run that never reported, instead of assuming it was fine. THE TELL — How do you find out an automation stopped? If it is "when somebody notices the output is missing", the zone is unowned. |
| Finance | AI explains last month's numbers. Genuinely useful, entirely backward-looking, and it changes no decision you had not already made. | Cash reasoned the way a controller reasons it: direct-method forecasting, the bank as the arbiter and the ledger as an opinion, committed and expected held apart. Invoices drafted inside three days and never issued by an agent. THE TELL — Do you know today what the balance will be in six weeks, and the three assumptions it rests on? |
| Team | AI as a per-person perk. Twelve people develop twelve private habits, the organisation learns nothing, and none of it can be handed to the next hire. | Roles written down once and executed the same way whoever is on shift. A method improved once is used by everyone who calls it, and the improvement is in the repository rather than in somebody's muscle memory. THE TELL — When your best person finds a better way, how long until everyone does it that way? |
| Owner | The owner is still the integration layer — the only place finance, delivery and sales meet — now with a larger queue of drafts to approve. This reads as progress for about six weeks. | A ranked queue with a hard cap, because thirty items is a list and three is a decision. The test is not how good the dashboard looks; it is whether the week the owner is unreachable is an ordinary week. THE TELL — What happens to your organisation in the week you cannot be reached? |
Six of the seven tells can be argued with. The seventh cannot, which is why it is last.
The translation
The seven zones are commercial words, and a chief reading "Lead Generation" is entitled to stop there. What is wrong with the commercial version is not that the functions are missing — they are all present, several of them staffed — it is that the labels are borrowed from a business that sells things, and a chief who spends more time managing a board than most sales VPs spend managing a pipeline does not need to be told they have no Sales function.
This is the translation we use. It is fixed, so that every page in this series and every proposal we write uses the same words.
| Commercial zone | The same zone in a fire district or a city |
|---|---|
| Lead Generation | A staffed function in most districts: the public information officer, plus every community event the crews run — station tours, CPR classes, car-seat checks, open houses, ride-alongs. Each one produces named people who turned up. Recruitment and volunteer intake sit here too. |
| Sales | The board of commissioners, continuously. Five elected people who have to be brought along before a levy, a ballot measure, a grant match, an interlocal agreement or a budget request goes anywhere. A chief is making the case every month, not every four years — and that is a longer, harder sale than most commercial pipelines. |
| Delivery | Response, and everything beside it: Mobile Integrated Health and community responder programmes with enrolled clients and referral sources, fire and life-safety inspections, plan review, permits, public education. The service the public receives, and the records that prove it happened. |
| Operations | Stations, apparatus, facilities, scheduling — and the inspection cycle itself: which occupancies are due, when, and what happens when a re-check slides past its date with nobody assigned to notice. |
| Finance | Budget, payroll, purchasing, audit, plus inspection and permit fee revenue and programme billing where it runs. Public money, public trail. |
| Team | Personnel, training, credentialing, succession. Certifications with expiry dates and no owner but the officer who happens to remember. |
| Owner | The chief — with a board. The one zone that is harder than its commercial twin: the single point of failure also has a governing body it must keep informed, so the week the chief is unreachable has an audience. |
Ask a business owner to build the thing in the Lead Generation row and it is months of work. Ask a fire district and the honest answer is that it already exists: the inspection programme keeps a population of buildings and businesses, a recorded history of every interaction with each one, and a date for when the next one is due.
That is exactly the structure the rest of this series argues for — facts with dates and sources, a cadence, and a defined meaning for the date passing. It is usually sitting inside the records system being asked one record at a time, by an inspector who opened it. What is almost never asked is the population-level question: what is overdue, by how much, which occupancy classes are drifting, and who was told.
The same is true one row up. A district can answer the Lead Generation tell — who moved toward us last week and what did they do — because the CPR class has a roster, the car-seat check has an appointment, the tour had a request behind it and the ride-along had an application. Those lists exist. They are just kept in the place that proves the event happened rather than in a place that can be asked a question.
Using it
The table invites a full-programme response and that is the wrong move. Seven simultaneous re-engineerings is how an initiative becomes a thing people wait out.
Choose the zone where the tell is most embarrassing and the first failure is cheapest to reverse. Those two conditions rarely point at the same zone, and where they disagree, reversibility wins — chapter eight explains why that is not timidity but the thing that buys you the mandate to do the next one.
Step one
In your own words, in one sitting, without discussing it first. The value is in how quickly you can answer, not in the answer — a tell you have to research is already telling you something.
Step two
Red is "I could not answer". Amber is "I could answer, but only because I happen to know". Green is "the organisation could answer without me". Amber is the most common and the most dangerous, because it looks like green from the outside.
Step three
Not the biggest, not the most strategic. The one where a bad first month costs you a fortnight and an apology rather than a client, a licence or a headline.
In your world
Patterns we keep meeting, offered as a starting guess rather than a diagnosis. Your own seven answers beat anything on this page.
The two zones where the data already exists and nothing queries it. The inspection cycle carries dates; the CPR classes and tours carry rosters. In both, the district finds out something slipped when a person happens to notice — which is the Operations tell, and it is usually the one that stings.
Records, packets and permits are Delivery, and in a city of a dozen staff the Owner zone is rarely ambiguous: the administrator is the integration layer and everyone knows it. That makes the Owner tell the honest place to start.
Quoting gets the attention; follow-up and cash are where the money actually leaks. The Lead Generation tell — naming who moved last week — is usually the fastest red to find and one of the cheapest to reverse.
Everything worth knowing sits in a billable person's head, and the better they are the worse it is. The Delivery tell — what a colleague would read — tends to produce a longer silence than principals expect.
What we will not claim
Where this sits
Look back at the right-hand column and notice how many entries assume something is written down — the client's decisions, the rule about what warms a relationship, the definition of "did not happen". That body of writing is the actual asset, and chapter three is about why almost nobody builds it correctly.