Adobe needed B2B content to support the launch of Adobe Express and its integrated generative AI capabilities powered by Adobe Firefly. The agency I freelanced for brought me onto the project because of my previous experience writing for Adobe, my background as an ebook writer, and my familiarity with the Adobe product ecosystem as a longtime user.

The deliverables were a gated ebook, a companion landing page, and, following the success of those assets, content for a Coursera course on the Adobe Firefly and Adobe Express ecosystem.

The Editorial Challenge

Adobe's existing marketing for Firefly and Express was consumer-facing and broad: creative professionals, individual designers, anyone who wanted to make things. The messaging centered on creative possibility and visual impact.

This project required a fundamentally different approach. The target audience was corporate creative teams and the business leaders who manage them: marketing directors, brand managers, and operations leads at organizations where content production is a cross-functional challenge, not a solo creative act. These readers don't need to be sold on creativity. They need to understand how a tool fits into their existing workflows, whether it can scale across departments, and how it protects the brand standards they're responsible for maintaining.

That gap between Adobe's consumer messaging and the needs of this B2B audience was the core editorial problem. I had to take the same product capabilities and reframe them entirely, emphasizing organizational efficiency, brand compliance, team empowerment, and production scalability rather than individual creative expression.

The Inputs

I worked from product documentation, Adobe's existing consumer marketing materials, and recorded interviews with product teams. The consumer materials gave me a clear picture of how Adobe wanted the products to feel. The product documentation gave me the technical specifics. The interviews gave me the internal logic of why these tools were built the way they were and what problems they were designed to solve.

The project's work was concentrated in the translation layer between those inputs and the final content.

The Narrative Decisions

1. Structure. I organized the ebook around the operational problems that corporate creative teams actually face rather than around product features. The opening frames the challenge: content demand is relentless, the ability to react quickly is essential, and delays have real revenue consequences. From there, each section addresses a specific pain point (cross-departmental collaboration, brand consistency at scale, generative AI as a production tool) and shows how Express and Firefly solve it. This meant the reader encounters their own problems first and the product second, which is a more persuasive sequence for a B2B buyer than a feature tour.

2. Audience reframing. Adobe's consumer messaging speaks to "creators" as individuals. The ebook repositions the same capabilities for teams: individual departments creating on-brand onboarding materials, sales teams building customized presentations, and field marketing teams localizing campaign assets for regional offices. Each use case demonstrates that Express isn't only a creative tool; it’s also a tool that creates new opportunities to reduce dependence on overburdened studio teams while maintaining brand standards.

3. Getting ahead of the AI objection. This was the editorial decision I'm most proud of on this project. I knew that corporate brand and legal stakeholders would immediately worry about the intellectual property implications of using AI-generated content in their marketing. Can we use this commercially? What are the rights? What about attribution? This concern wasn't addressed in the brief, the strategy documents, or the materials I was given to work from.

   Despite this, I made an editorial judgment and wrote content specifically addressing this, explaining Adobe's ethical AI training approach (licensed Adobe Stock assets and public domain content), the commercial safety of Firefly-generated outputs, the IP protections available to enterprise customers, and the Content Credentials metadata system that provides transparency and attribution. I flagged the addition in a comment explaining that this was a proactive decision to get ahead of a known objection that would otherwise stall adoption conversations.

4. How-to sections as proof. Rather than ending at the conceptual level, I included step-by-step walkthroughs showing how to set up brand kits, use branded templates, write generative prompts, and repurpose campaign assets using Quick Actions. These sections serve a dual purpose: they demonstrate the product's ease of use and provide the reader with something immediately actionable, increasing the likelihood that the ebook will be saved, shared, and referenced rather than skimmed and forgotten.

The Landing Page

The companion landing page needed to function as both a product overview and a conversion point for the gated ebook. The copy positions Firefly's generative AI capabilities within the broader Adobe creative ecosystem (Photoshop, Illustrator, Lightroom, Express) and emphasizes Adobe's "Creators first" commitment, which differentiates its approach to AI from competitors. The page balances product specificity with brand-level messaging, guiding visitors from awareness through to the ebook download without reading as a hard sell.

The Outcome

The client's response confirmed that the editorial decisions were the right ones. The proactive addition of the AI safety and IP content was singled out as exactly what the audience needed to see, and the ebook required no substantive revisions. Following the success of the ebook and landing page, the agency brought me back to develop content for a Coursera course on the same product ecosystem, extending the same editorial framework into an educational format.

While I don't have access to the downstream performance metrics, the fact that the project expanded in scope is meaningful in itself. Agencies don't extend contracts for deliverables that underperformed.

What This Project Proves

• Product storytelling for AI-native tools requires audience-specific editorial judgment. The same product capabilities that thrill an individual creator can confuse or concern a corporate buyer. The difference is in how you frame the value: operational efficiency and risk mitigation vs creative possibility. That framing decision is editorial, and it determines whether the content converts.

• Anticipating objections is part of the writer's job. A brief tells you what the client wants to say. It doesn't always tell you what the audience needs to hear. Identifying AI rights and safety concerns and writing content to address them before the audience ever raised them shortened the sales conversation and built trust with the stakeholders who would otherwise have been blockers.

• Translating technical capabilities into human-centered narratives is a specific skill. It requires understanding the product deeply enough to know which capabilities matter to which audience, and writing with enough craft to make the connection feel intuitive rather than forced. This project required working across product documentation, consumer marketing, and internal interviews to produce content that was accurate to the technology, appropriate for the audience, and compelling enough to prompt action.