You Know Where the Business Needs to Go. We Build the Path to Get There.
Case studies
Most owners don't need more ideas. They need the step between the idea and work that happens the same way every time: who owns it, what comes first, what it depends on, and how anyone will know it's done. That step is what we build together.
Along the way the work produces SOPs, project plans, role design, technology rollouts and vendor coordination. Those are outputs, not the point.
From owner idea to a system that runs
This is a composite from several projects, because it's the same story every time. An owner says "let's do this." Staff start moving before anyone has defined what "this" is. Work gets done twice, or not at all.
The fix is answering a short list of questions before anyone starts. Take "let's start planning meetings with our best customers." Before the first meeting was scheduled: which customers, who owns each relationship, meeting format and length, system access, the reports needed, who preps, what the customer takes home, and where it gets documented.
Objective: What does done look like, in a sentence anyone can repeat?
Owner: One name per piece, including the pieces between people.
Dependencies: What has to be true first: access, data, vendors, decisions.
Sequence: What happens in what order, so daily work keeps running.
Workflow: The repeatable steps, written so a new hire could follow them.
Deadline and follow-up: Dates, check-ins, and a record of what was decided.
Operations never stay finished
Businesses grow. People come and go. Technology changes. Customers expect something different. A process that worked three years ago can be the thing slowing you down today.
SSG's experience comes from inside businesses going through those changes: retail stores, restaurants, professional service firms and a growing multi-service office. None of them look today the way they did then, and even recent work keeps changing. That's the point. What worked then isn't automatically what's right now. What carries forward is knowing how to walk into an operation, figure out what's really going on, and build the path from where it is to where the owner needs it to be.
Situations you might recognize
These aren’t polished stories. Each one starts with what an owner might actually say. Click any of them below to see how it was handled.
Each one followed the same pattern an SSG engagement does: look at how the work actually runs, name what’s really in the way, then build the fix with the people doing the work.
-
More than once, a store was handed over well below the company standard: disorganized, inventory out of control, staff worn down. The job was to fix it while it stayed open and served customers every day.
There was no secret. It was consistency. Clean it, organize it, set the standard, hold the standard, and keep showing up until the new way became normal. Inventory got under control and shrink came down. It always took longer than anyone wanted. But the next manager walked into a store that didn’t need rebuilding.
What it means for you: Turning something around isn’t one big fix. It’s a clear standard, held long enough that people stop needing someone to hold it.
-
An established professional practice was still running mostly on paper, using methods decades behind how the work could be done.
It moved to a digital operation. Billing was standardized, clients got clear expectations about timing and how work would flow, and the office was remodeled. All of it happened while client work kept moving, through COVID and several years of long, overlapping busy seasons. When staff left, knowledge that had never been written down had to be found and rebuilt. Another firm’s client files were brought in and converted from paper too.
What it means for you: You don’t get to pause your business to fix it. The change has to be designed so the work keeps getting done while it happens.
-
A national restaurant and retail chain opened a new location in a small mountain town where people choose local first. Part of the job was helping a national operation feel like it belonged there: coaching staff on how to connect with local guests and building a team that fit the rhythm of a college town.
That same location was measured against forecasts built from other stores. The math was fine. The assumptions weren’t. A big home football game put thousands of people in town, but traffic locked up, locals stayed home, and sales didn’t jump the way the model said they would. For about two years the store was held to those numbers. The operation stayed steady instead of chasing a target that wasn’t real. The data eventually caught up, and the budgets changed.
What it means for you: A system that works somewhere else isn’t automatically the answer here. And before you fix your operation, make sure the operation is what’s broken. Sometimes it’s the forecast or the assumption underneath it.
-
Restaurant work is long and hard on your feet. Instead of accepting exhaustion as part of the job, hiring changed:
Over-hired on purpose, starting each new hire at 15 hours or less
Set expectations on day one: hours may vary, and you show up when we’re open, including breaks and holidays
Kept a target headcount for early, mid and late shifts
Kept a few people who worked one day a week or one day a month to fill gaps nobody else could
Built a call-out list so a missing person didn’t sink a shift
Never stopped hiring, so the next layer was ready when strong people moved on
Most people worked fewer hours, came in fresher, and morale went up. The strong ones rose into good hours and leadership. That model carried the store for about three years, and payroll tracked the business instead of swinging past it.
On the people side, the first step is asking questions before deciding someone is the problem. Do they know what’s expected? Do they know why it matters? Do they have the authority to do it? Often the operation created the behavior it’s complaining about.
What it means for you: Staffing is design, not just hiring. Clear roles and a schedule people can sustain fix more than replacing people does.
-
When the practice changed hands, the goal was simple: give the new owners a business that was fully running, so they could start making their own changes from a working state instead of digging out of a mess. That’s what they got. It’s the same standard applied every time a store changed managers: hand it over clean.
What it means for you: A good transition isn’t the day keys change hands. It’s making sure the next person inherits something they can actually operate.
-
A growing firm decided to open a second office, about a $500K project. The architect, contractor, IT, security, furniture vendors and staff each owned a piece. Nobody owned the places where those pieces meet.
Served as the owner-side coordinator across every vendor
Kept a decision trail and caught items that were agreed out loud but never made it into the drawings
Challenged a proposed cut through the concrete slab for floor wiring, about $10K, and worked out alternatives with IT and the contractor
Planned the space to be ready for people, not just finished construction: 33 network drops, 3 wireless access points, phones, security, access, signage and furniture
What it means for you: A second location is a hundred small decisions. Someone has to own the gaps between vendors, or you end up paying for them.
-
A firm had access to a set of new tools. Turning them all on at once would have meant everyone using them differently, or not at all.
Phased the rollout: scheduling, meeting summaries, CRM, email tools and mobile, each with training and testing
Mapped 11 core client processes into CRM workflows with triggers, owners, tasks, due dates and completion points
Replaced everyone’s personal scheduling tools with one firm standard
Redesigned a client-facing verification process so staff knew which method to use in which situation
Gave each tool a named internal owner
What it means for you: Software doesn’t fix a process. It needs a workflow, an owner, and a reason for people to use it the same way.
-
New staff, a new senior team member, a second office, a technology rollout and policy changes all hit at the same time, while the firm still had to serve clients every day.
Sequenced the projects so daily work kept running
Built onboarding plans covering day one, technology, training, payroll, benefits, responsibilities and follow-up
Looked at workload and coverage before treating headcount as the answer
Designed a part-time role around the actual work instead of a generic job description
Built an internship model that adds capacity instead of management load
Moved phone lines, verification texts and shared inboxes off individual employees and onto company-owned accounts
What it means for you: Growth adds work in the gaps between roles. The fix is designing those gaps on purpose, not handing extra duties to whoever is closest.
-
A growing service operation needed its overseas production team to work as one system, not a group of remote workers waiting on the U.S. side.
Built the operating cycle: onboarding, access, diagnostic review, cleanup and catch-up, recurring work, review, escalation and handoffs
Replaced permanent U.S. account management with a warm handoff to the overseas team, with the U.S. side handling true escalations only
Designed the path to overseas team leadership, with outside HR, payroll and compliance support and U.S. oversight
What it means for you: Outsourcing doesn’t have to mean losing control. Control comes from the structure, not from one person staying in the middle of every account.
-
“We do good work” isn’t a model you can grow. It wasn’t clear who owned the customer, the work, the review, the communication, the delivery or the liability.
Defined a white-label model: the partner firm owns the relationship, communication, billing and final review, and the production team does the work behind the scenes
Separated a partner channel from a direct-to-business channel, each with its own onboarding and pricing
Turned the core service into a repeatable cycle: onboarding, diagnostic, cleanup, recurring work, review, escalation and handoff
Built quality control around qualified review and escalation
Built a pricing model running from delivery cost to client quote
Outside review of the finished work was favorable.
What it means for you: A service becomes a business when anyone on the team can deliver it the same way, and you know what it costs to deliver.
-
Three patrollers, one busy mountain. On ski patrol, some days it was three of us on a busy mountain, bad conditions and injuries all over the hill. Reach people, get them down or to a higher level of care, restock, and be ready for the next call without leaving the slopes uncovered. Same question as any operation: what do we have, and where does it need to be next?
Two departments, one building. The restaurant and retail sides didn’t trust each other. Learning the restaurant side well enough to help when it went sideways mattered, because when it struggled, retail did too. Over time, staff from both sides brought problems forward. Not because of a title. Because someone was there and followed through.
When sales drop and it isn’t the operation. A move from a strong store to one in a very different market landed just as the financial crisis hit. Sales fell hard. Standards stayed up and everything controllable was controlled. Good operations don’t guarantee good sales, and it matters to know the difference.
An overnight shift that had to run itself. Everything staged, the audit done, and the morning crew walking into a ready building. Creating capacity when you don’t have any is a skill you learn by necessity.
A client event for about 305 people. Vendors, approvals, communication and day-of execution, with one owner for each piece.
Replacing equipment without going offline. Staged the swap so the office never went down all at once.
Policy people actually use. Turned a dense handbook into grids, scenarios and decision points staff can follow in real situations.
Building issues with an owner. Gave maintenance and repairs an owner and a vendor path so they stopped landing on whoever noticed.
What we don't claim
No one can know how those businesses run today, and a fix from years ago isn't automatically the fix for your business now. What carries forward is knowing how to learn an operation, separate symptoms from causes, use the resources you actually have, and build something you can run on your own.
Have an idea that hasn’t turned into a system yet?
You bring the destination. SSG helps build the path, and we work it out together. The first conversation is free: thirty minutes on where you want the business to go and what’s missing between here and there. Let’s talk.

