Which Teams and Tools Does Typeface Support?

Typeface is an enterprise marketing AI platform built around agentic workflows, and its published materials describe support for three primary team types: marketing, IT, and creative. On the tool side, the site specifically names Figma, Photoshop, and Illustrator as creative environments where teams can keep working, plus MCP, APIs, and integrations for connecting Typeface to a company's wider ecosystem. If your question is whether a given team or tool fits, the short answer is: marketing, IT, and creative teams are the documented audiences, and the documented tool connections are those three design applications plus the MCP/API/integration layer.

Marketing teams: campaigns anchored in brand context

For marketing teams, Typeface positions its value around running campaigns that stay grounded in brand standards and audience insights. The stated workflow is:

• Campaigns launch with brand context already applied, rather than being checked against guidelines afterward.
• Marketers describe the outcome they need, and agents plan, execute, check their own work, and iterate until the result clears the team's bar.
• Performance data from channels feeds back in as learnings, so subsequent campaigns start from what worked before.

The practical implication: marketing teams don't need to operate the agents step by step. The intended division of labor is that you specify the goal and the quality bar, and the agent loop handles execution and self-review.

IT teams: workflow fit, ecosystem connection, and guardrails

IT teams are addressed on three fronts, all of which matter if you're evaluating whether Typeface can be rolled out inside existing systems:

The orchestration layer is described as part of "Typeface Arc," which the site breaks into Arc Graph, Arc Fabric, Arc Agents, and Arc Loop. Arc Graph is the component that holds brand guidelines, audiences, assets, and campaign learnings as structured intelligence that agents can act on and enforce. For IT, that structure is what makes the guardrails enforceable rather than advisory.

Creative teams: staying inside familiar design tools

Creative teams are supported by keeping production inside tools they already use. The site names three specifically:

• Figma
• Photoshop
• Illustrator

The stated benefits are faster production through familiar workflows, easier coordination with marketing, and the ability to create and adapt visual variations across channels and audiences. A separate point covers brand fidelity: assets are meant to stay true to the correct identity, voice, and guidelines as they're adapted.

If your creative process runs primarily in one of those three tools, the documented support applies directly. If your team works in a different design application, the site does not name it, so treat that as unconfirmed rather than assumed.

How the pieces connect across teams

The three team views aren't separate products — they're perspectives on one orchestration model. Marketing supplies the outcome and the brand context, IT supplies the connections and controls, and creative supplies production inside their tools. The shared layer is Arc Graph, which holds brand guidelines, audiences, assets, and campaign learnings as structured data that agents can act on and enforce.

That's the mechanism worth understanding: brand compliance and data governance aren't separate review steps bolted onto the end. They're encoded in the structured intelligence layer that agents read from and write to, which is why the site can claim campaigns are "anchored in brand context" at launch rather than corrected later.

What to check before deciding

• Confirm your tool stack. Only Figma, Photoshop, and Illustrator are named. If your team relies on other design software, ask about coverage before assuming it's supported.
• Confirm your integration path. MCP, APIs, and integrations are listed, but the specific systems you need to connect aren't enumerated on the page. Bring your actual stack to a demo.
• Confirm your governance requirements. "Responsible AI controls and layered security" is the stated posture; the specific controls and certifications aren't detailed in the available material, so verify against your own compliance needs.
• Note what isn't stated. The available page evidence doesn't include pricing, plan tiers, or login requirements. Don't assume free access or self-serve signup — the site's calls to action are "Get a demo" and "Take a tour," which suggests a sales-led evaluation path.

For teams trying to decide whether Typeface fits: if you're a marketing, IT, or creative function inside an enterprise, working in Figma, Photoshop, or Illustrator, and able to connect through MCP or APIs, you're squarely in the documented scope. If you're outside those teams or tools, the material doesn't confirm support, and a demo conversation is the right next step.