Reference · 20 August 2026
For Ken, answering what he asked for at the end of the 19 August meeting:
"What do the workflows say? Where is the content? How does that work? Because I'm going to need to build the accelerants in a way that fit into the workflows."
Written 2026-08-20. Everything below was read out of the running code. Plain English throughout.
⚠️ Corrected before it was sent
The first draft of this said "copy Chad's twenty ISN emails — the content already exists." Ken has ruled the other way and he is right: "We don't need ISN, we're not doing that. When they lose ISN, they lose it." We are building our own. This version is written on that basis, and Part 3 explains why the ISN model would have been the wrong thing to copy even if we were allowed to.
A workflow is a list of messages that send themselves. Something happens, a timer starts, a message goes.
We have four running today. Two of the four engines we sell run on a monthly timer, and neither timer has been built. But the thing that makes ours different from ISN's is already half-built and nobody has noticed — see Part 3, which is the part worth reading.
Four messages. That is the entire automated system.
| # | What sends | When | To whom | How |
|---|---|---|---|---|
| 1 | "New booking" | The moment Josh books | The inspector | Text |
| 2 | "You're booked" | The moment Josh books | The customer | |
| 3 | Reminder | 24 hours before, again 2 hours before | The customer | |
| 4 | "How did we do?" | 3 hours after the report is published, again 2 days later if no answer | The customer |
All of it is off by default. A master switch, plus separate switches for the payment link, the agreement and the texts. Nothing sends until somebody turns it on.
The only text goes to the inspector. Everything the homeowner gets is email — the rule Dil made absolute today, now enforced in code.
| Engine | What the site promises | What exists |
|---|---|---|
| 1 — Reputation | Ask every client for a review, catch unhappy ones privately | ✅ Built |
| 4 — Conversion | Josh answers, quotes, books, takes the money | ✅ Built |
| 2 — Agent | "Your active referring agents get a monthly touchpoint… Runs monthly." | ❌ Nothing |
| 3 — Retention | "Every client enters the full twelve-month sequence." | ❌ Nothing |
Ken's diagnosis in the meeting was mechanically correct. The prospects asked only about the conversion engine because two of the other three cannot be demonstrated. There is nothing to show them.
This is the part that matters, and it is the reason Ken's ruling on ISN is right.
Chad's ISN sends twenty emails per inspection. Every client gets the same twenty, in the same order, on the same clock. It is a conveyor belt. It does not know anything about the person receiving the email, and it never changes its mind.
That is a perfectly good 2009 product and it is exactly the thing Ken keeps refusing to copy. Three times now, in his own words:
On ISN's report menu: "I bet there's nobody that ever pulls a quarter of these… What we need to do is get reports that have MEANING."
On ISN's work-order screen: "had all kind of information on there, you had to search and find what you were looking for."
On ISN itself: "We don't need ISN, we're not doing that."
And the deepest reason is the one he gave about America's Call Center: "In order not to get placed in the same bucket as ACC, we've got to make this change." Copying a conveyor belt is how you get put in the bucket with the other conveyor belts.
His four-people reframe, from the same meeting:
"Every engine is a person you'd hire if you could afford it."
Read the second one again, carefully:
"One whose only job is keeping every agent, whoever sent you work, feeling appreciated, and noticing when one goes quiet."
"Noticing when one goes quiet" is not something a conveyor belt can do. A person watches. A sequence just runs.
And his diagnostic question for the same engine:
"How many agents who sent you work haven't seen anything in 6 months from you?"
That is a question about STATE, not about a schedule. No fixed sequence can answer it, which is precisely why it is a good question to open a sales call with.
This is the finding of the whole document. The Business Center already sorts every agent by their own booking history, automatically, with no tagging by anyone:
| Standing | What it means | Set at |
|---|---|---|
| VIP | 5 or more referrals | AGENT_VIP_MIN |
| New | First job in the last 30 days | AGENT_NEW_DAYS |
| Active | Sent work in the last 60 days | AGENT_ACTIVE_DAYS |
| Cooling | 61–120 days — slowing down | — |
| Dormant | Over 120 days — gone quiet | AGENT_DORMANT_DAYS |
There is a report called "Who has gone quiet" built from Ken's own Mary Jones story, and it already shows the agent, their standing, how many jobs they sent, when the last one was, and their phone and email.
It reports. It never acts. Nothing sends anything on the strength of it.
So the difference between our sequence and ISN's is one sentence: ISN sends the same thing to everybody on a clock. Ours sends a different thing depending on what the person has actually been doing.
That is defensible on a sales call in a way that "we also send emails" never is. It is also the literal implementation of the person Ken described.
Built from Ken's four people, not from ISN's twenty slots.
Their whole job: keep every agent feeling appreciated, and notice when one goes quiet.
| Their standing | What the person does | Why |
|---|---|---|
| New — first job just landed | A thank-you that is not a receipt. Once. | The first referral is a test. Most inspectors fail it silently. |
| Active | The monthly touch — one useful thing, no ask | Staying in mind between referrals |
| VIP | The monthly touch, and the inspector is told to call them | Ken already holds slots for his best agents. Same instinct. |
| 🔴 Cooling (61–120 days) | "Sarah hasn't sent you anything in 3 months" — to the inspector, not the agent | This is the moment it is still recoverable |
| 🔴 Dormant (120+ days) | A win-back, and the inspector is told | Ken's "she ain't given us an inspection in two years" |
Two of those five rows are things ISN cannot do at all, and they are the two that make the engine worth paying for.
⚠️ The Cooling alert goes to the INSPECTOR, not the agent. An automated "we miss you" to an agent who has gone quiet is the most obviously automated message in the world. A nudge to Chad saying "Sarah's gone quiet — here's her number" is a person noticing. Same data, opposite feeling.
Their whole job: stay in touch with everyone you have ever inspected for.
The state that matters here is different — it is what kind of house they bought, not how recently they called.
| Their situation | What the person does |
|---|---|
| Everybody | The monthly touch — one ten-minute job they can actually do |
| New construction | The 11-month warranty reminder. Their builder warranty expires at 12 months |
| Bought 12 months ago | The anniversary — and this is the natural moment to hand them back to their agent |
⚠️ The 11-month warranty touch is the single highest-value message in the entire system, and it is the clearest example of the difference. It is worth real money to the client, it can only be sent by someone who knows what they bought, and it generates a paid re-inspection. A conveyor belt sends it to everybody or nobody.
We already know who is in new construction — Josh asks, and it is on the booking.
Already built. Engine 1 got its one-page review page today; Engine 4 is Josh.
Ken's actual reason for asking.
| Accelerant | Where it hangs | Needs |
|---|---|---|
| Newsletter | The monthly slot in Engines 2 and 3 | The monthly timer + content |
| Home Pro Network | A touch after the report — a real recommendation, not an ad | The slot exists |
| Google Business Profile / Microsites | Not a message. Runs beside the engines | — |
| Paid Ads | Feeds Engine 4 — more calls to Josh | — |
| Converting Website | Feeds Engine 4 | — |
| Authority Builder | ⚠️ Still not ruled on | Ken |
Two of the six are message sequences; four are not. Both of those two need the same monthly timer. Build it once and both have a home.
Added 2026-08-20 after the evening meeting, because this was misunderstood in both directions on the same call and it is worth being exact.
Dil said he still had to "integrate the Echo Desk, the modules." Ken stopped it:
"We don't want to do the Echo Desk. We created our own from Echo Desk."
But he is not throwing Echo Desk away — he asked for the opposite. Earlier in the same meeting:
"Like EchoDesk had that nice layout of the procedures for Sean Bacon. We need to get our procedures laid out on a Whimsical form. So that you and I can sit down and say, okay, this works, this works, here's what the content looks like, here's the topics."
So the position, in one line: build something LIKE Echo Desk, do not run Echo Desk. What we take from it is the shape — a readable map of modules, laid out so two people can sit in front of it and argue about it. What we do not take is their content, their timing or their integration.
| We copy | We do not copy |
|---|---|
| The layout — modules on one page, drawn so a non-technical person can follow it | Their sequences, their timing, their words |
| The idea that a procedure is something you can point at, not something buried in a tool | Any integration with Echo Desk itself. Nothing connects to them |
| Ken's own test: "okay, this works, this works" — a map built to be argued with | Their conveyor-belt shape. That is the ISN problem under a different name |
What Ken actually needs to see on that map, in his words — these four questions are the specification:
And one he asked separately, which decides whether this is generic or good: a client in Nashville — "would the information going to the agent be something about what's going on in the Nashville real estate market?" We know AI can localise it. Nobody has decided whether it should.
⚠️ THIS IS NOT ENGINEERING WORK YET, AND SAYING SO IS THE POINT. Ken: "Those things have to be worked out by us." The map is a sitting-down job for Ken and Dil, on Whimsical, before anything is built. Item 4 in Part 6 below — the words — is the same bottleneck seen from the other end.
Twelve months of history now comes in, not three — see FLOWS.md ⑩ for the mechanism. What matters here is where those people land.
| Who | What they get | Why |
|---|---|---|
| Booked by Josh, job finished | Engine 1, review request included | They were asked on the call and the answer is on the recording |
| Imported from their old system | Straight into Engine 3. No review request. | Their old system already asked. Ken: "they've already received it from the ISN and either did it or didn't do it" |
Ken's words: "they would just drop immediately into that Engine 3 sequence." The tag Engine 3 is applied on import, alongside Prior Client and Imported.
⚠️ NOBODY IMPORTED IS EVER TEXTED. That is the sentence that makes twelve months safe rather than reckless, and it is the whole reason the window moved.
⚠️ AND THE AGENT HALF IS NOT RULED. Ken named Engine 3 for prior clients. He did not say where a prior agent starts. Engine 2 is the obvious parallel, which is exactly why it has not been assumed. Ask him.
| # | The work | Size | Who |
|---|---|---|---|
| 1 | A repeating monthly job in the scheduler | Small — it already runs timed, cancellable jobs. It has never been asked to repeat | Engineering |
| 2 | Act on agent standing — fire when someone crosses into Cooling or Dormant | Small. The detection already exists and is already on screen | Engineering |
| 3 | The 11-month warranty touch | Small. We know who bought new construction | Engineering |
| 4 | Twelve agent emails and twelve client emails | ⚠️ The real work | Ken |
| 5 | Rule on the Authority Builder box | One sentence | Ken |
| 6 | The procedure map on Whimsical — the four questions in Part 5b | A sitting-down job, not a build | Ken + Dil |
| 7 | Where a prior AGENT starts — Engine 3 is ruled for clients only | One sentence | Ken |
| 8 | The spam / unsubscribe threshold that alerts Booked Solid | One number | Ken or Dil |
Items 1–3 are days, not weeks, and 2 is close to free because the hard half — knowing who has gone quiet — is already running.
Item 4 is the whole job, and it cannot be delegated. Nobody else can write in Ken's voice or decide what an inspector should say to an agent in March.
⚠️ These show the SHAPE. Ken should rewrite every word. Nothing here has been sent to anybody and nothing should be until he has been through it. They are deliberately short — the point is the trigger and the tone, not the prose.
Text to Greg: Sarah Mitchell hasn't sent you a job since 12 May — that's 3 months. She sent you 4 before that. 281-555-0140.
That is the whole engine in one message. No campaign, no template, no unsubscribe. A person noticing, and a phone number.
Subject: Pearland market note — August
Hi Sarah,
Seeing the same two things on 2015–2018 builds around Shadow Creek: attic ductwork pulling loose, and expansion tanks that were never strapped. Both cheap to fix, both ugly on a report if the buyer wasn't warned.
If you've got someone under contract on one of those, mentioning it up front lands much softer.
Anything you need this month, just call.
— Greg, GC Home Inspection
The shape: one useful thing, specific to their patch, no ask. The twelfth one gets the referral, not the first.
Subject: Your October home checklist — 10 minutes
Hi Marcus,
Ten-minute job this month: lift the water heater's pressure relief valve, let it discharge a second, close it. If it drips after, or nothing comes out at all, it needs replacing — about $15, and it's the valve that stops the tank becoming a problem.
While you're down there, check the drain pan isn't holding water.
Anything looks wrong, send me a photo.
— Greg, GC Home Inspection
The shape: something they can do this weekend. A newsletter gets deleted; a ten-minute job gets done, and the person who suggested it gets remembered.
Subject: Your builder warranty ends next month
Hi Marcus,
You closed on 14 September last year, so your builder's one-year warranty runs out around 14 September this year.
Anything they'd have to fix for free now becomes yours to pay for after that date. The usual list: drywall cracks from settling, doors that won't latch any more, grading that's moved, HVAC that never balanced properly.
Most people don't look until it's too late. If you'd like, I'll walk it before the date and give you a list to hand the builder.
— Greg, GC Home Inspection
Why this one matters most: it is worth real money to the client, it can only be sent by somebody who knows what they bought, and it books a paid re-inspection. This is what "four people, one flat fee" sounds like in an inbox.
Read from: api/backshop/jobs.js, module1.js, scheduler.js, api/ghl/inspector-read.js (the agent-standing rules), dashboard/inspector-portal.html (the "Who has gone quiet" report), and the four engine pages — all on 2026-08-20.