“Our team can build this” is among the most common things a prospect says, and the usual sales reflex is to wave it away. That is a mistake. Sometimes the customer is right. The better approach is to put the two options next to each other and compare them honestly. I will take a side at the end, but let me lay out the case for each first.
The case for building
Building gives control. The tool fits the company’s process exactly, data stays in-house, and there is no vendor to depend on or renew with. If the capability is central to what makes the company different, building can be right: a bank’s core risk model, a logistics firm’s routing logic. Engineers also like building, and a motivated team may deliver quickly.
The visible cost looks low, too. Engineers are already on payroll, so a proposal to spend a few months of their time seems cheap next to a vendor’s annual quote. That feeling is the weak point of the whole argument.
The case for buying
Buying gives speed, a product already used and fixed by many customers, and ongoing improvement paid for by a larger base. The vendor owns security patches, compliance updates and integrations. Above all, buying turns a large, uncertain, internal project into a known, recurring fee.
A comparison with numbers
Suppose a company in Nagpur wants an internal approvals-and-workflow tool. A vendor quotes ₹24 lakh a year. The internal team says three engineers can build it in six months. Assume each engineer costs ₹30 lakh a year fully loaded, which is an assumption for the example, not a benchmark.
Building: three engineers for six months cost 3 × 30 × 0.5 = ₹45 lakh. After launch, one engineer is needed part-time to fix bugs, add requests and keep up with dependencies and security updates. If that is one full engineer’s worth of time, it costs ₹30 lakh a year. Over three years, the cost is 45 + 2.5 × 30 = ₹120 lakh. Buying over three years is 3 × 24 = ₹72 lakh.
On these numbers buying wins by ₹48 lakh. But look at what moves the result. If the build really needs only a quarter of one engineer’s time afterwards, the build cost over three years drops to about 45 + 2.5 × 7.5 = ₹63.75 lakh, and building is cheaper. So the true question is not “who is cheaper” but “how much ongoing effort does this thing need?” Most internal tools need more than their authors predicted, because requirements grow, people leave and documentation is thin.
Costs both sides forget
- Opportunity cost: the three engineers could be building something customers pay for. This is usually the largest number and the one never written down.
- Key-person risk: when the one engineer who understands the tool resigns, the company owns undocumented software.
- Time to value: six months of building is six months without the benefit. A purchased tool might be live in weeks.
- On the buy side: integration effort, change management, per-seat growth, and the lock-in that comes from migrating data later.
My side
For anything that is not the company’s core differentiator, I would buy, and for a salesperson I would say so plainly. But I would not say it by attacking the customer’s engineers. Ask instead: Who will maintain it in year three? What else would the team build with that time? What is the cost of waiting six months? Let them answer. If their answers are strong, you may be talking to a customer who really should build, and an honest salesperson saves both sides a wasted pilot.
Where I think the vendor loses is when the product is only a modest improvement on what a competent team could assemble. If your value is a thin wrapper, “build” is a fair threat. Strong products win this argument through things a single team cannot easily replicate: depth, benchmarks from many customers, compliance certifications, support, and a roadmap that is not hostage to one company’s priorities.
One more practical point. A hybrid often exists: buy the commodity layer and build only the part that is uniquely theirs, connecting through APIs. Offering that path, rather than defending a monolith, is frequently how the argument ends.
Figures and names in the examples are illustrative.
Leave a Reply