The marketing system · Verified 2026-09-16
Every channel on one spine.
Every number traced.
The system that carries a stranger from a search to a booked job for the businesses I run it for: the lead lands, the front desk answers, the follow-up fires, the owner sees what it cost and what it made. Below is each piece with where it actually stands — 8 running on real traffic, 2 proven with our own, 2 built and waiting for the first real use.
No revenue figures, no named client results on this page. Demo-tier only, by the same rule as /proof.
How a lead moves
One path, start to finish.
Nothing waits in an inbox.
- Someone searches, or a sourcing run finds them first. Research says who they are and what they already pay for.
- They land on a site that serves its words with JavaScript off, so search engines and AI assistants can read it.
- The form, the call or the chat becomes a contact in the owner's list, and the owner is told.
- Riley answers, checks the real calendar, books the slot, sends the confirmation with a link the customer can change.
- Reminders and follow-ups go out on a schedule the business set, with an unsubscribe on every one.
- The owner's dashboard says what the lead cost, which ones became work, and what a job was worth.
- Every scheduled piece reports its own failure. Silence pages someone.
The pieces, with the honest rung of each
What runs. What's proven.
What's only built.
Every lead becomes a contact
A form, a call or a chat on a client's site lands in the owner's customer list and notifies the owner. Nothing sits in an inbox nobody reads.
A real lead on a client site routed and notified, 29 July 2026; the seam is probed hourly.
Answered, booked, followed up
Riley answers the phone and the chat, checks the real calendar, books the slot, and texts the confirmation with a link the customer can change. A claim guard in code stops her promising what the business hasn't authorised.
Real callers booked on a live line, 13 September 2026, after a fix found by two callers who weren't.
Follow-up sequences by email and text
Reminders, confirmations and nudges on a schedule, per business, with an unsubscribe on every message and the owner able to text the business line and have the reply reach the customer.
Reminder sequence enrolled and cancelled end to end, and the owner-text bridge answered through the real webhook path, September 2026 — with our own messages. No organic customer has been through it yet.
Newsletter with real consent
Distinct consent for digest and editions, deduplicated welcomes, signed unsubscribe links, scheduled sends through the mail rail.
Scoped production send receipts, 12 September 2026. First edition went to zero eligible readers, which is the honest state of the list, not the system.
Outreach where there is no API
A queue of outreach tasks worked by a browser that behaves like a person — posting, messaging, filling forms on platforms that offer no integration — with every action logged and the physical mouse untouched.
Production end-to-end verified 12 July 2026, our own tasks. Volume is gated by consent and the platform's rules, not by the machine.
Ad copy, images, landing pages, video briefs
Generators for the pieces a campaign needs, a creative analyser that scores them, and a landing page that receives the click and hands the lead to the contact list.
Twelve runtime pieces exist and run on demand. No client's paid campaign has gone through them yet; that is the next receipt to earn.
Tracking and attribution the owner can read
Browser tags and server-side conversion plumbing on the marketing side; clean product telemetry on the other; one owner dashboard that says what a lead cost, which ones became work, and what a job was worth.
Owner outcome events flowing since 25 June 2026; ingestion health checked hourly with a durable readback and an independent heartbeat, 7 September 2026.
Research and sourcing
Enumerate a market before anyone builds, spends or bids: every business of a kind in a place, with the signals that say who is paying an agency, who has an ads tag, who has the reviews.
One cloud run enumerated 2,203 distinct businesses across the Front Range, 8 September 2026; a scheduled run has passed since.
The audit that starts the conversation
Read a business from outside — site, listing, reviews, search, competitors — and write the report a busy owner reads on a phone, with a free fix at the top and the evidence behind every line.
Every deep report on localbusinessfactory.com is an output; the Chiappetta report was audited by blind readers and a skeptic against its own ledger before it went out, 16 September 2026.
Found and trusted locally
The Google listing kept right — category, hours, photos, reviews asked for on every job — and the local pages built so the business shows up where its customers search.
Installed for clients on the Front Range; the listing logic is the part of the audit that catches duplicate and unclaimed profiles.
Publishing to Amazon
A book from the press to a Kindle listing: the publish packet, the attended KDP wizard filled to the last step, a person presses Publish, the ASIN written back.
Machinery built and the attended draft proven; no title has gone all the way through it to a live listing yet.
Every scheduled job reports its own failure
Each cron, sender and collector carries a dead-man switch. Silence pages someone. A broken job is a page, not a surprise three weeks later.
Cron observability green on the working-state board, re-checked within the hour, 16 September 2026.
What this page will not say
The rung is the claim.
Nothing above it.
- No revenue figure, growth percentage or named client result appears here. Those need a saved receipt and written permission, and this page is demo-tier by rule.
- No client's paid campaign has run through the creative generators yet. The pieces exist; the receipt does not.
- Social and ad platforms need per-account keys before anything posts or spends. The machine does not hold a client's credentials by default.
- The marketing-os.io domain lapsed in September 2026. This page is the system's address until it is restored.
The rules every piece is built under are public: github.com/Traviseric/best-practices. The sourcing engine is at trend-os.io; the front desk is on localbusinessfactory.com.