Every brand writes for more than one audience. A SaaS company selling to both SMB ecommerce managers and enterprise CTOs needs different messaging for each. The pain points are different. The buying triggers are different. The objections are different. But the brand voice stays the same.

Until now, handling this in RequestDesk meant creating separate brand personas or stuffing audience details into freeform sections. Neither approach scaled well. You either duplicated your entire brand voice for each audience, or you lost the structured data that makes targeting useful.

ICP as a Persona Type

We added Ideal Customer Profile as a new persona type alongside Brand, Client, Personal, and Competitor. An ICP persona carries structured fields that describe a specific audience segment:

• Industry and company size (ecommerce, SaaS, mid-market, enterprise)
• Job titles and departments (CTO, VP Engineering, Director of Ecommerce)
• Pain points (platform migration headaches, scaling bottlenecks)
• Buying triggers (contract renewal, competitor switch, new funding round)
• Goals (reduce cart abandonment, improve site speed)
• Common objections (budget constraints, switching costs)
• Preferred channels (LinkedIn, email, webinars)

These fields are typed and filterable. When you need to know which ICPs target mid-market SaaS companies, you can query for that directly instead of searching through freeform text.

Mix and Match with Brand Voice

The key design decision: ICPs are independent from brand personas. You assign both to an agent. The brand persona controls voice and tone. The ICP controls who you are writing for.

One Content Cucumber agent might have:

• Brand persona: Content Cucumber (voice, values, style guide)
• ICP 1: Mid-market Ecommerce Director (pain points around scaling, goals around conversion)
• ICP 2: Agency Owner (pain points around client retention, goals around recurring revenue)

When the agent generates content, it gets both the brand voice context and the ICP targeting context injected into the prompt. The output sounds like Content Cucumber but speaks directly to the audience segment you selected.

How It Works in Practice

Create an ICP persona the same way you create any persona. Select Ideal Customer Profile as the type, and the form shows the structured fields. Fill in what you know. All fields are optional, so you can start with just industry and pain points and add more detail as you learn about the segment.

Assign the ICP to an agent alongside your brand persona. When that agent generates blog posts, social content, or case studies, the structured ICP data gets included in the LLM context. The content naturally addresses the right pain points, speaks to the right job titles, and handles the right objections.

The persona list now supports filtering by type, so you can view just your ICPs without scrolling through brand and client personas. Each ICP shows an amber badge in the list and on the agent persona manager, making it visually distinct from other persona types.

What This Replaces

Before this update, audience targeting lived in freeform persona sections. You could write Target Audience: mid-market ecommerce directors dealing with platform migration in a section, and the LLM would pick it up. That still works. The ICP type adds structure on top of that flexibility.

The structured fields make ICPs queryable, comparable, and consistent across your team. When someone new joins your content operation, they can look at the ICP fields and immediately understand who each piece of content targets, without reading through paragraphs of persona text.

Getting Started

Go to Personas, click Create, and select Ideal Customer Profile as the type. Start with one ICP for your primary audience segment. Fill in the pain points and goals you know best. Assign it to an agent alongside your brand persona and generate a test piece of content.

If the output addresses the right problems in the right voice, add more ICPs for your secondary segments.