Case Study 03
Creative content + marketing studio · Backend Glow-Up — current paid client
A boutique creative content and marketing studio came into the Backend Glow-Up with a problem common to highly creative businesses:
Every client was different.
The company works across areas such as:
That flexibility was intentional.
The founders did not want to turn the business into a rigid production factory.
But operationally, each new client could also create a new combination of:
And too much of that complexity still lived between the two founders.
One Founder summarized the backend:
“Oh, girl, everywhere. Everywhere. It’s a mess.”
01
The business had useful tools.
Information lived in:
The creative work was getting delivered.
The problem was that the business knew where things stood largely because the founders knew where things stood.
One Founder explained:
“We talk almost every day, and still sometimes it’s like, where’s that thing at?”
That becomes increasingly risky as the company grows.
02
The founders want to take on larger, more valuable work.
But they were beginning to hesitate.
One said:
“I am almost hesitant to take on newer, bigger projects because I don’t know if we could handle it.”
They were also finding that taking time off still required:
The business could not yet cleanly operate without founder context.
03
We started by following real client work.
That included:
The deeper pattern was:
Every custom creative engagement was also creating a custom operating process.
That meant the founders were not only doing creative work.
They were repeatedly rebuilding:
The creative work should remain custom.
The coordination does not need to.
04
Instead of trying to make every project identical, we started defining the structure that can sit underneath different types of work.
A client may still move through a shared operating journey:
Lead
Qualification
Scope + pricing
Agreement
Onboarding
Delivery
Approval
Completion
Re-engagement
The work inside each stage can vary.
A podcast is not a website.
A website is not an event campaign.
But the business should not have to invent how ownership, payment, follow-up, and handoff work every time.
05
Pricing was one of the clearest examples.
Historically, a new project could trigger a long internal conversation.
One Founder described it:
“We talk about it and we talk about it and we angst over it. We talk about it some more. Then we think about it.”
The founders had plenty of pricing judgment.
It simply had not been externalized.
So rather than creating a rigid rate card, we began defining:
The future system should help prepare the decision, not make the decision for them.
06
A recurring client surfaced another major issue.
A client might ask:
“Can you also do this?”
The founders might genuinely want to.
But additional work could begin through:
Then someone had to remember:
That is not a creative problem.
It is an operating problem.
The future model needs to make additional scope visible before it becomes free work.
07
One of the studio's strongest workflows is recurring podcast production.
A typical cycle includes:
The founders recently documented an editing process for a new contractor.
That simple change had an immediate effect.
The production Founder said:
“I think that document helped her kind of streamline the whole process.”
And the next episode was completed faster.
That gave us useful evidence:
Not everything the founders know needs to remain in their heads for quality to stay high.
08
The studio originally wanted SOPs.
As we dug deeper, the documentation need became much more specific.
The business needs some combination of:
That distinction matters.
A checklist cannot tell someone what to do when a Founder becomes unexpectedly unavailable.
A company policy cannot teach an editor how a particular show should feel.
Different operating knowledge needs different formats.
09
We also traced how invoicing currently works.
Recurring invoices are still manually created from previous documents.
Additional billable work can be remembered through:
Payments may arrive through different channels.
The process works at the current scale.
It becomes risky at the scale the founders want.
So we began establishing clearer rules around:
The direction is moving toward a backend where payment status is visible instead of something the Founder has to investigate.
10
The founders do not want to remain two people personally executing everything.
They want the ability to assemble project teams around higher-value work.
That means the future operating system needs to support:
One Founder said:
“We need an operating system that will support team growth.”
Their vision is not to remove themselves from the creative work.
It is to stop spending so much of their talent on the friction surrounding the creative work.
11
One Founder described the future business as having two types of work.
The repeatable work can become more of a production engine.
The founders can spend more time on the highly creative, high-value work.
He described it as:
“It’d be great if we could have a cheeseburger factory just making cheeseburgers for people, but then my co-founder and I can be high-quality chefs making great steak for people.”
The other Founder put it even more simply:
“I just want to make the cheese.”
That is the transformation being designed.
12
Diagnose is complete. Architect is currently underway.
So far, we have mapped and begun redesigning:
Build has not yet been completed.
No final software solution is being claimed yet.
The point of Architect is to decide what should be built before anything is built, so the design reflects what the business actually needs.
13
More clients
more custom coordination
more founder memory
more conversations
more mental load
More clients
shared operating structure
clearer scope + pricing
repeatable handoffs
visible ownership
founders spend more time on creative judgment
One Founder described the personal outcome she wants:
“I wouldn’t end every day feeling like there’s still so much that needs to be done.”
And:
“We’d be able to take true vacation days.”
The goal is not to make the business less creative.
It is to make sure creativity is no longer dependent on the founders personally holding the entire backend together.
Current engagement. Diagnose is complete. Architect is active. Build and Activate have not yet occurred. No post-implementation results are being claimed. Identifying business, client, team, and project details have been anonymized.
Your business does not have to look like this business for the operating problem to be similar.
If growth still depends on you remembering, checking, connecting and translating what happens next, the Backend Glow-Up is designed to change that.