One content calendar for every brand in the portfolio , no more ad-hoc requests
A multi-brand shipping and e-commerce software company replaced fragmented tools across Slack, Google, Confluence, Jira, and multiple project management platforms with Airtable, managing roughly 60 active content pieces across its brand portfolio from a single source of truth.
The problem
Content and marketing teams at a multi-brand shipping and e-commerce software company managed content production across a collection of disconnected tools: Slack for conversations, Google for drafts, Confluence for documentation, Jira for tickets, and several project management platforms for task tracking. With each brand operating in its own silo, there was no company-wide view of what content was in flight, what had been approved, or what was scheduled to publish.
Partner and outreach teams had no reliable way to see what content existed without filing a ticket or sending a Slack message. Reactive intake made forward planning difficult, quarterly theme alignment required manual collation, and leadership had no consolidated rollup of monthly activity across the brand portfolio.
What they built
The company deployed Airtable as the single source of truth for content production across its brand portfolio. Content items are logged with status tracking, brand-specific views, publish dates, and quarterly theme assignments. Approval routing and review queues replaced ad-hoc Slack requests, and automations push Slack digest notifications so stakeholders receive updates without checking the base manually.
Confluence-embedded views give partner and outreach teams self-serve access to the content library without exposing internal fields. Each of the company's consumer brands gets its own filtered editorial calendar view, and leadership receives monthly activity rollups without requiring manual report assembly.
The outcome
Content teams eliminated the reactive, ticket-based intake model that had previously consumed significant coordination time. With approximately 60 active content pieces visible in one place, editorial planning shifted from reactive to proactive, and quarterly theme alignment across the brand portfolio became a structured process rather than a manual exercise.
Stakeholders and partner teams now access the content library directly from Confluence without filing requests or waiting for replies. Leadership has reliable monthly rollups from live data, and approval routing through Airtable reduced the back-and-forth that previously fragmented review cycles across multiple tools.
Inside the solution
Cross-brand content production and editorial calendar
Content Production & Localization
- Content item logging and status tracking across the brand portfolio
- Brand-specific editorial calendar views
- Confluence-embedded public content library for stakeholder self-serve
- Quarterly theme planning and alignment
- Approval routing and review queues
- Fragmented tools across Slack, Google, Confluence, Jira, and multiple project management platforms
- No stakeholder-friendly views without exposing internal fields
- Reactive ticket-based intake instead of proactive planning
- Cross-brand visibility gaps and manual re-entry
- Single source of truth for content across the brand portfolio
- Organization-wide visibility and self-serve stakeholder access
- Time saved through automations and reduced manual work
- Leadership metrics and monthly activity rollups from live data
- Content Marketing
- Social Media
- Product Marketing
- Creative Services
- Communications
- Confluence
- Slack
- Jira
Cross-brand content production and editorial calendar
Run one editorial calendar for every brand in your portfolio: log each content piece with its brand, publish date and quarterly theme, route it through named review stages, and give partner teams a read-only library view that hides your internal notes. Automations convert accepted intake requests into calendar items, open the final approval when a piece is approved, and send a Monday digest of everything scheduled, while Airtable AI drafts stakeholder-safe summaries, intake triage notes and the monthly leadership rollup.
How the company manages content across its brand portfolio
Log and track content items across brands
Route approvals and automate digest notifications
Embed the library in Confluence for stakeholder self-serve
FAQ
Frequently asked questions
Each content item is tagged with a brand assignment and status field. Brand-specific views filter the base to show only that brand's content, giving each team its own editorial calendar without duplicating records or maintaining separate bases.
Yes. Airtable's shared views let teams publish filtered, read-only views to Confluence that show stakeholders the information they need without exposing internal status fields, owner notes, or approval comments.
Review queues in Airtable move content through defined stages: draft, in review, approved, and scheduled. Airtable automations trigger Slack notifications or email alerts at each stage transition, replacing manual follow-up.
Airtable became the single base for content logging, status tracking, approval routing, and calendar views. Slack and email integrations carry notifications out from Airtable rather than being the place where editorial decisions are made.
Quarterly theme fields are added to each content record so planning views can group or filter by theme across all brands. This gives content leads a company-wide view of upcoming content by theme without manually collating spreadsheets.