Let's Talk →

How We Work

Working Principle

Diagnose before prescribing. Build around how the business actually works.

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's actually happening.

The Approach

“Understand the business first. Then decide what actually deserves to change.”

The Working Method

01

Listen to what's happening

02

Follow the work

03

Find what is actually causing the friction

04

Fix what matters

05

Make sure it works in real life

No prepackaged transformation plan. No forcing the business into somebody else's framework. The work follows what we actually find.

See How the Process Works ↓

How We Actually Work

Start with what's happening. Work backward from there.

I'm not walking into your company with a prewritten answer. We understand what you're experiencing, follow how the work actually moves, figure out what keeps creating the problem, and then change what actually deserves to change.

01

Start With Reality

Tell me what's driving you nuts.

Maybe clients are slipping through the cracks. Maybe the team keeps asking the same questions. Maybe nobody knows who owns what. Maybe every decision somehow still lands back on your desk.

You don't need to diagnose anything for me. Tell me what's happening and what you wish worked differently.

Symptoms are enough to start.

CLIENTS TEAM SYSTEMS FOUNDER WORKFLOW
What's
happening?
02

Follow the Work

Then I get into how it actually works.

This is where we stop talking about how the company is supposed to work and start looking at what really happens.

We follow the client journey, handoffs, responsibilities, communication, CRM, workflows, automations, documentation, and all the unofficial workarounds people use to keep things moving.

Follow the work, not the org chart.

1

Client enters process

Clear
2

Responsibility changes

Watch
3

Information disappears

Friction
4

Founder gets pulled back in

Result
03

Diagnose the Pattern

We find the problem under the problem.

A missed follow-up may look like a people problem when the real issue is ownership. A messy CRM may actually be a broken workflow. A struggling employee may be operating inside a system nobody ever clearly defined.

We separate the visible symptom from the condition creating it. Rebuilding everything is not the goal.

Fix the cause. Stop babysitting the symptom.

Missed follow-up Confused team Founder involved

↓

What keeps making this possible?

Root Cause

04

Strategy Meets Reality

Then we build what actually needs fixing.

Recommendations become operating changes. Depending on what we uncover, that may mean clarifying ownership, rebuilding a workflow, fixing the client journey, cleaning up the CRM, improving automation, documenting a process, or helping leadership finally resolve a decision that's been sitting too long.

The solution follows the diagnosis. Not the other way around.

Strategy has to survive contact with the business.

01

Ownership

02

Workflow

03

Client Journey

04

Systems

05

Documentation

06

Leadership

05

Prove It

Then we make sure it works without me.

The goal isn't to make your company dependent on another consultant. It's to leave behind clearer ownership, better systems, stronger delivery, and fewer things that require someone to remember the secret handshake.

We keep testing the change against the real business because something isn't fixed just because it looked good in the meeting.

Real use is the final test.

Does it work
in real life?
USE WATCH IMPROVE TEST

The Point

We aren't trying to make your company look more organized. We're trying to make it genuinely easier to run.

The Operator Lens

We don't inspect departments. We inspect the business between them.

Operational problems rarely stay inside one neat category. A client problem might actually be a handoff problem. A people problem might be unclear ownership. A CRM problem might trace back to a process nobody ever defined. The job is figuring out how all of those pieces are affecting each other.

Symptoms travel Causes overlap

Operator Question

What keeps making this problem possible?

Follow the friction across the business.

01

Ownership & Decision Flow

Who owns it? Who decides? What still rolls uphill?

02

Customer Journey

Where does the client experience start to fracture?

03

Processes & Handoffs

Where does work disappear between people or teams?

04

Systems, CRM & Automation

Does the technology reflect the real workflow?

05

Documentation & Knowledge

What does the business know only because Sarah remembers it?

06

Leadership & Accountability

Are expectations, authority, and accountability actually clear?

Lens What We're Looking At Why It Matters

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

We follow the client from signed contract through onboarding, delivery, follow-up, retention, and renewal — especially the places where clients get confused, delayed, ignored, or quietly dropped.

03

Processes & Handoffs

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

04

Systems, CRM & Automation

Does the technology support the way the company actually works, or has the CRM become a digital junk drawer while automation quietly makes a bad process happen faster?

05

Documentation & Knowledge

We identify what the company genuinely needs to remember, what currently lives inside somebody's head, and what needs to become usable documentation 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 authority.

Operator's Note

“If the same problem keeps showing up 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.

Fair questions. You're letting somebody look at how the company actually works — including the parts nobody puts in the sales deck. Here's what most founders want to know before we get started.

01

No diagnosis required. Tell me what's happening.

02

No preset engagement. Scope follows the problem.

03

No 70-page theater. The work has to be usable.

Short Answer · 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 company simply feels harder to run than it should. That's enough. Figuring out what's underneath it is part of my job.

Next Step

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

Depends on the Problem

A defined workflow or client journey issue might take a few weeks. Broader operational work can take several months. Some founders want ongoing advisory support as the business changes. I'd rather give you an honest scope after I understand the problem than invent a tidy timeline before I've seen the business.

Enough to Give Context

Enough to give me context, answer questions, and make decisions when those decisions genuinely belong to you. I'm not dragging you into every detail, but I'm also not disappearing into a cave for three weeks and returning with a 70-page deck explaining your own company to you.

Both

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

God, I Hope Not

If the tools you already have can support the company, we'll use them. I'm not interested in rebuilding an entire tech stack just so it looks like something changed. Sometimes the software really is the problem. More often, the process underneath it never made much sense.

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.

Then We'll Say So

Sometimes the bottleneck genuinely is capacity and the company 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.

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 situations show up. The goal isn't dependency on TSG. It's the level of support that actually makes sense for the company.

One More Thing

If the question you actually have isn't listed here, that's probably a better reason to have the conversation.

The First Conversation

You bring me what's happening. We'll start making sense of it.

Book a free 30-minute Strategy Call and give me the real version of what's happening inside the business.

What keeps breaking? What keeps coming back to you? Where is the team frustrated? Where are clients feeling friction? What simply feels harder than it should?

You don't need the diagnosis before we talk. That's what the conversation is for.

You Can Literally Start With

“Jeremy, here's the thing that's driving me nuts...”

Book a Free Strategy Call →

No pitch · No pressure · No corporate theater

What the Call Actually Looks Like

About 30 Minutes

You

“Here's what's going on.”

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

Jeremy

“Okay. Why is that happening?”

I'll start asking questions and looking underneath the symptom. Sometimes the thing driving you crazy isn't actually the thing creating the problem. That's usually where the useful conversation starts.

Together

“So what makes sense from here?”

If TSG can genuinely help, I'll explain what I think the next step should be. If you don't need a consulting engagement, I'll tell you that too.

Outcome

A clearer view of what deserves attention next.

Maybe that means working together. Maybe it doesn't. The point of the call is to make the situation clearer, not manufacture something to sell.

The Swink Group · How We Work

Start with the truth. Figure out the rest from there.