The Story Behind Conveo
This is where it came from. And why it matters.
The Designer
I've been a designer since the mid-nineties. Started in web design back when web design was still explaining itself to the world — when a website was a novelty and the designers building them were figuring out the rules as they went. Over the years the work evolved. Freelance of every kind. A partnership that took on anything the industry could throw at us. Eventually a role inside a company with a national footprint, managing brand at a scale where the brief either holds everything together or nothing does.
Twenty-five years of knowing what good looks like. Knowing how to get there.
Knowing the language of design well enough to brief anyone — a photographer, a printer, a developer, another designer.
Anyone, it turned out, except AI.
The Project
A few years ago I was tasked with building a large internal microsite. AI governance, resources, project approvals — a significant piece of work for a significant purpose. I went through multiple versions, multiple tools, multiple rounds of revisions. AI tools, design tools, combinations of both. Tweaks that led to more tweaks.
Every version looked the same.
Forced. Generic. Like something that had been produced rather than designed.
The kind of output that could have been built by anyone for any company on any topic.
I knew what was wrong. I just didn't know why it kept happening no matter what I tried.
And then I read four sentences that changed everything.
Four Sentences
I started researching. Not just using AI tools but trying to understand them — taking training specifically on designing with AI, reading everything I could find about how these tools think and what they respond to.
Then I came across a color description in an art direction brief. Four sentences that stopped me completely.
“The blue-black of slate under compression — not the sky, not the sea. The color of igneous rock at depth, where light doesn't reach and pressure does the forming.”
#141B24
I read it twice. Then a third time.
That was a color description. For what most people would call dark blue or dark grey. And in four sentences it communicated something no hex value, no color name, and no generic descriptor ever could. It communicated the weight of the color. The origin of the color. What the color means and where it comes from and how it should feel when you encounter it.
I had been telling AI what colors to use. This was telling AI what a color is.
That was the moment I understood what the problem actually was. Not the AI tools. Not my design instincts. Not the quality of my direction. The problem was communication. AI had been trained on a vocabulary I wasn't using. A precise, layered, specific vocabulary for describing visual and emotional qualities that went far deeper than anything I had been putting into my prompts.
I had been speaking to AI in shorthand. AI needed the full language.
So I started asking questions.
The Questions
I started asking questions. Hundreds of them. How would you describe this color? How would you characterize this typeface? What language would you use to direct an image with this mood, this atmosphere, this specific quality of light?
I wasn't building a product yet. I was having a conversation.
But without realizing it I was doing something more significant — I was mapping the vocabulary. Learning the language that sits between a designer's visual instinct and an AI tool's ability to execute it. Building a dictionary that had never been written down because no one had needed it until now.
Four to six weeks of questions, answers, and accumulating understanding. And at the end of it something had taken shape that was more than research.
It was the foundation of Conveo.
What Everyone Else Missed
There are plenty of tools that promise to solve the AI brand problem.
All of them producing the same result.
Faster generation. Better templates. More options. Smoother interfaces. All of them producing the same result — brand documents that could belong to anyone, because the AI generating them had no structured intelligence about this specific brand before it started.
They made generic output faster. They didn't make it specific. The problem was never speed. The problem was communication.
Not how do I get AI to produce a brand document faster. But how do I tell AI exactly what this brand is — with enough precision, enough specificity, enough of the right vocabulary — that the output could only belong to this brand. That's a completely different question. And it required a completely different solution.
Why Conveo Exists
I built Conveo because I needed it.
Conveo doesn't ask AI to do the brand thinking. It does the brand thinking first — a structured discovery process that extracts the specific intelligence about each brand, translates it into the precise vocabulary AI tools respond to, and assembles it into prompt blocks the designer can use immediately in any AI tool of their choice.
The positioning. The personality. The emotional world. The visual language. The things a brand is and the things it categorically is not. All of it worked out before a single prompt is written. All of it expressed in the language that produces specific output rather than generic output.
The result is brand direction that belongs to one brand. Not a template dressed up as strategy. Not the most common version of what you asked for. Something that could only be this brand — because the intelligence behind it was built specifically for this brand.
Conveo is the answer I built when I couldn't find it anywhere else.
That's the only reason any good tool gets built.
Ready to build your first brief?
Start Now