What's the difference between a "software company" and an "agency" — who should I hire?

Three years ago we handed our fleet tracking portal over to an ad agency that gave a killer presentation. The UI looked stunning, but the backend was pure spaghetti code. The second we crossed 50 drivers, the whole system crashed. Turns out it was built by a single freelance kid who then got drafted for military service, leaving us completely stranded. We had to rebuild the whole thing from scratch with a proper software house.

Run a very simple litmus test: Ask both companies, "Who designs your database schema and API architecture at the kickoff, and how many backend engineers do you have on your actual payroll?" If the agency hesitates or says "we work with external experts," drop them immediately.

The critical mistake here isn't bashing agencies; it's picking the wrong tool for the job. An agency drives customer acquisition; a software company keeps your operations running. Your logistics portal isn't a storefront, it's a piece of mission-critical machinery where a glitch could spoil tons of freight. At this budget data integrity trumps visual flair every time; the technical discipline of a software firm is non-negotiable.

Three key criteria that draw the line: 1) Team profile: Agencies lean heavily on designers and copywriters; software firms employ system engineers and architects. 2) Lifecycle: Agencies deliver and move on to the next campaign; software firms sign SLAs and handle 24/7 bug tracking. 3) Code quality: Agencies prioritize speed and aesthetics; software houses prioritize security and load handling.

in logistics, design is only there to make the screens easy to read. like nobody needs flashy animations on a truck tracking dashboard. definitely go with the software company, save yourself the headache.

The biggest weakness of software firms is their UI. They'll hand you an interface that looks like a 90s accounting app, claim "the backend is rock solid," and using it becomes absolute torture for your staff. If you go with a software company, definitely make sure to vet their design portfolio first.

Summary of the debate: Hire an agency for sales and brand image; hire a software company for operational integrations, databases, and business workflows. Since yours is a critical logistics portal, partnering with a software firm and keeping design quality in check via a side agreement is the safest route.

Timely topic.

Correct in theory, but it doesn't work that way in practice. Taking notes for two weeks yields better results than a six-month estimate.

Weekly written progress reports are much more useful than asking for dates. Hope this helps.

Thanks, that was the answer I was looking for. When making decisions, write down the worst-case scenario too, not just the best.

Good luck with that.

There's one point I'm curious about. If you don't write this down from the start, it leads to arguments later.

I completely agree. If you don't write this down from the start, it leads to arguments later.

That's all, sorry if I went on too long.

I can't fully agree with this. Weekly written progress reports are much more useful than asking for dates.

Start with a small trial; don't commit to everything at once. Good luck with that.

i can't fully agree with this but when we decide without measuring, we always end up in the same place.

There's a common mistake people make when doing this. Solutions that work at a small scale collapse when you grow; I learned this late.

I'm also curious if anyone does it differently.

Let me summarize what's been said so far. Code without setup documentation isn't yours, even if you have it.

We need to take it step by step. Ask who prepared the quote and who will actually do the work.

Taking notes for two weeks yields better results than a six-month estimate. Of course, it varies if your situation is different.

the answer above hits the nail on the head.. then trying to do this alone is the most expensive way.

of course, it varies if your sitation is different.