Sales ops · Production

Delphi builds premium client-facing assets in minutes with Mutiny

The problem

Delphi's go-to-market team needed to deliver personalized, premium client materials but creating them was slow, manual, and repetitive — custom landing pages required hours in Figma and Framer, generic documents undersold the premium product, and a whole tier of client assets never got made due to the execution bottleneck.

First attempt

AI tools like Gamma and Claude Cowork evaluated before Mutiny could reach only roughly 75 percent of the desired quality, and getting the rest required so many iterations and manual corrections that the time savings evaporated.

Workflow diagram · grounded in source
1
Brand identity extraction
Ai action
Mutiny automatically extracts brand identity including fonts, colors, logo, and visual style from the company website.
source quote
“the platform extracted the brand identity, including fonts, colors, logo, and visual style, automatically”
2
Content pull from Notion
Integration
The team pulls content from Notion and describes what the asset needs to cover.
source quote
“The workflow: pull the content from Notion, describe what's needed”
3
Branded asset generation
Ai action
Mutiny generates a polished deliverable that matches Delphi's visual identity.
source quote
“Mutiny generates a polished deliverable that matches Delphi's visual identity”
4
Client-ready asset delivery
Output
Polished, client-ready branded assets are presented to or sent to clients.
source quote
“Within his first session, Basten had polished, client-ready assets”
Reported outcome

What used to take two to three hours in Figma now takes roughly three minutes in Mutiny, saving the team up to 20 hours a week and unlocking a new category of client assets the team could not previously justify creating.

Reported metrics
Hours saved per week on deal collateral20+
Time to create custom client landing page5 minutes
Design or dev resources required$0
asset creation time reduction vs. Figmatwo to three hours in Figma now takes roughly three minutes
Show all 6 reported metrics
hours saved per week on deal collateral20+
time to create custom client landing page5 minutes
design or dev resources required$0
asset creation time reduction vs. Figmatwo to three hours in Figma now takes roughly three minutes
weekly time savingsup to 20 hours a week
quality ceiling of previously evaluated AI toolsroughly 75 percent
Reported stack
MutinyNotionFigmaFramerGammaClaude Cowork
◆ Does this fit your context?

Compare to your context

Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.

Compare to your context →
~30 seconds · free
Source
https://www.mutinyhq.com/case-studies/delphi-builds-premium-client-facing-assets-in-minutes-with-mutiny
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

What used to take two to three hours in Figma now takes roughly three minutes in Mutiny, saving the team up to 20 hours a week and unlocking a new category of client assets the team could not previously justify creating.

What tools did this team use?

Mutiny, Notion, Figma, Framer, Gamma, Claude Cowork.

What results were reported?

Hours saved per week on deal collateral: 20+; Time to create custom client landing page: 5 minutes; Design or dev resources required: $0; asset creation time reduction vs. Figma: two to three hours in Figma now takes roughly three minutes (source-reported, not independently verified).

What failed first in this deployment?

AI tools like Gamma and Claude Cowork evaluated before Mutiny could reach only roughly 75 percent of the desired quality, and getting the rest required so many iterations and manual corrections that the time savings e…

How is this sales ops AI workflow structured?

Brand identity extraction → Content pull from Notion → Branded asset generation → Client-ready asset delivery.

WHAT TO DO WITH THIS

Now compare it to your context

This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.