Javeria built brands by hand for V1. Saffi built the engines that do it with you.
“The pain cards on the homepage are my old to-do list.”
Javeria ran Repic's V1 by hand – building brand voices, scripting reels, shipping content one client at a time. She leads content and brand: everything the studio generates is measured against the taste she built the hard way.
“If it can't show you what it's using and ask before it acts, it doesn't ship.”
Saffi built the engines – the Brand Persona resolver, the five creation pipelines, and the Allow/Disallow permission gate that keeps the assistant honest. That rule above applies to every feature.
Hover a founder to bring them forward
Nobody here does one job. These are the four positions the work actually needs, and who holds them.
Voice, taste and the judgement about what is on brand.
The models, the pipelines and everything that has to not break.
What ships, in what order, and what gets cut.
Support, onboarding and the replies you get from a person.
Every feature earns its place by being something we rely on ourselves – no shelf-ware, no demo-only buttons.
We show queued and rolling out. We'd rather tell you the truth than fake a screenshot or a user count.
No support tier between you and us. The two people who built it answer the email – usually within two working days.
The founder note on the homepage is signed by the same people who answer the contact form. Read the longer story on the About page, or our rules for AI on Trust.
1 min read · 3 sections
There are two of us, and the division is real rather than decorative. Javeria built brands by hand for our previous product: the palettes, the type pairings, the voice that made a body of work read as one thing. Saffi built the engines that now do that with you, and the infrastructure they run on.
That split is why the product has the shape it has. The brand model was designed by somebody who had done the work manually and knew which decisions actually recur, rather than by inferring a data model from what an API could accept. And the honesty constraints, real statuses, no fake progress, no invented capabilities on a marketing page, come from having been on the other side of tools that did the opposite.
Practically, it means the person answering your email is one of the two people who can change the thing you are emailing about.
One of the two of us. There is no tier, no queue routing and no outsourced first line, which is a consequence of the team size rather than a policy we could keep at scale.
No. It is the thing we are building, and it is why support answers come from the people who wrote the code rather than from a support tier.
