Helping businesses

Understand the business first. The tool comes second.

Before I recommend anything, I want to know how the work actually gets done — who touches it, where it stalls, and what it costs when it goes wrong.

I enjoy the part most people skip: sitting with a business and learning how it really operates. Not the org chart version — the real one, where someone keeps a spreadsheet on the side because the system doesn't do what they need, and everyone has quietly agreed to work around a step that stopped making sense years ago.

That's where the value is. Once you understand the process and the people running it, the right improvement is usually obvious — and it's often smaller and cheaper than anyone expected.

How I approach a problem

Questions before solutions.

  1. Learn the operation

    Walk the process end to end. Who is involved, what triggers each step, what information moves between them, and where the same work gets done twice.

  2. Find where it actually hurts

    Time lost, customers confused, staff frustrated, revenue delayed. If a problem can't be described in one of those terms, it may not be worth solving yet.

  3. Fix the process before adding tools

    Automating a broken process just produces bad results faster. Sometimes the improvement is removing a step, clarifying an owner, or changing the order of the work — no software required.

  4. Introduce technology only where it earns its place

    When a tool is genuinely the answer, keep it as simple as the problem allows and make sure the people using it understand it.

  5. Check whether it worked

    An improvement that nobody adopted isn't an improvement. I'd rather hear that something didn't help and adjust than declare victory early.

Where I focus

The problems I enjoy working on.

Workflow improvement

Mapping how work moves between people and removing the handoffs that lose information or stall progress.

Process optimization

Cutting the steps that exist only out of habit, and making the remaining ones clear enough that anyone can follow them.

Operational efficiency

Finding the routine work that quietly consumes hours each week and deciding whether it can be simplified, reassigned, or removed.

Automation

Taking repetitive, rules-based tasks off people's plates so their time goes to the work that needs judgment.

AI-assisted solutions

Using AI as a practical tool — drafting, summarizing, and helping build things faster — applied to real problems rather than for its own sake.

Internal tools

Simple systems that give a team one clear place to track what matters, instead of scattered spreadsheets and memory.

Business websites

A clear, fast, honest web presence that answers the questions customers are actually asking.

Customer experience improvements

Fixing the moments where customers get confused, repeat themselves, or wait without knowing why.

A real example

Anzures Boxing

A local boxing gym running on paper, text messages, and memory — the same pattern I've seen in plenty of small businesses.

Before building anything, I spent time understanding how the gym actually operated: how new people found it, how membership was tracked, how interested visitors were followed up with, and where information was getting lost. The technology decisions came out of that conversation, not ahead of it.

What exists today

  • A live public website that answers the questions people were calling to ask, at anzuresboxing.com.
  • A private admin dashboard for members and leads, with a foundation for payment tracking. It's built and in use internally — not public.

What's planned, not built

  • Event management and ticketing
  • Online payments
  • Reporting

I list the unfinished parts deliberately. Being clear about what's actually live is the same honesty I brought to recommending products to customers — and it's what makes the rest believable.

Technology is a tool. The job is solving the business problem.

How I think about every project

I'm not trying to be the most technical person in the room. I'm trying to be the person who understands the business well enough to know which problem is worth solving, can explain it clearly to the people who build the solution, and can tell whether it actually worked.

Let's connect

Tell me about the part that isn't working.

If your team is looking at a process that costs more time than it should, I'd enjoy that conversation.

Send an email Connect on LinkedIn