Notes from the studio
Consent-first voice cloning, explained
How Repic gates voice cloning behind recorded consent, own-voice-only.
Saffi & Javeria · 4 min readAlso in the journal
02The style guide nobody opens, and what replaces itAug 2026 · 5 min03A template solves layout. It cannot solve the thing that is wrongAug 2026 · 5 min04AI brand consistency: why generated content drifts and what fixes itAug 2026 · 9 min05Nine questions to ask before anything clones your voiceAug 2026 · 7 min06AI twin vs AI avatarJul 2026 · 5 min07Best AI branding tools in 2026, ranked honestlyAug 2026 · 9 min08Brand drift, and how to catch it before your audience doesJul 2026 · 7 min09We generated twenty brand kits and measured what industry actually changedAug 2026 · 8 min10Content pillars are not content categoriesAug 2026 · 5 min11What you can actually finish without signing upAug 2026 · 6 min12How to build a brand kit in 2026Aug 2026 · 9 min13How to define your brand voiceJul 2026 · 6 min14How to read a comparison page, including oursAug 2026 · 8 min15The on-brand content checklist: 12 checks before you publishAug 2026 · 9 min16Personal branding for founders, without becoming an influencerAug 2026 · 9 min17Personal branding when you cannot show your workAug 2026 · 6 min18Why we publish nobody's prices, including our ownAug 2026 · 5 min19What it actually costs to leave a branding toolAug 2026 · 6 min20We measured thirty announcement posts. The problem is not toneAug 2026 · 5 min21Why a checklist catches drift and taste does notAug 2026 · 6 min22Six branding words that are used to avoid a decisionAug 2026 · 8 min23Describing your brand once, instead of explaining it every timeAug 2026 · 6 min24What a brand kit actually isJul 2026 · 6 min25The point where a brand stops being a look and becomes a systemAug 2026 · 5 min26Seven tools that beat us, and exactly what they beat us atAug 2026 · 7 min27Why prompt-per-post content quietly falls apartJul 2026 · 7 min28Writing in a voice that is not yours, on purposeAug 2026 · 6 min2 min read · 4 sections
What the Journal is for
This is not a content-marketing blog and it is not trying to publish weekly. It is where we write down decisions we are actually making while building Repic, in enough detail that the reasoning is checkable rather than just agreeable.
Three subjects come up repeatedly, because they are the three we keep having to think hardest about: brand systems and why a kit is a decision system rather than a folder of assets; consent-first design and what a real gate looks like as opposed to a checkbox; and the failure modes of prompt-per-post content, which is the thing most AI content advice quietly assumes works.
Posts land when they are finished. That is a deliberate trade: four posts we would defend in an argument, rather than forty that exist to hit a cadence.
Step by step, with nothing skipped
Brand systems
What a kit is once you stop treating it as a folder of assets: a palette that says which colour carries a claim, type that says which line is a promise, and a voice spec concrete enough that two people writing separately produce the same brand. The posts here are about the decisions, not the deliverables.
Consent-first design
A real gate versus a checkbox. What it takes to clone a voice or a likeness in a way the person could defend afterwards - who holds the recording, what revocation actually does downstream, and why an ownership claim you cannot audit is not an ownership claim.
The failure modes of prompt-per-post
Most AI content advice assumes a prompt per post works. It does, for about a week: the outputs are individually fine and collectively incoherent, because nothing carries the brand between them. These posts trace how that drift starts and where it becomes visible to an audience.
Written while it is being built
Every post is a decision we were making at the time, with the reasoning left in so it is checkable rather than merely agreeable. That is also why the archive is short and why a post can contradict an earlier one - the later one says so.
Who wrote it, by name
Each piece carries an author with a profile on the team page, not a byline invented for a content calendar. If a post is wrong, there is a person to tell.
Straight answers
How often do you publish?
When a post is done. We would rather have a short archive of things we mean than a long one of things we filled in. If you want a specific topic covered, the founders read every message sent to the contact address.
Who writes these?
Javeria and Saffi, the two people building Repic. Each post carries the author, and the author is a real named person with a profile on the team page rather than a byline invented for a content calendar.