The Content Engine
You should be publishing more, but every fix falls short. Hiring is slow and expensive. Ghostwriters miss your voice. Generic AI sounds like everyone. The engine is the in-between: built on your own calls and data, so it writes like you, costs less than a hire, and stays yours. The last one drove 20x search impressions in 110 days.
One engine build for Juniper Real Estate, measured in Google Search Console.
Most people open an empty chatbot and ask it to write a post. The copy comes out average because the only raw material is what the model already knew. I build the opposite: a system fed on your own material, locked to your voice, with hard rules about what it will and will not ship.
I spent 20 years at the Associated Press building content systems before AI made it fashionable. The engine brings that newsroom discipline to your business: written voice rules, a quality gate that blocks the tells of machine writing, and a plan for what to publish next.
The engine is only half of what you're getting. Every build starts with strategy: the angle your market is missing and only you can own. For a real estate team that was data-backed local pages nobody else would build. For a product consultancy it was positioning. The strategy decides what to say. The engine makes sure it ships, every week, in your voice.
From a blank idea to published, distributed content.
Zoom in on one live URL. Grade it, then hand back ranked fixes.
Pull back to the whole picture. Score every core page as one system, not one URL at a time.
A failed draft loops back, revises, and re-runs. Nothing reaches you until it passes. You sign off at every checkpoint. Edit by voice or keyboard, or hand back your own rewrite, and the engine folds it in and keeps going. You are always in the loop.
I run this system for my own site, and I've shipped it for a real estate brokerage, a product consultancy, a housing data product, and a job search tool. Here are two of them.
Juniper Real Estate
An agency stalled for months. I gave Juniper a wedge, data-backed local content nobody else in San Diego was publishing, then rebuilt every page with the engine and shipped 23 pages in a week. Daily impressions went from 40 to over 1,500, clicks grew 4x, and ChatGPT, Perplexity, Claude, and Gemini now cite the pages. One local business found a guide and reached out.
Level Up Product
Jon Shutt built products at Disney, MLB, and Perry Street for 20 years, then let his consultancy sit for a year. I locked his positioning, built an engine on his own stories, and handed him a system he runs by voice. Five approved posts shipped before my work wrapped.
A lot of the edits already feel really close to what I would want anyway. At this point, it's likely just nitpicking.
Ryan didn't just build pages, he helped me figure out what we should actually be known for. Instead of chasing the same market updates every agent in San Diego posts, we focused on the local questions people were really asking.
Why impressions come first
Each step feeds the next, and impressions are the door. A quiet site has to get seen before clicks and leads can follow.
Search is splitting. People still Google, but more of them now ask ChatGPT, Perplexity, Claude, and Gemini, and those engines answer by citing pages they can actually parse. The engine writes structured, schema-tagged pages built to be that source. Juniper's are already turning up as citations in live answers.
See it for yourself
Everything on this page points to real work. Juniper's ADU permits guide was researched, written, illustrated, and published by the engine on real permit records by neighborhood. It's live, and it earns the best click-through rate on the whole site.
Curious what your business could do with an engine like this?
Book a Fit Call I'm Ryan. Most people call me Berg. One person builds your engine, start to finish, so there are no handoffs and nothing gets lost between a strategist and a dev shop. More about how I work.
I move fast and I like to keep it fun and as painless as I can. The one thing I ask for is a few working sessions up front, so we get your wedge and your voice genuinely aligned before the engine starts producing. Get that right and the rest runs itself.
The engine publishes to your live site, so it has to land on something solid. One client's search numbers only climbed after I fixed what was underneath: SEO configured correctly, schema in place, the basics working. If that groundwork is missing, we handle it first with the Foundation before the build.
Positioning and voice. I find your wedge, or help you find one if it isn't clear yet, mine your transcripts and past writing, then lock your voice and the roadmap.
I build the engine, tune the gate on real drafts, and wire up publishing automation.
Training for your team, first pieces shipped together, then a clean handoff with documentation.
You run it from day one, or I run production for a stretch and step back once the numbers show.
Before the engine
The engine only pays off if search engines can crawl, read, and rank your site. When the technical setup is in the way, broken crawling, missing schema, slow or thin pages, I fix that first in a scoped piece of groundwork I call the Foundation. It repairs the plumbing and flags the weak pages. The engine then fills the site with content worth ranking.
You're buying an asset, not renting hours. A writer or agency bills for as long as you keep them, and the work walks out the door when they do. The engine is a one-time build that costs less than the first few months of a senior hire, and it keeps producing after, because it's yours.
Voice lock, agent skill, quality gate, roadmap, visuals, publishing automation, training, handoff. Scope depends on how many voices, how much automation, and whether distribution is included. Scoped after a call.
An extra marketer and builder on your team without the headcount. I run production, publishing, and SEO upkeep, and send a performance readout every month. Higher in the band it becomes ongoing strategy too: where to aim the engine next, new pages and channels, and tuning what is already live so more of the traffic converts. Where you land comes down to how much of that you want and how much ships each month.
If your site needs technical groundwork first, site config, speed, and broken-link cleanup, that is the Foundation, scoped and quoted on its own before the engine build.
I also take a limited number of founder-scale engines for solo consultants. Ask on the call.
Two different problems. ChatGPT is a generalist with no memory of your business, so you re-explain yourself every session and still get something a competitor could have typed. A writer learns your business, then walks out the door with everything they learned when the contract ends. Hiring a writer is renting content. The engine holds your voice, market, and rules permanently, you own it, and it keeps producing long after I step away.
A QA layer for AI-written text. Multiple automated checks run before a draft ever reaches you: em dashes, banned words, robotic sentence patterns, claims without evidence. If a draft fails, the system rebuilds it. You only review work that already passed, and you stay the final check before anything ships.
Google says it rewards helpful content however it gets made and goes after mass-produced spam. The engine is built for the first and blocks the second: every piece runs on your real expertise and data, not filler. The Juniper numbers on this page came from engine-built pages, measured in Search Console, and AI engines cite those same pages as sources.
Three to four weeks for most engines. The exact shape depends on how many voices we lock and how much automation and distribution we wire in.
Either. Some clients take the keys the day training ends. Others keep me on as a fractional marketer and builder: I run production, and at the higher end the ongoing strategy too, while their team ramps up, then step back once the numbers prove out.
WordPress is proven in production, including automated Yoast and RankMath SEO metadata, FAQ schema, and image uploads through the API. It is not WordPress-only: this site runs its engine on Astro and Netlify, and I have published through fully custom apps like CasitaScore and Kinship Careers. If your stack has a way in, the engine can publish to it.
Engine builds start at $27,500. If you want me to run it after launch, that runs $12,000 to $18,000 per month with a six-month minimum. The exact number comes out of the fit call.