About

A builder who came up in freight.

Chan Chum

Since I was a kid: remote-control cars, taking things apart, putting them back together. Bikes, motorcycles, cars, walls, apps. I've always been someone who sees a pile of parts and feels the finished thing before it exists.

That instinct landed me in freight forwarding eight years ago. Operations work became platform engineering, which became building entire systems from scratch. Then I spent the last two years going all in on AI. So now the work that would take a team of five, I build alone. Today I do the job of a one-person technology department for my full-time employer: platform architect, full-stack engineer, data engineer, product manager, IT. A company staffing those separately would need five to seven people.

Two things come out of that. First, custom software: the apps, internal tools, quoting systems, and integrations a business needs but can't get a vendor to build. A quoting system I rebuilt over a weekend now saves more per year than my salary. The deepest of those is Atlas, a data platform I built solo that turns a closed freight ERP into an open one: it ingests the data, exposes it through a secured API, and feeds reporting, CRM sync, and an AI assistant on one foundation. Second, business intelligence: 15 Power BI dashboards, and a 188,000-record analysis that showed exactly where to raise prices without losing deals.

I studied computer science, but I came up doing both the operations side and the code at the same time. That combination is the point. AI is the reason I'm fast.

Chan Consulting is what happens when I bring that combination to other small businesses. When you hire me, you're not hiring an agency. You're hiring the one person who does the work. Freight forwarding is where I proved it, but the pattern is the same in distribution, the trades, restaurants, dental, and professional services: operational data scattered across systems, decisions made in the dark, and someone who can build the fix without a four-person team.

How I work

Problem-led, not tool-led

I name the actual problem first, then choose the tool. Never the other way around.

Build first

When something breaks on a Friday, I have the replacement in production by Monday.

Outcomes over output

Every project has a number attached, whether that's dollars saved or hours your team gets back.

If your operational data is broken, disconnected, or doesn't tell you what you need to know, that's exactly what I fix.