Skip to content
Start of content

My Work · The operating files Zamboanga City, Philippines · U.S. businesses

I want the damn thing to work.

It was never a ladder. It was a pile.

Army. Construction. DJ work. Marketing. Customer success. Operations. CRMs. Consulting. Businesses of my own. Government contracting.

Some of that happened in order. Some of it overlapped. Some of it became a business, some of it was a job, and some of it just taught me something useful. This page doesn’t pretend it was a plan.

The pile, sorted by where it ended up

Now part ofThe Swink Group

  • Operations
  • Customer Success
  • CRM & automation
  • Consulting

Now part ofJeremy Allen Swink, LLC

  • Gov’t contracting

Now part ofSwink Entertainment

  • Entertainment & DJ

Carried intoEverything since

  • U.S. Army
  • Construction
  • Marketing

Runs throughAll of it

  • Entrepreneurship

That’s more or less what I do for a living, too. Take the pile. Find out where things actually belong.

SYS-01Fault board

The stuff I notice first.

Walk me through a business and these light up before anything else. None of them are exotic. That’s kind of the point. Most businesses aren’t broken in some dramatic way. They’re held together by hand.

Faults detectedCommon · Fixable · Usually ignored

  1. F-01Work gets stuck and nobody can say where.
  2. F-02Nobody clearly owns it. Everybody kind of does.
  3. F-03Information disappears between one person and the next.
  4. F-04Clients get a different experience depending on who they talk to.
  5. F-05The founder is the bottleneck. Everything waits on one person.
  6. F-06The software gets blamed for what is really a process problem.
  7. F-07The workflow only exists in somebody’s head.
  8. F-08The same decision gets made again. And again.
  9. F-09It looks organized. Somebody is holding it together manually.
  10. F-10The people doing the work understand the problem better than the process does.

F-10 is usually the fastest way in. Ask the people doing the work.

Founder’s phoneNo system

  • NowWhere is this?
  • NowWho owns this?
  • NowDid anyone follow up?
  • NowWhat happens next?
  • NowWhy did this client fall through?
  • NowWhy am I involved in this again?
Before
  1. Clear ownership
  2. Visible work
  3. Defined stages
  4. Consistent updates
  5. Useful reporting
  6. Fewer founder interruptions

Founder’s phoneOperating system

No new questions.The answers are already where everybody can see them.

After (mostly)

SYS-02Wiring diagram

Operations isn’t a folder of SOPs.

It’s the machinery connecting what the business decides to what the customer gets, and everything in between. The order matters. Technology comes after you know what you’re trying to do.

Wired in this orderTop down

  1. 01DecisionsWhat is the business actually trying to do, and who gets to decide what?
  2. 02Customer journeyWhat should a client experience, start to finish?
  3. 03OperationsWho does what, in what order, and what “done” means.
  4. 04People & leadershipWho owns it, and do they have the authority to act on it?
  5. 05TechnologyNow the software. The CRM should show reality, not create a second version of it.
  6. 06CapacityWhat the business can handle without the founder in every loop.

Automation should reinforce a good process.

Wired the usual wayTech first

  1. 01TechnologyBuy the software. Surely it fixes things.
  2. 02OperationsWhatever the software happens to allow.
  3. 03Customer journeyImprovised, one client at a time.
  4. 04People & leadershipFigure it out.
  5. 05DecisionsStill the founder. Every time.
  6. 06CapacitySee: founder.

Congratulations. You automated the confusion.

SYS-03Altitude

From the boardroom to the weeds.

I’m comfortable at both ends. I can think about where a business is going, then disappear into the CRM to figure out why a workflow fired twice. Pick an altitude.

30,000 ftStrategy

What is this business actually trying to become?

What I’m looking atWhere the business is trying to go, and which decisions the founder should stop making alone.

Same instinct at every altitude: watch how it actually works, find where it breaks, figure out what should happen instead, build something people can use.
I’ve been running that play since junior high

SYS-04Currently running

What’s plugged in right now.

Three things with their own names and their own websites. They sell their own services over there. Here’s what each one actually is.

Operating

The Swink Group

Make the business easier to run.

For founder-led businesses. Scattered decisions, messy workflows, inconsistent client delivery and weak visibility get turned into a clear operating system people can actually follow.

  • Operations
  • Customer success
  • Client operations
  • Systems
  • CRM
  • Automation
  • Executive advisory
  • Remote Assistant placement & integration

Nota VA agency a marketing agency an automation shop generic consulting

Pursuing federal work

Jeremy Allen Swink, LLC

My U.S. business entity. Veteran-owned where it applies.

It’s also the vehicle for government contracting. I’m pursuing U.S. federal work in the same territory I’ve been working in all along.

  • Management & operations consulting
  • Process improvement
  • Customer success systems
  • Workflow design
  • CRM implementation
  • SOP development
  • Strategic planning

On

Swink Entertainment

DJ, entertainment, production.

I’ve had a long connection to DJ and entertainment work. This isn’t some hobby I hide from the “serious” business stuff. It’s another thing I built.

SYS-05Parts bin

Something is always on the bench.

I’m almost always building or testing something. Not all of it deserves to live. That’s fine. That’s how you find out.

On the bench, usually several at once

  • Websites
  • CRM systems
  • Automations
  • Internal tools
  • AI agents
  • Business concepts
  • Operational systems
  • Contract opportunities
  • Media projects
  • Personal projects
  1. Becomes a businessSometimes.
  2. Becomes a useful systemMore often.
  3. Gets abandonedThat’s fine. It still taught me something.

Not everything I touch turns into a company. I’m not going to pretend it does.

SYS-06Floor plan

Eight rooms. One room.

All of this happens in one office in Zamboanga City, working with businesses in the U.S. Sometimes that means U.S. hours while my family is living a normal evening around me. The room has a lot of jobs.

A floor plan of one office, overlapping zones: consulting office, operations command center, CRM lab, government contracting desk, website workshop, AI experiment room, gaming room, household storage with ten file boxes, and a door out to Projects. PROJECTS → 1 CONSULTING OFFICE 2 OPS COMMAND CENTER 3 CRM LAB 4 GOV’T CONTRACTING 5 WEBSITE WORKSHOP 6 AI EXPERIMENTS 7 GAMING 8 HOUSEHOLD STORAGE NOT TO SCALE · NOT THE ACTUAL LAYOUT · ZONES OVERLAP ON PURPOSE
One office, Zamboanga CityTen file boxes, for the record
  1. Consulting office
  2. Ops command center
  3. CRM lab
  4. Gov’t contracting desk
  5. Website workshop
  6. AI experiments
  7. Gaming room
  8. Household storage

ZamboangaUTC+8

U.S. East CoastUTC−5/−4

When the U.S. workday starts, it’s evening here.

Next room Projects This page is how I work. That one is what’s on the bench right now.

Still writing the story.

© 2026 Jeremy Swink

Set in Barlow Condensed, Newsreader & IBM Plex Mono · Built in Zamboanga City