Content that sounds like your brand.
ContentEngine turns your approved brand knowledge into a content system your team runs every week, inside the AI tools you already use.
Runs inside Claude and ChatGPT, the tools your team already uses.
Your time, roughly · six hours for your main contact, three for your approver, two and a half per creator.
Illustrative
The problem
Your brand lives in people’s heads. AI can’t read them.
When the team gets busy, content stops, and whoever picks it up next sounds like somebody else. A general-purpose AI tool makes it faster, not more on-brand.
-
Messaging that changes depending on who wrote it
-
Content that stops the moment the team gets busy
-
The same piece rewritten for every channel
-
Claims and offers nobody signed off
How it works
One source of truth. Five working layers.
Everything is generated from one approved master. Change it once and every channel picks it up.
Delivered where your team works
- Claude plugin
- Custom GPT
- MCP server
- Inside OpsEngine
A test suite the engine has to pass before handoff, including trap tests written around your business.
A brand check and a human approval in front of anything published.
Six skills that do the work: a router, social, blog, email, a campaign planner and Brand QA.
A prompt library wired to the stack, plus prompts written for your channels.
Your Knowledge Stack: positioning, audiences, offers, proof, FAQs, objections and rules. Nothing ships until you’ve approved it.
Process
Built with you. Four sign-off gates.
We draft, you review. Nothing locks until your approver signs it.
-
Fit check and kickoff
We confirm the fit, agree the scope and pre-fill the kickoff document. You see three sample posts early.
-
Build your Knowledge Stack Gates 1–2
You answer ten questions at most. We build the stack and a second reviewer checks every row.
-
Review, lock and test Gates 3–4
Your approver signs off and the engine locks. Each platform is tested to 90% or better.
-
Train and hand off
Recorded training for every role, a quick reference card and two weeks of close support.
What you get
Built to run every week, by your team.
The engine
- Your Knowledge Stack master
- Claude plugin, Custom GPT and/or MCP server
- Prompt library wired to your stack
- Brand Kernel
How you run it
- Operating playbook: who does what
- Content plan and calendar
- Quick reference card
- Recorded training for every role
Proof and support
- QA tests and a shared QA report
- Change log and versioning
- 30 days of support, the first 14 with close support
- An optional care plan after that
Why trust it
Built so you can check it.
-
It writes from what you approved.
Only approved rows ever ship. Ended or unapproved offers can’t leak into content.
-
It says when it doesn’t know.
If the answer isn’t in your stack, it writes [NEEDS CONFIRMATION] instead of guessing.
-
Two sets of eyes before yours.
A second reviewer checks the stack. Brand QA and a human approval sit in front of every piece.
-
Retested when models change.
When an AI model updates, we re-run the tests built to trip it up. Every change is versioned and logged.
Questions
Questions about ContentEngine.
What is ContentEngine?
ContentEngine is an AI content system that FieldSignal builds and installs for your organization. It turns one approved Knowledge Stack (your positioning, audiences, offers, proof and rules) into working skills for social, blog, email and campaign planning, with a Brand QA check in front of anything published.
It runs inside the AI tools your team already uses: Claude, ChatGPT or any MCP client.
How is ContentEngine different from using ChatGPT or Claude on its own?
A general-purpose assistant knows the internet. It doesn’t know your brand. ContentEngine gives it your approved knowledge, your voice and your rules, then tests it before your team relies on it.
The result sounds like you on the first draft. When it doesn’t know something, it says so instead of filling the gap.
Which AI platforms does ContentEngine work with?
Claude as a plugin, ChatGPT as a Custom GPT, and any MCP client, including OpsEngine. You choose the platforms at kickoff, and only those get built and tested.
What does the build involve?
Eight steps with four sign-off gates: a fit check and kickoff, a first look with three sample posts, an intake check (ten questions at most, Gate 1), building the Knowledge Stack, a second reviewer’s Stack QA (Gate 2), an Engine Review where your approver signs off and the engine locks at version 1.0 (Gate 3), building and testing on each platform to 90% or better with no failed trap tests (Gate 4), then recorded training and handoff with two weeks of hypercare.
How much of my team’s time does it take?
Roughly six hours for your main contact, three hours for your approver and about two and a half hours per creator. Most of that is reviewing drafts we’ve already prepared, plus recorded training.
What happens when our offers or messaging change?
Changes go through the master. We update it, validate it, rebuild, retest the affected tests and every trap test, then redeploy. Bigger changes, like a new offer, a new audience or a rewrite of your voice, get a fresh Engine Review before they go live.
Will ContentEngine make things up?
It’s built not to. The engine writes only from approved knowledge, marks anything it can’t confirm as [NEEDS CONFIRMATION], and has to pass its trap tests before handoff. Brand QA and a human approval still sit in front of everything that gets published.
Are there add-ons?
Yes. The Image Prompt add-on gives the engine a visual director for on-brand image prompts. Compliance packs for US FTC rules, Canada’s Competition Act, the EU AI Act and platform AI labels stay off unless you switch them on. They summarise public rules so the engine stays conservative; they aren’t legal advice.
Who is ContentEngine for?
Marketing teams that need more content than they have hands for and can’t let the brand slip: professional services firms, startups and tech companies, nonprofits, and in-house marketing teams at mid-sized and larger businesses.
Talk to us
Tell us what’s stuck.
Tell us where content slows down: drafting, approvals, voice, or keeping up across channels. We’ll tell you straight whether ContentEngine fits.