How We Work

You Don't Need to Know What's Broken.
That's Kind of the Point.

Most founders come to us with symptoms, not a neat diagnosis. Something keeps slipping. The team is frustrated. Clients are feeling it. The founder is still in the middle of everything. We start by figuring out what the hell is actually happening, then work backward from there.

Diagnose First
Fix What Matters
Build for Real Use

How We Actually Work

Start with the mess.
Work backward from there.

I'm not going to walk into your business with a prewritten answer. First we understand what's happening. Then we figure out why. Then we fix what actually matters.

1

Step One

Tell Me What's
Driving You Nuts

We start with a conversation about what you're actually experiencing. Maybe clients are slipping through the cracks. Maybe your team keeps asking you the same questions. Maybe nobody knows who owns what. Maybe everything technically works, but somehow you're still involved in every damn decision.

You don't need to diagnose it for me. Tell me what's happening, what's frustrating you, and what you wish worked differently. That's enough to start.

Symptoms are enough. We'll find the problem.

Step Two

I Get Into
How It Actually Works

This is where we stop talking about how the business is supposed to work and start looking at how it actually works. The client journey, handoffs, responsibilities, CRM, workflows, automations, communication, documentation, and all the unofficial workarounds your team created just to keep things moving.

I'm looking for where information disappears, ownership gets fuzzy, unnecessary work gets created, clients feel friction, and the founder gets pulled back into things that shouldn't require them.

Client journey & handoffs

Systems, workflows & CRM

Ownership, communication & decision flow

2
3

Step Three

We Find the
Problem Under the Problem

The obvious problem isn't always the real problem. A missed follow-up might look like a people problem when the real issue is ownership. A messy CRM might actually be a broken process. A struggling employee might simply be working inside a system nobody ever properly defined.

We separate the symptoms from the root cause and decide what actually deserves attention. Because rebuilding everything just because we can is a really expensive way to feel productive.

Fix the cause. Stop babysitting the symptom.

Step Four — Where Strategy Meets Reality

Then We Build
What Actually Needs Fixing

This is where recommendations become actual operating improvements. Depending on what we uncover, that might mean rebuilding a workflow, clarifying responsibilities, documenting a process, fixing the client journey, cleaning up the CRM, improving an automation, restructuring a handoff, or helping leadership make a decision that's been sitting unresolved for six months.

✓ Clear ownership & responsibilities

✓ Workflows & process design

✓ Customer journey & delivery improvements

✓ CRM, automation & systems cleanup

✓ SOPs & usable documentation

✓ Leadership & operational decision support

4

The Swink Difference

Strategy That Survives Reality

5

Step Five

Then We Make Sure
It Works Without Me

The goal isn't to make your business dependent on another consultant. The goal is to leave behind clearer systems, better ownership, stronger client delivery, and fewer things that require somebody to remember the secret handshake.

Some problems are projects. Others need ongoing operational advisory as the company grows. Either way, we keep testing what we've built against the real business — because something isn't fixed just because it looked good in the meeting.

Show Me What's Going On →
The Operator Lens

What we look at when we
get under the hood.

Operational problems rarely stay inside one neat little box. A client issue can actually be a handoff problem. A people problem can really be an ownership problem. A CRM problem can turn out to be a process nobody ever defined in the first place. These are the areas we look at together to figure out what the hell is actually going on.

01

Ownership & Decision Flow

Who owns what? Who can make the call? What still requires the founder? If everybody owns something, there's a pretty good chance nobody actually does.

02

Customer Journey

What happens from signed contract to onboarding, delivery, follow-up, retention, and renewal? More importantly: where do clients get confused, ignored, delayed, or quietly dropped into the abyss?

03

Processes & Handoffs

We follow the work from person to person and department to department. That's usually where the unofficial workarounds, duplicated effort, unclear ownership, and “I thought they had it” moments start showing up.

04

Systems, CRM & Automation

Does the technology reflect how the business actually operates? Or has the CRM become a digital junk drawer while automations quietly make bad processes happen faster?

