Notes

What I’ve learned building the systems businesses run on

No listicles and no AI slop. These are the questions clients actually ask me on the first call — costs, trade-offs, and the compliance details nobody warns you about — written out properly so you can decide before you ever contact me.

Everything here comes out of work that is currently running in production: a custom transportation management system a US carrier dispatches on every day, an AI voice agent that dials newly registered broker authorities, and the operations software behind several smaller businesses. When I quote a number, it is a number I have invoiced or paid. When I describe a failure mode, it is one I have had to fix at 2am.

What these notes cover

Three subjects, because those are the three places I actually have scars. If a topic isn’t here, it’s because I haven’t shipped enough of it to write anything you couldn’t get from a search.

The economics of software that fits

What a build genuinely costs versus what you are already paying in subscriptions, where per-seat pricing quietly starts making staffing decisions for you, and how to run the payback math honestly — including the cases where renting wins and you should not build anything. Start with the custom vs. off-the-shelf TMS comparison, then run your own numbers in the calculator.

Logistics and TMS builds

Dispatch boards, load lifecycles, driver settlements, document handling and the integrations that carriers and brokers live inside. Written from maintaining a TMS that has carried thousands of shipments for a working fleet, not from reading vendor marketing. See the SHM Transport case study for the long version.

AI automation that survives production

Voice agents, call compliance, workflow automation, and the difference between a demo that impresses a room and a system that runs unattended for months. Mostly: what breaks, what it costs to run per month, and which parts still need a human in the loop. More on the AI automation page.

Who writes these

I’m Rajan — a software engineer and founder with over a decade of building, and more than 200 projects delivered for clients across the US, UK, Australia and India. I don’t run a content team, and nothing here is ghostwritten or generated. New notes go up when I actually learn something worth passing on, which works out to roughly one or two a month rather than a publishing schedule.

If a post answers your question and you never contact me, that is a completely fine outcome — it is most of the reason I write them. If it raises a question instead, say so directly and you’ll get a straight answer, usually within the hour.

Got a question these don’t answer?

Ask me directly — I answer within the hour, and I’ll tell you if the honest answer is that you don’t need me.

Prefer email? hello@buildwithrajan.com — a real answer within the hour.