ContentCal: from spreadsheet chaos to a marketing operating system

I joined Concept Dash as a graphic designer. My job was supposed to be creating content. Working with the social media team, I noticed something else: they weren't struggling to create content, they were struggling to organise everything around it.

The first problem sounded simple: "we're using too many spreadsheets". Looking closer, the whole marketing workflow had become fragmented.

I started with the smallest useful version: a visual content calendar where posts could be created and moved around easily. I studied how established planning products handle scheduling and built around drag-and-drop cards, calendar-based planning, structured post information, visual status and platform-specific views.

The team responded well, and the MVP immediately raised better questions. Those questions became the roadmap.

There wasn't one social channel; there were several, Instagram, LinkedIn and eventually multiple regional accounts. Instead of separate systems, I built a unified experience with a platform switcher between account-specific calendars.

Concept Dash works across regions with different strategies and audiences. I added workspace and calendar switching so one product adapts to each regional workflow instead of pushing the team back into separate spreadsheets.

As more people used it, not everyone should be able to do everything. Once the product grew from a personal planning tool into a team system, role-based access control became essential, and role-gated approvals and team governance are now a core capability.

Then I noticed an unrelated workflow. Senior management attends trade shows and industry events, but tracking them was manual: spreadsheets management had to dig through, and event details the content team needed for campaign planning.

Rather than making the researcher re-type an existing spreadsheet, I designed an import workflow. Management gets a shareable public link, so they can review events without an application account.

The next question: why research the same kinds of events by hand every time? I designed an automated workflow that scrapes relevant trade-show and event information and populates the system by region, turning a recurring manual task into an automation problem.

One of the most repetitive parts of the day: content cards constantly needed links to creative assets that lived in SharePoint. It was a textbook case of unnecessary context switching.

So I asked why the user should leave the product to find the asset at all. I worked with the organisation to get access to the relevant SharePoint resources and connected them through APIs, so assets can be reached from inside ContentCal. That removed one of the team's most common tab-switching loops.

With multiple calendars, someone working across the team doesn't want to see everything. They want to know one thing: what do I need to do? I added a My Tasks view that aggregates everything assigned to a person across all calendars, turning the calendar from a planning system into a personal execution system.

With the operational foundation in place, I asked which parts of content work were predictable enough to automate. Captions were the obvious first candidate. A user describes the post and gets multiple caption variations across different voice directions, then picks the one closest to the brand's tone.

The goal wasn't to remove the content team. It was to cut the repetitive first-draft work.

Planning a month across several regions means juggling dates, platforms, campaign objectives, regional strategy, content types, frequency and product launches. I built an AI planning workflow directly into the calendar that turns a natural-language brief into a structured, placed content plan, so nobody starts from an empty month.

A brief can be as simple as: "Create posts for Monday, Tuesday and Friday for the next month. We are launching a SaaS product in this region. Focus on awareness first, then education, then conversion."

The team runs an Instagram news channel that needs frequent updates. News moves fast; graphic production doesn't. So I designed a pipeline that goes from credible sources to a finished post, using predefined visual templates for headline structure, image placement, typography, overlay, gradient and hierarchy, so every post comes out in a consistent format instead of a new design each time.

Scheduled GitHub Actions jobs trigger it on a recurring basis and it publishes through the platform's API.

As the system grew, publishing couldn't just happen automatically; people needed control. I designed a six-stage content lifecycle with role-gated progression, which gives a clear answer to "who owns this post?" and "can this be published yet?"

What began as "let's replace our Excel content calendar" became "let's build the operating system for the marketing team", because every feature came from an observed problem, not a predefined roadmap.

There was never a complete specification. The users effectively shaped the product while it was being built.

The hardest engineering problem was keeping all these modules connected without a fragmented experience. The product evolved around a small set of shared concepts, and that common data model lets the modules work together instead of becoming isolated mini-apps.

About 10-11 people use ContentCal daily, and it is embedded in the team's real marketing workflow rather than sitting as a prototype. It helped the team:

This wasn't a weekend SaaS built to show off a technology. It was built inside a real organisation, for real users, against real operational problems, by someone hired to make graphics who kept asking "why are we doing this manually?"

My formal title at Concept Dash is graphic designer. My work on ContentCal went well beyond it.