Skip to content

Guide

Overview

BrandKind turns a rough idea into a finished, on-brand draft — written in a voice you define, checked before it goes out, and delivered wherever you publish. This guide covers every part of that, from your first session to the webhook payload your CMS receives.

What BrandKind does

You give it a topic and a voice. It writes a draft in one of six formats, scores how well the result matches your voice, rewrites it to read as something a person wrote, and hands you a version you can publish. Nothing needs copying into another tool along the way.

The part that does the writing is a chain of several AI models rather than one. Each stage has a job — drafting in your voice, judging the fit, shaping it for the channel, and a final pass that removes the tells that make text read as machine-generated. You never choose or configure the models; you choose the voice and the format, and the chain is fixed.

Who this guide is for

Anyone who has just been given access and has not used the system before. It assumes you write for a living or manage people who do. It does not assume you know anything about how language models work, and it never asks you to.

If you are integrating BrandKind with another system rather than using it, skip to the Delivery API — it is the full wire contract and stands on its own.

How to read it

The pages are in the order you would meet the features. Reading straight through is a reasonable way to learn the system; the pager at the foot of each page follows the same order.

Start here if you are new

Read Concepts and glossary first. Every term the product puts on screen is defined there, once, and the rest of the guide links back to it rather than re-explaining. Ten minutes there saves you guessing later.

Conventions used here

  • Things you click or type are named exactly as they appear on screen.
  • Field names, values and status words are set in a monospace face when the exact string matters — for example a delivery whose status is failed.
  • Where a feature is limited by your role, the page says so at that point rather than collecting all the permissions somewhere else.
  • Nothing is explained twice. If a page mentions a concept it does not define, the definition is one link away.

Everything in this guide