For consultancies, brokerages, and research firms
Your own research and white papers, or public data in your field that anyone could download and nobody has read. I build the engine that turns it into content sounding like you, then hand you the keys.
The last build drove 20x search impressions in 110 days, written from public building-permit records.
Full builds start at $27,500 and end with a licensed system your team runs. Start smaller with a four-week Pilot at $12,500.
Built by a 20-year Associated Press content-systems veteran.
The messy part
The research, client work, and white papers are sitting there. What fails is turning that into pages that keep ranking, get cited, and sound like you every month.
You get a draft in a chat window, then you still research the claims, fix the voice, create or find the images, upload them, relink everything, fill SEO fields, and rewrite it for LinkedIn. Most chats start from zero with no memory of last month’s work, so the manual grind repeats every time.
You bring someone on to publish, and they spend the first months building voice docs, workflows, and templates instead of shipping. The pipeline stays thin while the salary runs.
New posts trickle in. Last year’s best URLs go stale, and that slow decay eats at ranking in Google and AI search while fresher, data-backed stories rise past them. Those pages stop bringing in traffic and leads the way they once did.
I built the Content Engine for that gap: a licensed system around your material that your team can keep running.
Why I built it
The source material is already there. I build the engine around it in 3 to 4 weeks, then hand over the keys.
The engine starts with what you can reach that competitors cannot bother to: your datasets, your records, your client work. Then it builds a roadmap around the questions your buyers are already asking.
Voice rules and a quality gate keep weak claims, repeated ideas, and machine-writing tells out of the drafts you review.
Your team gets a license to run the engine, its files, and the publishing workflow. Run it in-house or keep me on for production.
Branded charts and custom graphics are available as an add-on. They increase the build scope and price.
Proof from shipped engines
Juniper Real Estate
An agency stalled for months while Juniper's search traffic stayed flat. I rebuilt the site with the engine. Daily impressions went from about 40 to more than 1,500, and organic clicks grew 4x in the same window.
Read the Juniper case study →Level Up Product
Jon Shutt built products at Disney, MLB, and Perry Street for 20 years, but his consultancy went quiet for a year. The engine turned his own stories into five approved posts before the work wrapped.
“A lot of the edits already feel really close to what I would want anyway.”Read the Level Up case study →
Built for AI search too
Search is splitting. People still Google, but more of them now ask an AI system directly, and those systems answer by citing pages they can parse. Juniper's North Park coffee guide is already turning up as a source in live answers.
Start with the site
I review the site first. Most sites can already carry new work, so that review just sets the Pilot's mix of finished content and light repairs. If the technical setup is badly broken, I fix that first as its own scoped engagement.
First
I check crawlability, indexing, speed, broken links, SEO config, schema, and the pages new work will build on.
Usually
$12,500, four weeks. The review sets how much goes to finished content versus repairs, so most sites start here.
If it's serious
Scoped and quoted on its own when repairs alone would take longer than four weeks. The Pilot or the engine follows after.