Case study · Agency operations systems

Building a scalable ClickUp operating system for a growing marketing agency

Branded Genius had grown beyond the workflow that once supported it. ClearKnot reorganized internal marketing, finance, and client delivery into one coherent ClickUp operating system designed to remain usable as the agency and its AI-driven services expand.

20+ active client projects
System diagramThree connected operating areas
Marketing
  • Content workflow
  • Publishing calendar
  • Content-team workload
  • Campaign tracking
Finance & Admin
  • Payment stages
  • Reconciliation status
  • What needs chasing
Client Delivery
  • Reusable project template
  • Isolated client intake
  • Consistent delivery pipeline

Project snapshot

Client
Branded Genius
Business
German marketing agency scaling into AI-driven services
Engagement
ClickUp workspace design and implementation
Scope
Internal marketing, finance and administration, and reusable client delivery
Delivery context
20+ active client projects
Platform
ClickUp, with an explicit operating boundary around the existing CRM
Status
Completed

The challenge

The agency had outgrown its own workflow

As the team expanded and the client roster passed twenty active projects, work was scattered across disconnected lists. Notification noise overwhelmed the team, client requests had no consistent intake and delivery path, and overlapping tools made it unclear what belonged in the CRM and what belonged in project management.

Every new client also required structure to be recreated manually. The workspace was accumulating complexity instead of making delivery easier.

Branded Genius needed one operating model the team could scan, trust, and reproduce without creating another layer of administration.

Requirements and constraints

One central system per operating area

The workspace was designed around one central system for each operating area, using views and fields rather than endless lists.

Every design decision was tested against three client priorities: keep it simple, keep it scannable, and remove the notification spam that had reduced trust in the tool.

  • The CRM owns leads, sales, and publishing execution.
  • ClickUp owns internal planning, finance tracking, project execution, and client delivery.
  • The two systems do not duplicate the same work.

Audit → Architect → Implement → Optimize

1Audit

Mapped the existing marketing, finance, and client-delivery structures; identified duplicated lists, notification sources, tool overlap, intake gaps, and the risk of mixing requests from different clients.

2Architect

Defined a central operating model for each area, the CRM/ClickUp ownership boundary, reusable client-project architecture, intake isolation, fields, views, statuses, and manual control points.

3Implement

Built the internal marketing system, finance and administration board, reusable client-delivery template, and German-language client intake experience.

4Optimize

Removed bot-driven notification spam, corrected the publishing-calendar configuration, prevented cross-client request leakage, and added new capabilities non-destructively around live client work.

Completed projects

What ClearKnot built

1

Internal marketing system

A single marketing hub replaced platform- and channel-specific list sprawl. The system includes:

  • one five-stage workflow;
  • seven purpose-built custom fields;
  • five focused views covering workflow, publishing calendar, content-team workload, and campaign tracking;
  • ten reusable templates for content and campaign types including reels, YouTube videos, SEO, and paid campaigns.

Each template creates a structured task with the appropriate steps and owners already in place.

2

Finance and administration board

A focused business tracking board was added alongside the agency's banking and accounting tools without attempting to replace them. It includes:

  • six payment stages;
  • structured fields for amounts, systems, and reconciliation status;
  • eight views that surface what needs paying, checking, or chasing.
3

Reusable client-delivery system

A master client-project template standardizes the majority of each engagement. A German-language intake form gives clients a structured self-service request path.

  • New client requests become ClickUp tasks and reach the project manager for triage.
  • Triaged work moves through a consistent delivery pipeline.
  • Each client's intake is isolated inside its own project so information cannot leak across client workspaces.

Problem-solving decisions

Notification trust was restored by removing unnecessary automation

An automated bot had been flooding the founder with alerts. The system was rebuilt without that automation and uses lightweight manual triage where judgment is required.

Client intake was isolated by project

An early design risk could have directed every client's request into one central project. The architecture was corrected so each client form feeds only the corresponding client project.

Publishing dates were separated from internal administration

A configuration issue prevented the calendar from representing actual publishing work cleanly. The view was corrected so it plots real publish dates and excludes internal administrative tasks.

Live delivery work was preserved

Existing projects already in delivery were not overwritten. New capabilities were introduced around live work through non-destructive changes.

Project evidence

Client screenshots are not published without written approval. The diagrams below are reconstructed from the delivered architecture and contain no client data.

System diagram
Internal marketing system
One marketing hub
  • Five-stage workflow
  • Seven custom fields
Five focused views
  • Workflow
  • Publishing calendar
  • Content-team workload
  • Campaign tracking
Ten reusable templates
  • Reels
  • YouTube videos
  • SEO
  • Paid campaigns
One hub replaced channel-by-channel lists: a single five-stage workflow and seven custom fields feed five focused views, and ten templates create structured tasks with steps and owners already set.
System diagram
Finance and administration board
Payment stages
  • Six stages on one board
Structured fields
  • Amount
  • System
  • Reconciliation status
Views by purpose
  • Needs paying
  • Needs checking
  • Needs chasing
The board tracks payments alongside the agency's banking and accounting tools rather than replacing them, with views organised by the question being asked rather than by account.
Workflow model
Client intake, isolated by project
  1. Client submits the German intake form
  2. Request lands in that client's project only
  3. Project manager triages
  4. Work moves through the shared delivery pipeline
Each client's German-language form feeds only that client's project, so a request is triaged and delivered without ever appearing in another client's workspace.

Has your agency outgrown the workspace it started with?

ClearKnot audits how internal work, client delivery, tools, ownership, and reporting fit together—then shows you what to simplify, separate, or rebuild first.

← All case studies

Book a free call