What Is a Forward Deployed Creative?

The term "Forward Deployed Creative" is new, but the problem it solves is not.

Every creative team that adopted a AI creative tool has faced the massive gap between what’s first demoed, and what’s actually possible when faced with a real project with real constraints, pressure, and standards. That gap doesn’t close on its own. The only solution is having the right person guiding adoption, someone who understands both the tool and creative work deeply. 

FLORA built a role around that person. 

We call them Forward Deployed Creatives, or FDCs, and they’re the reason our enterprise customers don't just adopt FLORA; they fundamentally change how their approach to creative work. 

The origin of “Forward Deployed”: what Palantir figured out first

To understand what a Forward Deployed Creative is, it helps to understand where the model comes from.

Palantir pioneered the concept of the Forward Deployed Engineer in the early 2010s. The premise was straightforward: complex software deployed into complex organizations fails without someone bridging the gap between the product and the environment it's being deployed into. Palantir's answer was to send engineers directly into customer teams to build in the field, understand the client's real constraints, and feed that knowledge back into the product. At one point, Palantir employed more Forward Deployed Engineers than traditional software engineers.

The guiding insight, at the time, was that implementation – when a team puts the tool to work in real ways – is where technology actually succeeds or fails. That translates directly to creative AI, but with one important difference. The wall creative teams hit isn't just, or even mostly, technical. It's actually cultural, aesthetic, and deeply personal.

Why creative AI adoption fails without the right support

Creative teams are not like other enterprise software buyers. Their workflows are actually accumulated instinct, training, taste, and a finely tuned sense of what good looks like. Asking them to integrate a new AI tool isn't a neutral request. It asks them to interrogate something they've built their professional identity around.

No amount of tutorials, docs, or templates can resolve that. The roles that exist to support software adoption — customer success, solutions architecture, technical onboarding — are essential and excellent at what they're designed for: sustaining adoption, managing the relationship, keeping the product working. But they weren't designed for the moment before all of that, when a creative team has to decide whether to actually change how they work. That moment requires someone with genuine creative credibility and product context to walk them through how a tool like FLORA would work for their specific use cases. 

What is a Forward Deployed Creative, and what do they do? 

A Forward Deployed Creative is a senior creative professional whose credibility comes from having done the work, not studied it. They've navigated agency briefs, client pressure, and production deadlines. That background is what lets them sit alongside a creative team and figure out together how AI fits into how they actually make things. They build alongside the team, in their environment, on live projects, and stays engaged long enough to know whether it worked.

In practice that looks like: mapping where a creative team's current process breaks down, identifying which workflows solve real problems for their specific outputs, building custom solutions calibrated to their aesthetic standards and approval processes, and staying in the relationship long enough for the change to stick.

The credibility piece is not incidental. Catherine Chung, one of FLORA's Forward Deployed Creatives, spent three and a half years at Pentagram before joining the FDC team. When she sits down with a brand designer, she's one practitioner talking to another about how the work gets done. That changes the conversation entirely. As Catherine puts it: "The only thing scarier to a designer than having to learn a new tool is learning how to use it from someone who isn't a designer."

How FLORA thinks about Forward Deployed Creatives

This is where FLORA's model diverges from how the rest of the industry is just starting to think about the role. Most companies adopting the Forward Deployed Creative function are treating it as a GTM problem. The FDC lives inside sales and partnerships, the engagement is time-boxed, and the goal is a successful handoff: get the client to the point where they can run independently, then move on. That's a reasonable interpretation of the role.

It's just not what FLORA built.

At FLORA, Forward Deployed Creatives sit across the entire company. They are not a service tier. They are a core function that touches product, community, and go-to-market in ways that compound over time.

On the product side: FDCs test new model releases against real creative standards, not internal benchmarks. They identify where FLORA's capabilities fall short on actual client work and bring that back to the product team with enough specificity to act on. They don't report that "users found it confusing." They report how and why a team loses confidence at a specific step in a specific workflow, and here's what the tool needs to do differently.

On the community side: FDCs build workflows, publish resources, and model what sophisticated creative AI use looks like for practitioners who are still deciding whether any of this is worth their time. They do this because they're practitioners with real opinions about the work, and not because it's a content deliverable.

On the customer side: they do what's described aboveL: embed, build, and stay.

The reason this structure matters is that the problem FDCs are solving is understanding, a continuous, compounding understanding of what creative teams actually need from AI, fed back into everything FLORA makes. An FDC whose only mandate is a successful client handoff will optimize for that. An FDC accountable to the product, the community, and the long-term quality of the work will optimize for something harder and more important.

Why the Forward Deployed Creative model Is the future of creative AI

In 2025, Forward Deployed Engineer job postings grew more than 800%, with companies like Salesforce committing to building a 1,000 person team of them. If the pattern holds, we’ll start to see this same movement on the creative side. As software gets more and more powerful, the end user adoption problem gets even more complex. The teams FLORA works with aren't just adopting new software, they're being asked to reckon with a fundamental shift in how creative work gets made. That's not a technical transition. It's a professional one, and it doesn't happen on anyone's timeline but the team's.

The Forward Deployed Creative is perfectly suited for this moment.