What this post is. An illustrative worked example, not a client result. The 12-person B2B SAAS marketing team and its numbers are assumptions. The design is a content-production system on Claude and Airtable: drafts from a structured brief, with a human editor signing off before anything publishes.
For illustration, assume the team ships two long-form posts a week and wants more. Hiring more writers is the obvious answer, and it is slow and expensive. So they ask a different question. Could AI draft the first version without flattening the brand voice they have built over years?
a note on the numbers: there is no client here. The team, the cadence and any figures are assumptions for illustration. A team in this position would measure time per post and posts shipped per week before and after, and judge the result on its own data.
#What would the system consist of?
A brief-to-draft pipeline. The brief lives in Airtable. Each row holds the working title, the target reader, the key points, and the proof to cite. Claude reads that structured brief and writes the first draft against a brand-voice constraint file. The draft lands back in Airtable in a review column. A human editor signs off before anything publishes.
- Airtable as the brief and workflow layer. One row per post, status moves left to right.
- Claude for drafting. It reads the structured brief plus a voice file with the do-and-don't rules.
- human-review gates. no draft skips the editor. The editor approves, edits, or sends it back.
We are
We design a system that drafts from a structured brief and routes every draft through a human editor before it ships.
We aren't
We do not build a content farm that publishes unedited AI slop on a schedule.
#Did quality drop?
No, if the design holds. That is the point of the voice file and the review gate. The editor still reads every post and still has the final word. What changes is where their time goes. They stop writing from a blank page and start editing a draft that already sounds like the brand. Nothing goes out without a human signing it off.
Can AI increase content output without hurting brand voice?
Yes, when the voice is encoded as an explicit constraint and a human edits every draft. In this example, Claude drafts from a brand-voice file in Airtable and an editor approves each post. Output can rise and the voice can hold, because no draft publishes without human review.
#How would you tell if it works?
Most of the design effort goes into the brief schema and the voice file, not the model. Once the brief holds the right structure, Claude has what it needs. Expect the early drafts to go back to the editor often. As the constraint file tightens, the edits get smaller. The measure to watch is editor time per post, judged against your own baseline.
The writers stop staring at a blank page. They start editing a draft that already sounds like the brand.
For illustration, assume a post takes six hours to produce today. If an editor only has to polish a draft, the time per post falls, but by how much is something to measure, not to assume. This is the kind of work our AI consulting covers, and the marketing team is the one that feels it first.
#Would this work for your team?
It works when you already know your voice and can write it down. It works when an editor is willing to own the gate. It does not work if the plan is to publish whatever the model writes. The constraint file and the review step are not overhead. They are the reason the voice held while the output tripled.
If you're a marketing lead weighing whether AI can move your throughput without losing your voice, this is the shape of the design. Start with the brief, encode the voice, keep the human gate. We do this end to end in an AI implementation engagement. Tell us what you're building and we'll tell you whether this fits. start here.
