Use Case

Creative delivery clients can see and approve in real time

A global professional services and consulting firm orchestrates end-to-end creative delivery for global clients across industries such as financial services and automotive: brief intake and routing, Figma-integrated asset production, multi-round QA and proofing, layered approvals across brand, legal, and regional leads, and localized delivery, all surfaced to external collaborators through client-facing Portals. The workflow replaced manual Excel trafficking sheets running to 1,000 lines, email handoffs, and version control chaos.

The problem

Creative delivery for global clients ran through manual email and spreadsheet handoffs, including copy and paste across trafficking sheets that stretched to 1,000 lines. Every revision risked version conflicts, and clients had no real-time visibility into where their assets stood.

External collaborators needed access without the cost of per-user licensing on heavyweight tools, and feedback stayed fragmented across brands and regions instead of routing through one approval path.

What they built

The firm built a shared Airtable base that runs brief intake and routing through forms, Figma-integrated creative production, multi-round QA and proofing with client feedback loops, and layered approvals across brand, legal, and regional leads.

Client-facing Portals extend the same base to more than 300 external users at a lower cost than per-seat licensing, so clients review and approve work directly instead of waiting on email threads. Content localization and delivery, plus campaign calendar and status tracking, round out the workflow.

The outcome

Email churn and manual setup dropped as trafficking moved into structured records. Creative cycles run faster, workflow execution improved, and time-to-market shortened across client engagements.

SLA adherence on delivery now runs above 95% on time, external collaboration scaled at a lower cost through Portals, and a single source of truth replaced the version control chaos of the old spreadsheet process, improving client satisfaction along the way.

Inside the solution

Client-Facing Creative Production and Approvals with Portals

Content Production & Localization

  • Brief intake and routing via forms and interfaces
  • Figma-integrated creative production
  • Multi-round QA and proofing with client feedback
  • Layered approvals
  • Content localization and delivery
  • Campaign calendar and status tracking
  • Manual email and spreadsheet handoffs including 1,000-line Excel trafficking
  • Version control and duplicate entry
  • Lack of real-time client visibility
  • High cost of per-user licensing for external collaborators
  • Fragmented feedback across brands
  • Reduced email churn and manual setup
  • Faster creative cycles and time-to-market
  • Scalable external collaboration at lower cost via Portals
  • Improved SLA adherence
  • Centralized source of truth and approvals
  • Improved client satisfaction
  • Marketing
  • Creative Services
  • Service Delivery
  • QA
  • Figma
  • Portals
  • Slack
  • Adobe Workfront
Build out this use case

Client-facing creative production and approvals with Portals

Run end-to-end creative delivery for global clients in one base: briefs come in through structured intake, assets move through design, multi-round QA, and layered brand, legal, and regional approvals, and localized delivery is tracked per market, all ready to surface to external reviewers through client-facing Portals. Automations route every new brief into production and flip assets back to Revisions the moment an approver requests changes, while native AI fields summarize briefs, draft QA punch lists, and turn review feedback into designer action items.

Client-facing creative production and approvals with Portals - Overview dashboard
How it works

From spreadsheet trafficking to a client-facing approval workflow

Copy the templates

Start from the digital asset management template above for the production core, then layer in the brand asset management template for regional and brand-level governance.

Add a client-facing Portal

Extend the same base to external reviewers using the client portal pattern, so clients see live status and leave feedback without full editor seats.

Wire the integrations

Connect Figma through a custom plugin for asset production and Slack for notifications, so approvals move without leaving the tools creative teams already use.

FAQ

Frequently asked questions

Clients work through a Portal that surfaces only their own assets and status, so they can comment and approve without a seat on the underlying base or its other client engagements.

A structured intake form feeds linked asset records directly, so trafficking data lives in one place instead of a spreadsheet copied and pasted between teams.

Each asset carries linked approval records for brand, legal, and regional leads, so a single record shows exactly who has signed off and who is still pending.

Portals let more than 300 external users work directly in the base at a fraction of the cost of full per-seat licensing, while keeping their access scoped to only what they need to see.

Not for the core production and approval workflow. The structured asset and approval data built here is well suited to later AI-assisted QA or proofing automation.