The team function
What is a team of forward deployed creatives?
A team of forward deployed creatives is the unit a generative-AI platform builds to place its creatives inside client organizations. Each member works hands-on within an enterprise, brand, studio, or agency account, turning purchased platform access into repeat production use, while the team pools what those engagements teach into shared playbooks, templates, and product signal.
Customer, as the hiring listings use it, points at two different organizations. On this page the platform is the employer: the generative-AI company whose product the team represents, currently Adobe, Comfy, ElevenLabs, FLORA, and Luma. The client is the organization a creative deploys into: the enterprise, brand, studio, or agency adopting that product. Platform and client hold those meanings throughout.
This is an independent reference, not affiliated with any company named on this page. It synthesizes the public listings currently defining the team function.
Composition
Three team shapes are visible in current listings
Every platform hiring for this function is hiring the same job: a creative who earns adoption from inside the client's own pipeline. What differs is how much team gets built around that job. The current listings catch the function at three distinct sizes.
- 1
The foundational seat
FLORA, Luma, and ElevenLabs each post a single Forward Deployed Creative, and Comfy posts a single seat under the Technologist form of the title. FLORA, which built the first team under the title, runs its seat from a roughly 45-person company's go-to-market group, split across customer success and sales, marketing, and product feedback in a stated 70/20/10 weighting. Luma's US listing is explicit that the hire is foundational: the first creative writes the partner-engagement playbook the function will run on. ElevenLabs opens one seat globally, remote, serving agencies, studios, brands, and media companies. Comfy's is a San Francisco in-office seat working directly with its founding account executive and go-to-market team.
- 2
The embedded seat with a builder behind it
Luma also posts a London Creative Technologist described in its own listing as "the build engine behind Forward Deployed Creative." The internal seat takes handoffs from embedded FDCs, turns account-specific problems into working workflows, and maintains the demo and customer boards those FDCs run inside client accounts. The deployed creative holds the client relationship; the builder behind them keeps the material current.
- 3
The laddered team
Adobe is hiring Lead, Principal, and Manager Forward Deployed Creative Technologists at once, on a ladder that also carries a Senior Manager level, the only posted evidence of a full career ladder for this function. The Manager listing describes a player-coach who spends about half the week hands-on in code, client rooms, and demos, and the other half hiring and coaching ICs, with pods that pass reusable templates and workflow nodes between them. The Principal seat is specialized by medium, sitting deep in the video pipeline while the Lead spans static, video, and 3D.
Whether a team moves through these shapes in order is more than the listings can show. What they do show is the same function sized three different ways at the same moment, mid-2026.
Placement
Who is hiring, and where the team reports
| Platform | Posted titles | Reports into | Shape as posted |
|---|---|---|---|
| Adobe | FDCT Lead, Principal, and Manager, Forward Deployed Creative Technologist | Listings filed under design and under engineering and product | Laddered ICs and a player-coach manager; medium-specialized principal seat |
| Comfy | FDCT Forward Deployed Creative Technologist | Works with the founding account executive and GTM team; San Francisco, in-office | Single seat spanning pre-sale discovery through production handoff |
| ElevenLabs | FDC Forward Deployed Creative | Department not stated; remote, global | Single seat; the listing's own body also names the hire an AI Creative Director |
| FLORA | FDC Forward Deployed Creative | GTM, New York, on-site | Single seat weighted 70/20/10 across customer success and sales, marketing, and product |
| Luma | FDC Forward Deployed Creative (US), plus an unprefixed Creative Technologist (London) | GTM | Foundational US seat plus an internal build seat supporting embedded FDCs |
- Titles
- Lead, Principal, and Manager, Forward Deployed Creative Technologist
- Reports into
- Listings filed under design and under engineering and product
- Shape
- Laddered ICs and a player-coach manager; medium-specialized principal seat
- Titles
- Forward Deployed Creative Technologist
- Reports into
- Works with the founding account executive and GTM team; San Francisco, in-office
- Shape
- Single seat spanning pre-sale discovery through production handoff
- Titles
- Forward Deployed Creative
- Reports into
- Department not stated; remote, global
- Shape
- Single seat; the listing's own body also names the hire an AI Creative Director
- Titles
- Forward Deployed Creative
- Reports into
- GTM, New York, on-site
- Shape
- Single seat weighted 70/20/10 across customer success and sales, marketing, and product
- Titles
- Forward Deployed Creative (US), plus an unprefixed Creative Technologist (London)
- Reports into
- GTM
- Shape
- Foundational US seat plus an internal build seat supporting embedded FDCs
Go-to-market is where the team clusters when a department shows at all: FLORA and Luma place the seat there, and Comfy's listing has it working with the go-to-market team. Adobe files its listings under design and under engineering and product. ElevenLabs names no department. Published pay for the individual role is tracked on the Forward Deployed Creative reference, and the technologist form has its own reference.
The yardstick
The team is measured on adoption, and says so
Adobe's listings put the metric in six words: "adoption and renewals, not features shipped." The situation behind it recurs across all three of its postings. The deal is signed before the creative arrives, and the editors, designers, and marketers who have to live with the tool never chose it. The team's job is winning them over at their desks, through workshops and live builds, until use repeats without the creative in the room, then handing off so the client runs the workflow themselves. Renewal follows from that usage.
The other platforms weight the same direction without the slogan. FLORA gives customer success and sales enablement 70 percent of the role. ElevenLabs defines the seat around the gap between having platform access and getting production value from it, and asks for the templates and reference work that close that gap. Luma's foundational hire is judged on the playbook: whether client and partner engagement becomes repeatable.
One structural split does run through this axis. Adobe's listings state the team is not pre-sales, while Comfy's seat runs technical discovery on live sales calls and builds the proofs that close the deal before riding the engagement into production. The function spans both arrangements, with adoption as the shared exit condition.
FLORA's own published material on its team describes the same yardstick from the inside: members sit alongside agency and in-house brand teams adopting generative workflows for the first time, working the gap between what the platform can do and how a team actually works, then carrying what they learn back into the product.
Titles
FDC and FDCT split cleanly by company
No platform posts both titles. FLORA, Luma, and ElevenLabs hire the Forward Deployed Creative. Adobe and Comfy use the Forward Deployed Creative Technologist form, and both write code into the entry requirements: Adobe asks for thin front-ends, editor panels, custom workflow nodes, and working integrations, and screens out creatives who cannot build them; Comfy asks for Python strong enough to build custom nodes and debug other people's workflows. The FDC listings set their floor at professional creative craft and daily generative-tool fluency, treating programming as additive; ElevenLabs lists API prototyping as a bonus rather than a requirement.
Five companies make a pattern, not a rule. But as posted, the suffix marks a real requirements difference, and a candidate reading the two titles as interchangeable will misjudge one of them. The technologist form has its own dedicated reference.
The prefix
Dropping "Forward Deployed" moves the seat inside
Both Luma and Adobe also post creative-technologist roles without the prefix, and in both cases the seat comes off the client site. Luma's London Creative Technologist supports the deployed team from inside the company, building from FDC handoffs. Adobe's Creative Technologist for its AI Studio in India operates the automated production workflows behind Adobe's own campaign work, in contact with client counterparts on requirements but working from the production engine. In this set, the prefix marks the seat that lives in the client account; its absence marks the builder behind that seat. Two companies is early evidence, worth watching as more platforms structure their teams.
The engineering parallel
What the team borrows from forward deployed engineering
The operating model is inherited whole from forward deployed engineering as a practice: embed where the work happens, let field contact drive product signal, and compound each engagement into reusable assets so the next one starts further ahead.
The creative team's evidence bends that model at two points. Specialization runs by medium where it is posted at all: Adobe's Principal seat lives in the video pipeline while static and 3D sit with the Lead, and client industries surface in demo libraries, as with Luma's vertical-specific demo sets, sooner than in the team's own structure. And where a department is visible at all, the team sits closest to go-to-market.
Common questions
Frequently asked questions
- What is a team of forward deployed creatives?
- The client-facing creative unit at a generative-AI platform. Members embed inside client organizations, from enterprises and brands to studios and agencies, and build the AI-powered production workflows that turn a purchased platform into the way those clients actually produce. The team pools what each engagement teaches into shared playbooks, templates, and product feedback.
- How is a team of forward deployed creatives different from a team of forward deployed engineers?
- Same embedded model, different material and different neighbors. Engineering teams deploy software builders and organize around industry verticals; the creative team deploys senior creative practitioners into production pipelines, specializes by medium where any specialization is posted, and sits closest to go-to-market at the companies that name a department.
- What is the difference between a Forward Deployed Creative and a Forward Deployed Creative Technologist?
- The employer and the technical floor. FLORA, Luma, and ElevenLabs hire Forward Deployed Creatives; Adobe and Comfy use the Forward Deployed Creative Technologist title and write a code requirement into the listing, from panels and custom nodes to working integrations. The FDC listings ask for professional creative craft and generative-tool fluency first and treat programming as a plus. No company posts both titles.
- Who staffs a forward deployed creative team?
- Senior practitioners from professional creative production who crossed into generative tooling: editors and motion designers with post-production depth, creative technologists and technical directors from agencies and studios, and creative and production leads from brand work. Portfolios of shipped work are an explicit requirement at Adobe, Luma, and ElevenLabs, Comfy asks applicants to submit a built workflow, and every listing asks for hands-on generative fluency.
- How is a forward deployed creative team measured?
- On whether clients keep using what the team builds. Adobe measures adoption and renewal outcomes over delivered features, FLORA weights the role toward customer success and sales enablement, and ElevenLabs defines the seat around closing the gap between platform access and production value. Repeat usage inside the client's own pipeline is the recurring standard.
- Do forward deployed creatives work alone inside client accounts?
- The embedded relationship is typically one creative to one engagement, with team scaffolding behind it. Luma pairs embedded FDCs with an internal creative technologist who turns their account handoffs into working workflows, and Adobe runs pods under player-coach managers with shared template and node libraries, so a creative works solo in the room with the team's accumulated material behind them.
What does "forward deployed" mean, across every role →
Methodology and sources
How this reference is compiled
Compiled from the public listings of the five platforms hiring for this team: Adobe's three Forward Deployed Creative Technologist listings, the Forward Deployed Creative listings at FLORA, Luma, and ElevenLabs, Comfy's Forward Deployed Creative Technologist listing, and the adjacent creative-technologist listings Luma and Adobe post without the prefix. FLORA's own published material about its team informs emphasis, not definitions. Team-shape statements restate what the listings publish. Where a claim rests on the full set rather than a single listing, it is stated as a pattern and held to that weight. Coverage is updated as listings change.