Small Business Operations Case Study: Building Clearer Systems for a Growing Service-Based Business
About this case study
This is an anonymized, in-progress example based on a current DeSha & Co. engagement. Identifying business, client, financial, and confidential information has been intentionally omitted. Because the engagement is ongoing, this case study focuses on the operational work completed to date rather than claiming final or quantified results.
Case Study in Progress: Building Clearer Systems for a Growing Service-Based Business
Growth does not always arrive with a perfectly organized operations manual tucked under its arm.
Sometimes the business grows first.
The systems catch up later.
That was the situation when I began working with a growing service-based business whose client volume, administrative needs, communication requirements, billing processes, and internal responsibilities had become increasingly interconnected.
The business itself was working.
People cared deeply about the clients they served.
Important information already existed.
Processes were happening every day.
But like many growing small businesses, much of the operational knowledge had developed organically over time.
Some information lived in individual documents.
Some lived in software.
Some lived in email.
Some lived in processes people simply knew how to perform.
And some lived in the founder’s head.
The work did not begin with:
“Let’s replace everything.”
It began with:
“Let’s understand what already exists, identify what is creating friction, and make the business easier to operate.”
That distinction is at the heart of how I approach business operations consulting.
The Challenge: Growth Had Created Layers
This business had reached the point where several operational areas needed to work together more clearly.
Those areas included:
internal policies
client-facing information
billing communication
onboarding
administrative responsibilities
scheduling communication
documentation
recurring operational processes
software and client-portal usage
None of these areas existed in isolation.
A change to billing affects customer communication.
A change to client onboarding affects administration.
A policy decision affects the team and the customer experience.
A scheduling process can affect billing, communication, and reporting.
That is why operations work rarely succeeds when every problem is treated as a separate little island.
The business needed more than individual documents.
It needed a clearer operating structure.
Step One: Turn Scattered Policies Into a Usable Internal Reference
One of the first opportunities was policy organization.
The business already had important policies covering different parts of the client relationship and service experience.
Rather than allowing those documents to remain separate operational fragments, we began consolidating them into a master internal policy reference.
The goal was not simply to create a bigger document.
The goal was to create a clearer source of truth.
That meant organizing information so the team could more easily understand:
which policies existed
where information belonged
how different policies related to one another
what still required review
where conflicting or incomplete information needed to be resolved
This is an important distinction in SOP and policy development for small businesses.
Documentation is not useful merely because it exists.
It has to be usable.
Step Two: Build a Better Client Resource Experience
Another major focus has been client-facing information.
Growing businesses often answer the same administrative questions repeatedly:
Where do I find this?
How does billing work?
What should I bring?
Who should I contact?
Where do I submit something?
What happens before my first visit?
When these questions happen often enough, they are telling you something.
The customer experience needs infrastructure.
For this business, that led to the development of a centralized client resource library designed to give customers clearer access to common information.
Resources developed so far include guidance around areas such as:
using the client portal
understanding billing processes
preparing for a first visit
communication expectations
frequently asked administrative questions
shared-space or service-related preparation
where to find official policies and forms
This work creates an important operational bridge:
Internal process → clear customer communication.
Because the best internal system in the world still creates friction if the customer cannot understand what is happening.
Step Three: Clarify Billing Communication
Billing is one of those areas where operational confusion becomes customer frustration very quickly.
The work here has included organizing clearer guidance around:
how clients access billing information
where payments are made
how recurring billing cycles function
what information is available in the client portal
when customers should contact the office
how payment questions should be routed
The important lesson is that improving a billing process is not always about changing the billing software.
Sometimes it is about improving the system surrounding the software.
Who communicates what?
When?
Where does the customer go?
What does the team do when something goes wrong?
What information should be documented?
That is operational design.
Step Four: Make the First Client Experience Easier to Navigate
New-client onboarding is another area where small inefficiencies multiply quickly.
A growing business may have several steps that all have to happen correctly:
collect information
create the client record
schedule services
confirm documentation
communicate expectations
verify relevant administrative information
establish billing
make sure the right people have what they need
When those steps live primarily in memory, the business becomes dependent on the person who knows the process best.
So part of the ongoing work has been identifying opportunities to create a more consistent client onboarding process.
That includes developing clearer first-visit guidance and exploring ways to simplify how new-client information is collected and moved into the business’s systems.
This is where small business operations work becomes very practical.
We are not creating process for the sake of process.
We are reducing the number of things someone has to remember.
Step Five: Clarify Administrative Ownership
As businesses grow, one sentence becomes increasingly dangerous:
“I thought someone else was doing that.”
A healthy operating model needs clarity around ownership.
Who monitors scheduling changes?
Who handles new-customer setup?
Who follows up on billing issues?
Who manages recurring administrative work?
What gets escalated to the owner?
What can the team handle independently?
The engagement has included documenting administrative responsibilities and identifying recurring workflows that can be made more consistent.
This is especially important for founders.
Every responsibility that remains unclear tends to float upward.
Eventually, it lands on the owner.
Role clarity is therefore not just an HR issue.
It is a founder capacity strategy.
Step Six: Look for Opportunities to Use Existing Technology Better
Another important part of this engagement has been looking at how existing software and systems support the operation.
This is one of my favorite parts of the work because businesses often already own more capability than they realize.
Before recommending another platform, I want to understand:
What do you already have?
What is it capable of?
Where are you still doing something manually?
Where is information being duplicated?
Where are employees or customers confused?
Could the existing tool support the process more effectively?
My nearly 20 years working across corporate operations, technology, systems, platforms, and workflows shapes this part of my consulting heavily.
Sometimes the smartest technology recommendation is:
“You do not need another system. You need a better process around the one you already have.”
What Has Been Built So Far
This engagement is still in progress, so I am intentionally not presenting final results or invented percentages.
There are no dramatic “we increased efficiency by 47%” claims here.
Not yet.
What does exist is tangible operational infrastructure.
So far, the work has included developing or organizing:
a consolidated internal policy reference
a centralized client resource library
clearer billing and portal guidance
first-visit preparation resources
communication guidance
documented administrative responsibilities
clearer recurring workflows
opportunities for simplified client intake
operating processes designed to reduce reliance on individual memory
Those are the building blocks of a more scalable business.
The Bigger Transformation
The real work is not the documents.
It is what the documents represent.
We are moving information from:
scattered → centralized
Processes from:
remembered → repeatable
Responsibilities from:
assumed → clarified
Customer communication from:
reactive → proactive
Founder knowledge from:
living in one person’s head → becoming business infrastructure
That is what business process improvement looks like in a real small business.
It is rarely one giant transformation.
It is dozens of thoughtful decisions that gradually make the business easier to understand, easier to operate, and easier to grow.
What I Would Tell Another Growing Business Owner
If your business feels disorganized, that does not automatically mean you need to rebuild it.
You may already have most of the pieces.
They may simply need to be connected.
Start by asking:
Where does information live?
Which questions do we answer repeatedly?
What depends on one person remembering?
Where does work get stuck?
Which responsibilities are unclear?
What are we doing manually that our existing tools could support?
What does the customer experience from their side?
Those questions will tell you far more than downloading another generic SOP template.
Why I Work as an Integrated Partner
This engagement also demonstrates why I believe so strongly in integrated consulting partnerships.
You cannot understand this type of operational environment from a single questionnaire.
You have to get close enough to see the connections.
The policy affects the billing process.
The billing process affects the customer experience.
The customer experience affects communication.
Communication affects administration.
Administration affects founder capacity.
It is a web.
My role is to help untangle that web without stripping away what already works.
That is very different from dropping a cookie-cutter solution into the business and hoping everyone adapts to it.
Sometimes I am advising.
Sometimes I am building.
Sometimes I am documenting.
Sometimes I am asking:
“Why are we doing this twice?”
And sometimes I am helping the client see that something they assumed required a complicated solution can actually become much simpler.
That is the kind of work I want DeSha & Co. to be known for.
What Comes Next
Because this engagement is still active, there is more to learn.
The next phase is not about creating documentation simply because documentation looks organized.
It is about watching how the systems perform in real life.
What gets used?
What still causes questions?
What needs refinement?
Where can additional automation help?
What should be simplified further?
What can eventually be delegated with confidence?
That is an important part of sustainable operations.
Build. Use. Learn. Refine.
Not:
Build something impressive and never touch it again.
Is Your Business Growing Faster Than Your Systems?
You may recognize some of this in your own company.
The business is successful.
Customers are coming.
The work is getting done.
But behind the scenes, too much depends on memory, manual effort, scattered information, or the founder stepping in to keep everything moving.
That is exactly the kind of business I love working with.
DeSha & Co. helps growing small businesses simplify operations, improve workflows, strengthen client onboarding, organize policies and processes, get more value from existing systems, and build operational structure that supports sustainable growth.
You do not need everything figured out before we begin.
Bring me the business as it is.
We will figure out what needs to work better.
Build simply. Lead sustainably.
→ Explore CEO Consulting Engagements
→ Tell Me What’s Feeling Heavy
