Cinqa/Field Notes/Content
Content · 4 min read · Updated

Our AI content engine for D2C brands: the 4-system stack, tool by tool

The voice fingerprint, brief engine, draft pipeline and distribution formatter behind our D2C content work, with the tools we use and the steps we never automate.

Vaidehi Khunt
Vaidehi Khunt
CEO · Brand & Content
Top-down view of skincare bottles, a phone showing a vertical video and a row of printed photo thumbnails on a walnut table

Why four systems, not one

Most AI content tools treat content as one problem: type a topic, get a post. That's why so much AI content sounds the same. One model and one prompt are being asked to do five jobs at once: find the angle, match the voice, structure the argument, write it, and reformat it for every channel.

We split the problem into four systems, each with its own prompt, its own inputs and its own human check. This is how we structure content work for D2C brands.

System 1: the voice fingerprint

Before anything gets written, we build a voice fingerprint for the brand. It's not a brand voice PDF nobody opens. It's a set of instructions pulled from the brand's best existing content and built into every prompt downstream.

How we build it:

  1. Collect 30 to 50 pieces the founder considers on-brand: captions, emails, product pages, ads that worked.
  2. Run them through an extraction prompt that pulls out sentence length, recurring phrases, how arguments open (hook first or context first), emotional register, and the words the brand never uses.
  3. Write the result into the system prompt itself, not into a separate document someone has to remember to attach.

Every later step inherits it, so nobody types "make it sound like us" again.

System 2: the brief engine

A topic goes in and a structured brief comes out, before a word of the draft is written. The brief includes:

  • One primary keyword and up to three secondary ones
  • The audience segment and the specific problem they have
  • The angle: problem and solution, story, list, contrarian take, tutorial or case study
  • Three pieces already ranking for the topic, and the gap this one fills
  • Must-haves: claims the brand can actually back, product mentions, the call to action

The brief is the spec, and the draft is judged against it. It sounds basic. It's also the difference between content that ranks and content that merely exists.

System 3: the draft and review pipeline

The writing isn't one generation call. It's a sequence:

  1. Outline as structured output: sections, word targets and key points for each.
  2. Outline approval. Two minutes of a person approving or editing it.
  3. Section-by-section drafting, each section written with the one before it as context.
  4. Coherence pass. A second model call reads the whole draft and flags repetition, weak transitions and anything that breaks the brief.
  5. Human edit. Fifteen minutes with someone who knows the brand.

Drafting section by section is the most important choice in the stack. Long single-pass drafts sag in the middle: by the third section the model is repeating itself and the argument has gone soft.

An Indian woman content editor with headphones round her neck reviewing a grid of vertical video thumbnails on a laptop
The human edit is the step we never automate. Fifteen minutes with someone who knows the brand.

System 4: the distribution formatter

An article that only lives on the blog hasn't earned its production cost. Once a piece is approved, the formatter turns it into:

  • A LinkedIn post in the founder's voice
  • An X thread
  • An Instagram caption, hook first
  • A newsletter section
  • A 30 to 45 second short video script with a hook and a payoff

All five come out of one pipeline run, in parallel, and the extra model cost is tiny next to the time it saves. Each one then goes through the same human check as the article.

The stack

  • Orchestration: n8n, self-hosted
  • Drafting and review: Claude
  • Research context for briefs: Perplexity's API
  • Content database: whatever the client already uses (often Notion)
  • Review: a Notion view with approve and reject buttons that trigger n8n webhooks
  • Scheduling: Buffer

None of this is exotic, on purpose. Boring tools are easier to hand over, and the client's team can keep running them after we leave.

What we don't automate

The voice refresh. Every quarter a person reviews what performed and updates the fingerprint. Let the model update its own fingerprint from engagement data and it drifts towards whatever gets clicks, away from the brand.

The outline approval. Two minutes of a person deciding what the brand wants to be known for saves an hour of rewriting later. The model is good at structure. It doesn't know your strategy.

The final edit. A model catches most copy errors. "Most" isn't good enough on content with a founder's name on it.

What a month looks like

The system is sized for roughly 8 long-form articles, 40 social posts, 8 newsletter sections and 8 short video scripts a month. The human time goes into briefs, outline approvals and the final edit, which is exactly where it should go.

The aim was never to take people out of content. It was to take them out of the parts a person shouldn't be doing. If you'd rather point this kind of system at ad creative than articles, that's our bulk ad creative work.

← Back to Field NotesStart a Project →