What custom software actually replaces
It is almost never a competitor's product. It is WhatsApp, a spreadsheet, and someone's memory.
Vinay Kumar
When a business asks about custom software, the comparison in their head is usually against a product they have seen advertised. In practice the thing being replaced is almost never a competitor's product. It is three WhatsApp groups, an Excel file with a version number in the filename, an approval that happens over email, and one person who knows how it all actually works.
That matters because it changes how you judge the investment. Against a polished SaaS product, a first version of custom software looks sparse. Against the real incumbent — scattered tools and institutional memory — even a modest internal panel is transformative, because for the first time there is one place where the answer lives and an audit trail explaining how it got there.
The honest test is whether your process is genuinely unusual. If your workflow is the standard one for your industry, buy the product; you will get more for less and someone else maintains it. Build when the workflow is the business: a pricing rule nobody else has, an approval chain specific to how you are regulated, an integration between two systems that were never meant to meet.
The second test is ownership. Buying means your operating data lives in someone else's schema, and the cost of leaving grows every month. That is a perfectly reasonable trade for a commodity function like email. It is a worse trade for the process that differentiates you.
The third is the boring one: who maintains it. Custom software is a thing you now own, which is an advantage only if the handover was real — repository, infrastructure, runbooks and a team that can actually change it. Without that you have swapped a subscription for a dependency on a specific agency, which is the worst of both.
If you want to argue with any of this, that is what hello@valentir.in is for.
