Innervate
Flow sketch

Create Brand via AI — from upload to confirmed brand

The shape of the flow in five steps. Each box names what happens, who is in the driver's seat, and where it gets genuinely tricky — reasoning behind each decision is in the companion one-page brief.

System-driven Human decides Both Tricky moment
1

Choose a source

Human decides
What happens

Marketer is asked one question — got a document? — then picks: upload a file, point to a live website/socials, or skip straight to a blank manual form.

Who decides
  • Human picks the path
  • No AI runs yet
Tricky moment
No source at allNot every team has a doc or a live site to scan — the manual path has to be a first-class option, not an afterthought bolted on later.
2

AI reads & extracts

System-driven
What happens

Structured facts (logo files, hex codes, font names) and subjective ones (tone, personality) are pulled out, page-linked, and each one is scored high / medium / low confidence — never a raw percentage.

Who decides
  • System proposes everything
  • Nothing is saved yet
Tricky moment
Confident ≠ correctA cleanly-formatted hex code and a contradictory tone claim can both look "confident" on the page — the extractor has to actively check plausibility and cross-reference, not just parse.
Same step whether the source was a document or a website/social scan — a URL-based read just gets a stronger "this is inferred, not documented" caveat downstream.
3

Human reviews & resolves

Both
What happens

High-confidence fields sit pre-approved and collapsed. Anything flagged — a contradiction, a data conflict, a rule with no worked example — sits open, with the source quoted, and a recommended default already selected.

Who decides
  • Human resolves every flag
  • System never auto-picks a side on a real conflict
Tricky moment
Two kinds of "flag"A hex-code mismatch is a data error with a right answer. "Bold, not chaotic" vs. "slightly chaotic" is a judgment call with no right answer — the UI has to ask for different things in each case, not force both into one generic "confirm?" pattern.
4

Confirm & publish

Human decides
What happens

Confirm is disabled until every flag has a resolution. Once pressed, the brand is versioned — every field keeps a link back to the source page it came from, or to the human decision that overrode it.

Who decides
  • Human gives final sign-off
  • System locks & versions the record
Tricky moment
One brand, one workspaceThis flow assumes a single brand per workspace — a regional variant (e.g. an EU version) gets its own workspace rather than living inside this one. Real at enterprise scale, out of scope here.
5

Used as context in the campaign lifecycle

System-driven
What happens

The confirmed brand becomes the default context wherever this brand shows up next: ad-creative generation, creative review & compliance checks, and campaign briefs.

Who decides
  • No new decisions here
  • Every choice from step 3 now enforces itself automatically
Tricky moment
The payoff has to be visibleIf step 4 dead-ends at a "Saved" toast, the value of steps 1–3 never lands. The flow has to visibly hand off into "generate your first creatives" so confirming a brand feels like unlocking something, not filing paperwork.