A content engine that keeps posting.

Why posting stops

Posting runs on memory, and memory loses to a busy week. Your crew gets a hundred great moments a month — before and afters, a tricky install, a happy customer — and most of them die in the group chat. Not because nobody cares, but because nobody’s job is to turn them into posts.

The loop

1. Research. What your audience saved, watched and asked about last week, and what’s working in your trade and your area.
2. Draft. One job becomes a week of posts, each written for its platform rather than copy-pasted: a reel, a carousel, a LinkedIn write-up, a short with chapters.
3. Approve. The week lands in one queue on your phone. Preview anything, edit anything, approve the rest. The one step we never automate away
4. Publish. On schedule, on every channel, while you’re on the job.
5. Measure. Reach, saves, watch time and messages feed straight back into next week’s research.

What the approval step checks

Four ways engines go stale

1. The same angle every week. The research step flags repetition and rotates angles.
2. Old photos. A standing ask to the crew: three photos from every job, sent the day it finishes.
3. Platforms change what they reward. Formats get rechecked when the platforms shift, instead of a year later.
4. Nobody’s measuring. If the loop doesn’t close, it’s a posting schedule, not an engine.

The part that actually matters

Posts are the means, not the point. The point is the message that says “can you quote mine?” — and a system that answers it, books the estimate and drops it in your pipeline where you can see it.