MediaConsole: Turning spreadsheet chaos into scalable SEO operations

Context & My role

MotherLink began as an SEO marketplace connecting brands with publishers. But as customers scaled, it became clear that access to publishers was no longer the main problem. The real challenge was operations. SEO teams were struggling to manage outreach, content, placements, payments, reporting, audits, and renewals across fragmented spreadsheets and disconnected workflows.

I joined as a founding designer to help transform that operational chaos into a scalable product system: MediaConsole. My role extended beyond interface design into product strategy and workflow architecture. I worked closely with founders, engineers, and early customers to shape the platform from the ground up.

I led:

• user research across SEO, Outreach, Coordination, and Finance roles,

• workflow modeling and information architecture,

• UX/UI across 30+ modules,

• PRFAQs, product requirements, and roadmap definition,

• operational system design for enterprise-scale workflows.

The challenge was designing a system that teams could trust enough to replace the spreadsheets they had built their businesses on.

The problem

Every SEO team I studied relied on sprawling spreadsheets to manage their operations. What began as simple tracking systems eventually became operational bottlenecks.

Teams used spreadsheets to coordinate:

• publishers and websites,

• outreach workflows,

• content requirements,

• placements and anchors,

• payments and invoices,

• audits and renewals,

• reporting across sites and campaigns.

These systems worked until teams scaled. As operations grew, visibility degraded. Reporting became manual. Ownership became unclear. Errors accumulated quietly across dozens of interconnected workflows. Yet despite these issues, nearly every team believed their process was “too unique” for software to support.

The core challenge became clear:

How do you standardize operational structure without removing the flexibility teams depend on?

That tension shaped the entire product strategy.

Research & product strategy

To understand how SEO operations actually functioned beneath the spreadsheets, I conducted:

• interviews with SEO managers and agency owners,

• role-specific stakeholder research,

• workflow shadowing,

• spreadsheet audits,

• asynchronous operational mapping sessions.

Across teams, several consistent patterns emerged:

1. Most workflows shared the same structural core. Despite surface-level differences, nearly every team followed the same operational lifecycle.

2. Teams rejected rigid project-management tooling. Many teams disliked kanban systems, even though their work naturally moved through staged operational flows.

3. Most operational work was repetitive and rule-based. Large portions of SEO operations were highly procedural and ideal candidates for automation.

4. Users wanted automation, but not at the cost of control. Teams needed visibility, override capabilities, and auditability alongside automation.

5. Not all data had equal importance. Operational clarity depended on prioritizing signal over volume.

These insights helped define the platform’s operational backbone:

Import → Order → Pay → Report → Audit → Renew.

This lifecycle became the foundation for the system architecture.

Designing the operational core

One of the biggest discoveries during research was that nearly every workflow revolved around the same operational object: a placement request moving through multiple lifecycle stages. This became the Order item — the atomic unit of MediaConsole.

The Order item is connected:

• publishers,

• placements,

• content,

• payments,

• reporting,

• audits,

• renewals,

• collaboration.

Instead of designing isolated features, the platform evolved by expanding the capabilities surrounding this single operational entity. This approach allowed the product to scale without fragmenting the experience.

System Evolution

Phase #1: Foundation

The first challenge was creating a stable operational structure that teams could migrate into without overwhelming them. To accelerate development, I reused and adapted components from the existing MotherLink marketplace design system, reducing engineering overhead and speeding up iteration.

Key foundations included:

• media database import,

• workspace setup,

• operational table patterns,

• publisher and website entities,

• mobile-friendly interactions for quick operational checks.

The goal of this phase was not feature depth — it was to build trust in the system's structure.

Phase #2: Operational workflows

Once the foundation was in place, MediaConsole evolved from a database into an operational platform. The Order Item became the center of execution.

This phase introduced:

• end-to-end placement workflows,

• publication tracking,

• payment logic,

• live-link monitoring,

• reporting foundations,

• structured operational states.

A major product decision during this phase was moving away from kanban-style interaction models toward dense operational tables optimized for scalability and clarity. The product began behaving less like a task manager and more like operational infrastructure.

Phase #3: Automation & scale

As larger teams adopted the platform, scalability shifted from a UX problem to a systems problem.

MediaConsole expanded to support:

• hierarchical roles and permissions,

• account and multi-site structures,

• unified reporting across active and historical links,

• renewals as a first-class lifecycle,

• collaborative notes and operational history,

• automated audits for link validation and compliance,

• campaigns and planning workflows,

• asynchronous draft preparation.

At this stage, MediaConsole became a true operational engine connecting strategy, execution, reporting, finance, and collaboration inside a single system.

Outcomes

MediaConsole evolved from a marketplace extension into the operational backbone for enterprise SEO teams.

Key outcomes included:

• replacing spreadsheets for high-volume customers;

• reducing reporting workflows from days to minutes;

• enabling multi-site and account-level operations;

• supporting enterprise onboarding through early-access programs;

• scaling across 30+ interconnected modules without workflow fragmentation.

More importantly, the platform proved that highly fragmented SEO operations could be standardized without becoming rigid.

Reflection

The biggest lesson from MediaConsole was that operational software succeeds when it balances structure with adaptability. Most teams initially believed their workflows were unique. But beneath the spreadsheets, the operational patterns were remarkably consistent.

By designing around shared system primitives rather than isolated features, we created a platform that scaled across different team structures while remaining understandable, flexible, and operationally reliable. MediaConsole was ultimately less about building interfaces and more about designing operational behavior at scale.