DEV Community

Tzvi Boxer
Tzvi Boxer

Posted on

Tzvi Boxer Explains Why Process Beats Platforms in Most SMBs

Walk into enough small and mid-sized businesses and you will see the same pattern: a shelf of platforms and a shortage of process.

CRM, project tool, help desk, chat, accounting add-ons, a couple of “AI” seats, three reporting views that disagree. The stack looks busy. The work still depends on one person’s memory and a spreadsheet that is not supposed to exist.

I am a technology consultant. I am not anti-platform. I am anti-platform-as-substitute-for-process. After more than two decades helping organizations modernize systems — and after seeing budgets vanish into licenses that never changed how work actually moved I can say this plainly: in most SMBs, process beats platforms.

Not forever. Not as ideology. As sequence. Get the process right, and almost any competent platform becomes useful. Skip the process, and the best platform becomes an expensive mirror of confusion.

What “process” means when you are not a Fortune 500 company

Process does not mean a 40-page SOP binder nobody opens. For an SMB, process means a few operational truths written down and followed:

  • Who owns each critical workflow
  • What “done” means in language the team shares
  • Where the source of truth lives for customers, money, and delivery
  • How exceptions get handled without inventing a new path every time
  • What gets measured weekly so problems show up before customers do. That is enough to beat a new platform purchase most of the time. Platforms multiply whatever you already do. If what you already do is unclear, multiplication is not progress.

Why SMBs reach for platforms first

Platforms feel like action. A demo is scheduled. A credit card is charged. A kickoff email goes out. Leadership can say “we invested in systems.”

Process work feels like admitting the current path is messy. It names owners. It forces trade-offs. It sometimes reveals that the pain is not software — it is unclear roles, conflicting incentives, or a workflow that was never designed for today’s volume.

Buying is emotionally easier than clarifying. That is why shelves fill up while handoffs stay broken.

AI has intensified the pattern. Urgency culture pushes teams to “add AI” before they can describe the job the AI is supposed to support. The result is familiar: pilots without owners, outputs without review standards, and renewals nobody wants to defend in daylight.

Platforms cannot fix what process never defined

Consider a common SMB failure mode: sales, ops, and finance disagree on when a deal is “closed.” Each team’s tool is correct according to its own fields. Leadership asks for a dashboard. A vendor sells a connector. The dashboard now displays disagreement in higher resolution.

No platform resolves a definition problem. A definition does.

Or take support: tickets bounce because categories were invented ad hoc, SLAs were never agreed, and the urgent” label means something different to every agent. A new help desk will not create shared meaning. Training, categories, and ownership will.

Technology should amplify a process that already makes sense. Asking software to invent sense is how SMBs burn budget.

A process-first sequence that still respects tools

Here is the sequence I use with SMB leaders who want better systems without collecting more logos.

1. Pick the pain that costs time or trust every week

Not the trendiest initiative. The recurring friction: re-keying, status chasing, report rebuilding, missed follow-ups, inventory surprises.

2. Write the current path as it really happens

Include the spreadsheet, the text message, and the exception only one person knows. If the room argues about the map, you have found the real project.

3. Agree on owners and definitions before vendors

Name who owns the workflow. Agree what “complete,” “closed,” or resolved” means. Choose one source of truth per domain. Do this on a whiteboard if you have to. Do it before the demo.

4. Fix what does not require a purchase

Clean fields. Retire duplicate sheets. Document the handoff. Train people on tools you already pay for. Many “technology problems” shrink dramatically here.

5. Only then choose the smallest platform move that fits

Sometimes that is configuring what you own. Sometimes it is a lightweight automation. Sometimes it is a migration. Sometimes it is AI with human review. The point is fit after clarity — not fashion before it.

6. Put a review date on the calendar

In 30–60 days, ask what changed in hours, errors, cycle time, or customer trust. Keep, adjust, or cancel. Platforms without review become furniture.

Where platforms still matter

Process-first is not process-only. Good platforms matter when:

  • Multiple people need concurrent access to the same reliable records
  • Compliance or audit trails are non-negotiable
  • Volume exceeds what spreadsheets can safely hold
  • Integrations reduce genuine re-keying after definitions exist
  • Automation can execute a process the team already trusts

In those cases, platforms are leverage. The difference is timing. Buy after the process can be stated. Not instead of stating it.

How AI fits the process-beats-platforms rule

AI is a platform category with louder marketing. The same rule applies.

If your intake categories are unstable and your knowledge lives in one person’s head, a model will scale inconsistency. If your process for drafting, reviewing, and publishing is clear and your data is usable — AI can shorten the middle of the work with oversight.

I recommend AI when process readiness exists. I recommend process work when it does not. That is not conservatism. That is fiduciary sense with someone else’s budget.

A one-meeting test for SMB leaders

In your next leadership meeting, ask only these:

  1. Which weekly pain costs us the most time or trust?
  2. Can we describe the current path without arguing for ten minutes?
  3. Who owns the outcome — with calendar time?
  4. What definition must be shared before any tool can help?
  5. What will we not buy until those answers exist?

If the room struggles, you do not have a platform gap. You have a process gap wearing a software costume.

The competitive edge for SMBs

Large enterprises can sometimes survive platform sprawl with headcount and program offices. Most SMBs cannot. Their advantage is speed and clarity — the ability to decide, document, and improve without a twelve-month transformation theater.

Process is how that advantage stays real as you grow. Platforms are how you encode it once it is real.

In most SMBs I advise, the winning move is not the next logo on the stack. It is the next shared definition, the next named owner, and the next boring handoff that finally works without heroics.

Process first. Platforms second. AI when both are ready.


About the author: Tzvi Boxer is a technology consultant and AI strategist based in Columbia. He helps organizations modernize systems, streamline operations, and decide where AI and automation actually add value — and where they don’t. Remotely, he works with Optimal Targeting on practical AI and high-authority content strategy. He is the author of The Practical AI Playbook. More at https://www.tzviboxer.com/.

Top comments (0)