When a business decides it needs software help, the first question is usually “who should build it?”. The better first question is “what kind of help do we need?”. There are four common answers, and they suit very different situations.
Build: a product made for you
Choose this when your process is genuinely distinctive and no existing product fits without bending your business around it. You bring the problem; the partner plans, designs, engineers and launches the solution. It costs more up front, and you get software that fits exactly, and that you own.
Adopt: start from something that exists
Choose this when the problem is common (HR records, approvals, document control, delivery tracking) and speed matters more than uniqueness. Starting from a working product and configuring it around your process is faster and cheaper than building from scratch. Ask how far it can be customised and who does the customising.
Extend: add people to your own team
Choose this when you already have a product team and a roadmap, but not enough people. The partner's engineers and designers work inside your tools and rituals. The questions to ask are about standards and continuity: who reviews the code, and what happens when someone leaves?
Operate: a reliable owner for live software
Choose this when the software already exists and needs someone to keep it healthy: monitoring, fixes, security patches and steady improvement. This is often the most neglected need, and the one that decides whether software keeps paying off after launch.
Most engagements combine them
In practice these overlap. A build turns into an operate. An adopt grows a few custom features. An extend team ends up owning a product area. The point is not to pick a box; it is to be clear about what you need now, so the partner can shape the engagement around it.
