Skip to content
Space
Back to notes
Artificial IntelligenceCreative

Your Client Knows It When They See It. We Built an AI That Decodes Why.

The Taste Decoder is Space's AI system that reads every approved and rejected piece of creative, extracts the unspoken principles behind the decisions, and turns them into a playbook. The result: fewer revision rounds, faster approvals, and clients who feel understood.

Nathan Roth
Nathan RothCo-founder
The Taste Decoder

TL;DR

  • The Taste Decoder is a Space-built AI that reads every approved and rejected piece of creative, extracts the unspoken principles separating them, and hands the team a playbook.
  • It was born with a founder-CEO who could only say yes or no to ad copy; after the Decoder extracted his principles, nearly everything in the next round got approved.
  • The CEO agreed with most extracted principles immediately, including patterns he had never consciously recognized in his own decisions, and every playbook is validated by the decision-maker before use.
  • It compresses the two years of osmosis agencies traditionally need to learn a client's taste into an afternoon, and it runs even when feedback is clear and specific.
  • Clients get fewer revision rounds, faster approvals, and lower cost, but the Decoder only articulates judgment; it cannot resolve conflicting rubrics or supply taste where none exists.

The most expensive sentence in creative work is "I'll know it when I see it." It isn't a difficult-client problem; it's a human one. Taste is real, decisive, and mostly inarticulate, which is why revision rounds exist: the team guesses, the decision-maker reacts, and everyone burns a week per guess. Space built a system for this. We call it the Taste Decoder, and it turns a pile of yes/no reactions into the principles that were driving them all along.

The case that created it

A CEO and founder was reviewing ad copy. He couldn't give high-level direction up front, but he was extremely decisive piece by piece: yes, no, yes, no. After a round, the team had plenty of data on what he liked and none on why, which meant the next round would be another guess wearing a strategy costume.

So we built an agent that read every approved ad and every rejected ad, found the correlations, and extracted first principles from the patterns: here's what the approved work has in common, here's what the rejected work has in common, and here are the underlying rules that separate them.

The writers ran the next round against that playbook. Nearly everything got approved. And when we showed the CEO the principles the system had extracted, he agreed with most immediately; the rest were patterns he hadn't consciously recognized in his own decisions but, seeing them articulated, believed to be true. The system had decoded his taste better than he could describe it himself.

Why taste resists articulation

Nobody's holding out. Decision-makers with great instincts are running pattern recognition built from years of exposure, and pattern recognition doesn't come with a printout. Ask someone to state their creative principles in advance and you get generalities ("bold but not gimmicky") that fail to predict a single actual decision. But every approval and rejection is a data point where the real principles briefly surface. Enough data points, read carefully, and the invisible rubric becomes a visible one.

Agencies traditionally solve this with tenure: after two years, the account team just knows what the client likes. That's real, and it's slow, expensive, and it walks out the door when the team rotates. The Decoder compresses two years of osmosis into an afternoon and writes it down.

How it runs now

The Taste Decoder is standard on Space engagements, and here's the part that surprised us: we use it even when feedback is specific and articulate. Clear feedback has unspoken patterns too, preferences operating beneath the surface, principles the person holds but has never put into words. The Decoder catches those and turns them into a shared language between the client and the creative team.

The extracted principles never ship as gospel. They go back to the decision-maker for a yes/no of their own, which takes minutes and does something valuable beyond validation: the client sees their own taste articulated, often for the first time, and the whole relationship starts operating on stated principles instead of guessed ones.

What it changes for clients

Fewer rounds, because round two aims at the actual target. Faster approvals, because the work arrives already inside the rubric. Lower cost, because revision cycles are where budgets quietly die. And something harder to price: the experience of being deeply understood without having had to explain yourself perfectly, which is what every client of every agency actually wants and almost never gets.

There's an internal benefit too. Creative teams do their best work with a real brief, and "make it more like the ones he liked" is not a brief. Give writers and designers the decoded principles and they stop defensive-designing toward the middle and start taking confident swings inside known lines.

The honest limit

Decoded taste is a map of one person's judgment, and organizations have more than one person. When the CMO's rubric and the CEO's rubric conflict, no agent resolves that; it's a governance decision, and surfacing the conflict explicitly is itself half the value. The Decoder also can't supply taste where none exists. It articulates judgment; it doesn't replace it, which is the same rule that governs every system in our AI-native stack: the machines make the humans legible to each other, and the humans still make the calls.

Frequently asked questions

What is the Taste Decoder?
A Space-built AI system that analyzes every approved and rejected piece of creative in an engagement, extracts the unspoken principles separating them, and produces a playbook the creative team and client validate together. It runs as standard on Space engagements.
How does it reduce revision rounds?
By replacing guesswork with decoded principles. Instead of inferring direction from reactions, the team writes and designs against the actual patterns in the decision-maker's approvals, so subsequent rounds land inside the rubric on the first pass.
What if the client gives clear, specific feedback?
The Decoder runs anyway. Even articulate feedback carries unstated patterns and preferences; extracting them builds a shared language that makes every future round faster.
Does this replace creative judgment?
No. It articulates the client's judgment so the team can aim at it, and every extracted principle is validated by the decision-maker before it's used. Taste stays human; the Decoder just writes it down.
What's a real example of it working?
A founder-CEO reviewing ad copy could approve and reject decisively but couldn't explain his logic. The Decoder extracted his principles from the pattern of decisions; the next round of work was written against them and nearly everything was approved, including principles he hadn't consciously known he held.

hi, i'm Cleo, the Space AI. ask me anything about our sprints, the services we run, pricing, or the work we've shipped.