Your Business Shouldn't Be This Fucking Hard to Run.
Growth has a funny way of exposing every process nobody documented, every handoff nobody owns, and every decision that somehow still needs the founder. We help figure out why the business keeps fighting itself — and fix the operational shit underneath it.
Operational X-Ray
What usually shows up.
Founder Dependency
Decisions, approvals and exceptions still roll uphill.
Ownership & Handoffs
Everybody is busy. Nobody is completely sure who has the ball.
Process Documentation
Some of it is written down. The useful part lives in somebody's head.
CRM & Systems
The software and the actual business are telling different stories.
Client Delivery
Good people are working hard inside inconsistent processes.
Operator Note
“The thing driving you nuts is usually a symptom. I want to know what keeps creating it.”
The Goal
A business that makes sense without needing founder telepathy.
What Operational Problems Look Like
It rarely starts with
“we have an operations problem.”
Usually it shows up as missed work, frustrated employees, annoyed clients, constant interruptions, or another meeting about why something still didn't happen. The symptoms look different. The underlying problems are usually a lot more connected than they seem.
Everything somehow still ends up back on your desk.
You hired people so you could stop being involved in everything. Instead, you're still approving exceptions, answering questions, solving weird edge cases, and becoming the default answer whenever nobody knows what happens next.
Everybody's busy. Somehow the important shit still gets missed.
Plenty of people are working. That's not the same as clear ownership. Tasks bounce between people, responsibilities overlap, and work sits untouched because everybody reasonably assumed somebody else had it.
“We have a process for that.” No. You have a person for that.
The process works because one experienced employee knows all the exceptions, shortcuts, context, and unofficial rules. When they're unavailable, everybody suddenly discovers the documentation was mostly wishful thinking.
The work doesn't break inside departments. It breaks between them.
Sales thinks delivery has it. Delivery thinks onboarding owns it. Customer Success assumes somebody already followed up. The client doesn't care whose fault it was — they just know nobody called them.
You've got plenty of software. You still don't trust the information.
The CRM says one thing, Slack says another, somebody has a spreadsheet, and the actual truth lives in a conversation from last Thursday. Technology is supposed to create visibility — not an archaeological dig.
You keep talking about the same problem in different meetings.
Everyone agrees something needs to change. Then the meeting ends, normal work takes over, ownership gets fuzzy, and two weeks later you're having another conversation about why the same damn thing is still happening.
The Question I'm Asking
“Why does this keep happening — and what in the operation keeps making it possible?”
What We Actually Fix
We don't “optimize operations.”
We fix the shit making work harder.
Sometimes that means rebuilding a workflow. Sometimes it's clarifying who owns what. Sometimes the CRM is a disaster. Sometimes the technology is fine and the process underneath it makes absolutely no sense. The solution depends on what we actually find.
Jeremy's Rule
“I don't change shit just so I can say I changed something. If it already works, leave it alone.”
Ownership & Accountability
We clarify who owns the work, who makes the decision, who gets consulted, and what actually requires the founder. Because “the team handles it” is not an operating model.
Workflows & Process Design
We follow work from trigger to completion and remove unnecessary steps, duplicated effort, bottlenecks, dead ends, and the weird workarounds everyone forgot were supposed to be temporary.
Handoffs Between People & Teams
We define what happens when work moves from sales to onboarding, onboarding to delivery, leadership to execution, or one person to another. Good handoffs make responsibility visible before the ball hits the floor.
Documentation & Institutional Knowledge
We pull critical operating knowledge out of people's heads and turn it into documentation the team can actually use. Not a 47-page SOP written for the sole purpose of technically having an SOP.
Systems, CRM & Automation
We make the systems support the process instead of forcing the business to work around the software. That can mean cleanup, redesign, automation, integrations, better visibility, or occasionally admitting that a tool really does need to go.
Execution & Operating Rhythm
We look at how decisions become action: meetings, priorities, follow-up, accountability, communication, and the rhythm the team uses to actually move work forward. A decision nobody executes is just a conversation.
Capacity & Team Structure
Sometimes the process is fine and the team simply doesn't have enough capacity. Sometimes the opposite is true. We help determine whether you actually need another person, a different division of responsibility, or simply a better way of using the people you already have.
Important Distinction
Not every problem needs a transformation project.
Sometimes the right answer is a small change in ownership, one cleaned-up workflow, or finally making a decision everyone has been dancing around. Other times, the operation genuinely needs deeper work. We're interested in the smallest solution that actually solves the problem — not the biggest engagement we can sell you.
The Operator Lens
I don't start by fixing
the loudest problem.
The thing everybody is complaining about might absolutely be a problem. It just might not be the problem.
A missed client follow-up could look like somebody forgot to do their job. But maybe nobody clearly owned the follow-up. Maybe the CRM never created the task. Maybe the handoff happened in Slack. Maybe the process depends on somebody remembering something every single time.
So instead of immediately fixing the latest fire, I start tracing it backward until we find the part of the operation that keeps making the same kind of failure possible.
Operator Note
“People are easy to blame. Systems are harder to see. I want to understand both before deciding what actually needs to change.”
Trace the Failure Backward
From “what the hell happened?” to something we can actually fix.
Start With the Symptom
What actually happened?
A client was missed. A deadline slipped. Work duplicated. Someone got confused. The founder had to step back in.
Follow the Work
Where did the process actually break?
We look at the handoff, system, responsibility, communication, decision point, or missing step immediately before the failure.
Ask Why Again
Why was that failure possible?
Was ownership unclear? Was the process undocumented? Did the software not support the workflow? Were expectations different depending on who you asked?
Fix the Structure
What needs to change so this stops happening?
Now we can change the process, ownership, documentation, system, handoff, decision flow, or team structure with an actual reason for doing it.
The Result
We stop repeatedly solving the same problem wearing different clothes.
01
Don't assume it's a people problem.
Good employees can look bad inside unclear processes, weak systems, and conflicting expectations.
02
Don't rebuild what already works.
Existing systems earn the right to stay when they're doing their job. Change needs a reason.
03
Don't automate confusion.
Make the process make sense manually first. Then let technology make the good process faster.
What Better Looks Like
Same business.
Less unnecessary bullshit.
Operational improvement isn't about making the company look impressive on a diagram. It's about changing what happens on a normal workday. People know what they own. Work moves. Clients get taken care of. Leaders can see what's happening without chasing everybody for answers.
Before
The business fights itself.
After
The operation makes sense.
Ownership
“Ask the founder.”
Decisions and exceptions keep rolling uphill because nobody is completely sure where their authority starts or stops.
Ownership
The right person owns the decision.
Responsibility, authority, and escalation paths are clear enough that everything doesn't require founder approval.
Handoffs
“I thought they had it.”
Work changes hands through assumptions, Slack messages, memory, and whatever somebody happened to say in the last meeting.
Handoffs
The next owner is obvious.
The trigger, responsibility, information, and next action are visible before the work leaves one person's hands.
Process
“Sarah knows how.”
Critical knowledge lives inside experienced employees, and the real process only becomes visible when one of them is unavailable.
Process
The business knows how.
The important knowledge is documented clearly enough that execution doesn't depend on one person's memory or tribal knowledge.
Systems
Nobody trusts the CRM.
People keep their own notes, spreadsheets, reminders, and side systems because the official system no longer reflects reality.
Systems
The system tells the truth.
The tools support the actual workflow, information lives where the team expects it, and leadership can trust what they're looking at.
Execution
Same meeting. Same problem.
Everybody agrees something needs to happen, but ownership disappears somewhere between the meeting and the actual work.
Execution
Decisions turn into action.
Owners, next steps, priorities, and follow-up are clear enough that execution doesn't rely on somebody remembering the conversation.
Leadership
You have to chase the business for answers.
Visibility comes from meetings, messages, checking spreadsheets, and asking people individually what the hell is going on.
Leadership
The business can show you what's happening.
Leadership gets useful visibility from the operation itself instead of becoming the company's human status-reporting system.
The Actual Goal
Not perfection.
A business that's easier to run.
Businesses will always have weird situations, difficult days, unexpected problems, and somebody asking a question nobody planned for. Good operations don't eliminate reality. They make the business much better at dealing with it without turning every problem into a fire drill.
How We Can Work Together
The problem decides
what the engagement looks like.
I'm not going to pretend every business needs the same twelve-week transformation package. Some problems need a focused set of experienced eyes. Others need hands-on implementation or someone who can stay close to the operation as the company grows. We figure out the shape of the work after we understand what actually needs to change.
Operational Review
You know the business has friction, but you're too close to it to see exactly where the real problem lives. We dig into how the operation actually works, identify patterns, find the gaps, and give you a clearer picture of what deserves attention first.
Useful When
The symptoms are obvious, but the root cause isn't.
Focused Operational Project
Sometimes we already know where the pain is. A broken handoff. A messy onboarding process. Unclear ownership. An unreliable workflow. A process trapped inside somebody's head. We define the problem, fix that part of the operation, and keep the scope where it belongs.
Useful When
There's a specific operational problem that needs to stop being a problem.
Implementation Support
Knowing what should change is only useful if somebody turns it into reality. We can help design workflows, document processes, restructure systems, improve the CRM, clarify roles, build automations, and work alongside your team while the new way of operating actually gets put into practice.
Useful When
You don't need another recommendation deck. You need the damn thing implemented.
Ongoing Operational Advisory
Growing companies keep creating new decisions, bottlenecks, people challenges, system questions, and weird shit nobody planned for. Ongoing advisory gives the founder or leadership team another experienced operational brain in the room to help think through what comes next without adding another full-time executive.
Useful When
The business doesn't need one answer. Leadership needs a trusted operator to help navigate the answers that keep coming.
No Forced Packages
Sometimes you need less help than you think.
I'm perfectly comfortable telling you that the right answer is one workflow change, one clearer responsibility, or one decision you've been avoiding. And if what we uncover requires deeper work, we'll talk about that too. The scope should earn its way into the engagement. It shouldn't exist because somebody needed another line item on a proposal.
Not sure which one you need?
Good. You don't have to figure that out before we talk.
Jeremy's Rules for Operations
After enough years in the mess,
you learn a few things.
These aren't commandments and I'm not pretending I invented operations. They're just lessons I've learned after watching good businesses make the same avoidable mistakes over and over again. Simple rules tend to survive reality better than complicated frameworks.
A General Philosophy
“Make the business easier to understand, easier to operate, and less dependent on somebody remembering what the hell happens next.”
If everybody owns it, nobody owns it.
Shared responsibility sounds collaborative right up until something gets missed. Every important outcome needs a clear owner. Other people can contribute. Somebody still has to have the ball.
Don't automate a process nobody can explain manually.
Automation does not create clarity. It multiplies whatever you give it. If the manual process is confusing, inconsistent, or broken, automating it just lets the confusion happen faster.
A 47-page SOP nobody reads isn't documentation. It's literature.
Documentation exists to help somebody do the work. If employees need a search party, a philosophy degree, and twenty uninterrupted minutes just to find the next step, we missed the point.
Hiring another person into a broken process gives you another confused person.
Sometimes you genuinely need more capacity. Great. But headcount should not become the default solution to unclear ownership, poor workflows, weak onboarding, or work nobody has bothered to structure.
Don't blame the employee before you look at the environment.
People absolutely make mistakes. They also work inside the systems, expectations, tools, training, and decisions leadership gives them. Before calling someone the problem, make sure the business didn't set them up to fail.
If it already works, leave the damn thing alone.
Consultants sometimes feel obligated to change things because they were hired to change things. I don't. If a process is simple, understood, reliable, and doing its job, it has earned the right to survive the consulting engagement.
What All Six Have in Common
Operations should help people work. Not give them more shit to work around.
The goal isn't more process for the sake of process. It's enough structure to make ownership clear, execution repeatable, information trustworthy, and the business easier to navigate. Good operations should disappear into the way the company works — not become another department everybody complains about.
Let's Talk About the Mess
Show Me the Part of Your Business That's Driving You Fucking Crazy.
You don't need a polished explanation, a process map, or a diagnosis before we talk. Tell me what's happening, what keeps breaking, what keeps landing back on your desk, or what your team keeps fighting with. We'll start there and figure out whether The Swink Group can actually help.
30 minutes. No pitch. No pressure. No corporate theater.
You Can Literally Start With
“Jeremy, here's the shit I can't figure out.”
“Everything still needs me.”
The team exists, but decisions, exceptions, approvals, and answers keep rolling back uphill.
“Nobody seems to own this.”
Work keeps falling into the gaps between people, departments, systems, or somebody's assumptions.
“Our systems are a mess.”
The CRM, spreadsheets, Slack, automations, and actual operation have stopped telling the same story.
“We keep having the same damn problem.”
Different week. Different symptom. Somehow it keeps feeling suspiciously familiar.
“I don't even know where to start.”
Perfectly acceptable. That's why the first conversation exists.
One More Thing
“If I don't think you need me, I'll tell you. That's still a useful conversation.”
The Swink Group · Operations Consulting
Make the business easier to run.