Somewhere in your business right now, there is a process that doesn’t fit the software it lives in. Your team has invented workarounds: an extra spreadsheet, a shared inbox, a “just message K. Bee and she’ll sort it” step. It works, mostly. And every month it quietly costs you hours, errors and the occasional lost customer.
When that pain gets loud enough, businesses ask the classic question: should we buy something off the shelf, or build custom? After two decades of building systems, our honest answer is that the question is framed wrong. It is never all-or-nothing. Instead, the right question is: for this specific capability, is our way of doing it an advantage, or just a habit?
Where off-the-shelf wins, almost every time
Accounting, payroll, email, calendars, document storage, video calls: buy them. These are solved problems where your process should conform to the tool, because the tool encodes decades of best practice and compliance. Custom-building any of these is how projects go to die.
The same is true for standard CRM and e-commerce needs. If your sales process looks like most sales processes, a well-configured mainstream product will serve you better than anything built from scratch — cheaper, faster, maintained by someone else.
An engineering-led firm should tell you this plainly. If a consultancy’s answer to every problem is a custom build, they are selling billable hours, not outcomes.
Where custom earns its cost
Custom work earns its keep in exactly two places.
The first is your differentiator, the thing you do differently that customers choose you for. If your pricing model, logistics routing, booking flow or customer experience is genuinely unusual, forcing it into generic software sands off the edge that makes you competitive. This is where a custom application, or a custom module on top of a standard platform, pays for itself.
The second is the connective tissue. Off-the-shelf tools are built to be everything to everyone, which means they are rarely built to talk to your particular combination of other tools. Integration layers are the pipes that move data between your website, CRM, inventory, accounting, and reporting. They are almost always custom, almost always small, and almost always the highest-ROI code a growing business can own.
The hybrid pattern that actually works
The systems we build for clients usually follow the same architecture: standard products for solved problems, a custom layer where the business is genuinely different, and engineered integrations so the whole thing behaves as a single platform. The custom portion is often less than 20% of the system, but it is the 20% that makes the other 80% fit your business, not the other way around.
This pattern also protects you from the two classic failure modes. All-off-the-shelf businesses stall because their processes slowly deform to fit their tools. All-custom businesses drown because they maintain software that solves problems someone else has already solved better.
Count the full cost, not the sticker price.
Whichever way a decision leans, run the numbers over five years, not one. Off-the-shelf costs look small on a monthly basis and compound: per-seat pricing that scales with your headcount, paid tiers you get pushed into as you grow, and the hidden cost of staff hours spent working around the tool’s assumptions. Custom costs look large upfront and then behave differently: no per-seat fees, but a real ongoing obligation to maintain, patch, and evolve what you own. Budget roughly 15–20% of the build cost per year for that, and treat any estimate that omits it as incomplete.
The five-year view regularly reverses the instinctive answer. A THB 40,000-per-month workaround team is a THB 2.4 million, five-year cost in disguise. A custom integration that removes it can pay for itself several times over, but only if it was scoped by someone who priced the maintenance honestly. That is the decision worth getting right before you write a line of code.
Getting the decision right before writing code
The build-or-buy call should be made by someone who has seen both fail. Before any code, insist on three things: a map of the actual process (not the org chart version of what really happens), a hard look at whether the process should be simplified before being automated, and a total-cost view that includes maintenance, not just delivery. A surprising number of “we need custom software” conversations end with “you need two integrations and one process change”, which is a much cheaper sentence.
That is the value of senior capability at the decision stage. Junior teams build what you ask for. Senior teams tell you what not to build.
WereHumans provides exactly that: senior engineering and design capability, without the cost or commitment of building an in-house team. We’re based in Pattaya and work globally, and we’re happy to be the people who talk you out of a build you don’t need.
Have a build-or-buy decision on your desk? Call Eve on +66 89 354 9916 or visit werehumans.com.