Case Study 02
Event management + creative strategy · Backend Glow-Up — current paid client
This established event management and creative strategy company already had a sophisticated-looking backend.
They had:
The Founder had spent years documenting how the business should work.
And yet, she was still the person making sure it actually worked.
She described the growth challenge clearly:
“I cannot be the center of it, and I cannot be the main touch point for everything going forward.”
New opportunities were already arriving.
The problem was that more business still meant more founder oversight.
01
Projects were technically delegated.
But the Founder was still:
In one especially telling example, a team member had responsibility for an event.
The templates existed.
The SOPs existed.
The team had reviewed the project repeatedly.
But when the Founder arrived at the event:
the production schedule did not exist.
That showed us the real issue.
The company did not need another SOP.
It needed a stronger definition of ownership.
02
We followed actual engagements from:
inquiry → sale → onboarding → planning → production → execution → closeout
and looked at where responsibility really sat.
Five patterns emerged:
The Founder reflected:
“This was eye-opening for me because I assumed that having SOPs and having the tools and having clearly defined roles meant everybody knew what needed to happen next.”
That was the real breakthrough.
03
Instead of organizing the business around the people who happened to be there today, we designed around the functions the business actually needs.
We clarified the future responsibilities of:
The most important distinction:
The Founder summarized her future role simply:
“The CEO is not the project manager.”
And:
“I come in as an exception, not as the rule.”
04
We also turned something that had previously lived largely in founder experience into an explicit operating standard:
What actually has to be true before an event is ready?
The answer involved more than checking tasks.
The team needs confidence that the critical pieces — client decisions, vendors, production, staffing, schedules, documentation, and outstanding risks — are actually resolved.
That means the business can distinguish between:
“Someone did the follow-up.”
and:
“The outcome we needed actually exists.”
That distinction now sits at the center of the new operating model.
05
The operating work also surfaced a financial issue.
Some engagements looked profitable based on the contract value.
But when founder time, meetings, creative work, coordination, and repeated follow-up were considered, the economics looked different.
The Founder realized:
“We’re now donating our time at this point.”
That changed the pricing conversation.
She subsequently created a new pricing calculator and later reflected:
“I realized that we are in fact undercharging probably across the board.”
The value of the Diagnose phase was already influencing how the business made decisions before the software had even been built.
06
During Architect, we translated those findings into a product direction.
The future system is being designed to give each role a different view of the same underlying engagement.
A Project Manager should be able to see:
Operations should see the health of the portfolio and where support is required.
The Founder should get a much smaller leadership view answering:
What genuinely needs me?
When she reviewed that direction, she said:
“Everything lives here.”
And:
“Love the CEO Pulse. That’s such a great, great tool.”
07
Diagnose and Architect are complete.
The Operating System Blueprint has been approved.
The Founder responded:
“This looks great, we can move forward.”
Build has been authorized and the client-owned technical environment is now being established.
The next stage is turning the approved operating model into working software.
08
More clients
more monitoring
more checking
more founder involvement
More clients
clearer ownership
stronger project management
visible capacity
structured escalation
Founder stays in the executive seat
When asked how growth would feel if the company operated this way, the Founder answered:
“A no-brainer. You just say yes and keep it moving and keep growing.”
Current engagement. Diagnose and Architect are complete and approved. Build has been authorized. Final post-implementation outcomes are not yet being claimed. Identifying 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.