The Marketing Show

client_context / docs / the ecosystem

It is not a pipeline. It is a loop.

Everything a business touches flows into one brain — reviews, phone calls, text threads, job photos, what people did on the website. Agents read from it and publish back out to the same platforms the facts came from. And here is the part that makes it an ecosystem rather than a funnel: every post that goes out lands back in as a row, so next week the system already knows what it said.

What comes in Google reviews polled every morning also a place we post The profile itself hours, categories, area also a place we post Voice AI calls the whole transcript every call, as it ends Conversations texts and replies all day long Jobs and photos from Wayne's phone the moment he is done The website pages, forms, visits also a place we post client_context one row per business sealed per client Who reads it The job publisher every finished job you approve, then it goes The weekly agent mines the week's calls checks what it said before The dossier whole client, one page never goes stale You, just asking one question every source at once Where it goes Google Business Profile posts, photos, review replies the same place the reviews came from Facebook the business page what lands here comes back as a row The website a new section, deployed then read back in as a page YouTube the walkthrough clip views come back as a fact too every post that goes out lands back in the brain — that is why it never repeats itself
Wayne was great! Showed up on time and cleaned up after himself.
incoming call · 4m 12s
“Do you do drywall, or just demolition?”
text · 9:41 am
“Can you come Thursday instead?”
job 214 · 6 photos
Bathroom remodel — before and after
already posted · 9 days ago
“We also do drywall repair”
written from a real call
Drywall or demolition? Both, usually on the same job.
posted tuesday · coming home
kind='social_post' — now the system knows it said this

↔ swipe the diagram

fetched on a schedule arrives as it happens agents reading and publishing the return loop

The platforms are on both ends

Google is where the reviews come from and where the posts go. Same for Facebook and the website. The marks on those boxes are not decoration — the arrow genuinely goes both ways, which is the difference between a feed and an ecosystem.

Nobody hands anything off

The job publisher does not tell the weekly agent what it posted. It does not have to. Both write to the same table and both read the same table, so the handoff is the database rather than a message between two systems that have to stay in sync.

The loop is the whole point

A post that goes out and is forgotten is how you end up saying the same thing in week three and week eleven. Because published posts come back in as rows, "have we said this already" is a query, and next week's agent starts smarter than this week's did.

Six streams in, four readers, four places to publish, and one return path. None of the streams know about each other. A review, a phone call, a text thread, a photo from a driveway, a form submission, and a post that went out last Tuesday all land in facts as rows that differ only by their kind. That is the entire trick. Because they share one table, an agent writing Tuesday's post can read Monday's phone call, the service area, the brand voice, and every post already published — in one query, with none of it typed in twice.