05

Documentation & Knowledge

What does the team actually know versus what exists only inside Sarah's head? We identify the knowledge the business can't afford to lose and document it in a way normal humans might actually read.

06

Leadership & Accountability

Are expectations clear? Do people know what good looks like? Can leaders make decisions without everything rolling uphill? Another accountability meeting won't fix unclear leadership structure.

“If the same shit keeps breaking in different places, I'm usually less interested in the latest fire than I am in whatever keeps handing out the matches.”

Jeremy Swink — Founder, The Swink Group

Common Questions

Things founders usually want to know
before they let me poke around their business.

Do I need to know exactly what's wrong before we talk?

Nope. Most founders don't come to me with a beautifully diagnosed operational problem. They come with symptoms: things keep getting missed, clients are frustrated, the team is confused, everything still comes back to them, or the business just feels harder to run than it should. That's enough. Figuring out what's underneath it is part of my job.

What happens after the first conversation?

If it looks like TSG can help, we'll decide what makes sense next. That might be a focused project, a deeper operational review, help fixing a specific part of the business, or an ongoing advisory relationship. I don't force every company into the same package just because it makes my website easier to explain.

How long does an engagement usually take?

It depends on what we're fixing. A defined workflow or client journey problem might take a few weeks. Broader operational work can take several months. Some founders want ongoing advisory support as the business keeps changing. I'd rather give you an honest scope once I understand the problem than make up a neat little timeline before I've seen the business.

How involved do I need to be?

Enough to give me context, answer questions, and make decisions when decisions actually belong to you. I'm not going to drag you into every detail, but I'm also not going to disappear into a cave for three weeks and come back with a 70-page deck explaining your own business to you.

Do you just give recommendations, or do you help implement them?

Both, depending on the engagement. Sometimes you need another experienced brain in the room. Sometimes you need somebody to help rebuild the workflow, structure the CRM, document the process, clean up the client journey, or get the new system working in real life. Strategy is useful. Strategy that never survives implementation is just expensive reading material.

Are you going to make us replace all our software?

God, I hope not. If the tools you already have can support the business, we'll use them. I'm not interested in rebuilding your entire tech stack so I can feel productive. Sometimes the software really is the problem. More often, the process underneath it just never made much sense.

Do you work directly with my team too?

Usually, yes. The people actually doing the work tend to know where the bodies are buried. Leadership can tell me how the process should work. The team can usually tell me what happens when Tuesday gets weird. I want both versions.

What if we actually do need another person?

Then we'll say so. Sometimes the bottleneck really is capacity and the business needs additional support. TSG can help with remote assistant solutions when that makes sense. I just don't believe hiring should be the automatic answer before we understand the work. Hiring another person into a broken process usually gives you one more confused person.

Can you stay involved after the initial problem is fixed?

Absolutely. Some businesses need a defined project and they're good. Others benefit from having an experienced operational advisor around as new problems, decisions, growth stages, and inevitable weird shit show up. The goal is not to create dependency on TSG. It's to provide the level of support that actually makes sense for the business.

Ready to Talk?

You bring the problem.
We’ll start making sense of it.

Book a free 30-minute Strategy Call and tell me what's happening inside your business. What keeps breaking, what keeps coming back to you, what's frustrating the team, or what simply feels harder than it should. You don't need the diagnosis before we talk.

Book a Free Strategy Call

No pitch. No pressure. No corporate theater.

What Happens on the Call

1

You tell me what's going on.

Give me the real version. What's frustrating you, what the team keeps struggling with, what clients are experiencing, and what keeps landing back on your desk.

2

I start asking why.

We'll talk through what might actually be underneath the symptoms. Sometimes the thing driving you nuts isn't the real problem. That's usually where things get interesting.

3

We decide whether there's a useful next step.

If TSG can genuinely help, I'll explain what I think makes sense. If you don't need me, I'll tell you that too. I'm not interested in manufacturing a consulting engagement just to sell one.