Buying guide
Custom software vs off-the-shelf software
Buy software when a reputable product already matches the process and will still be supported. Build when the process is the advantage, or when the workarounds around a product have become a second, worse product.
Buy when
The workflow is ordinary: standard accounting, ordinary email, a simple pipeline with no special record. The vendor’s integrations cover the systems you already run. You can live with their data model. The licence cost over three years is acceptable, including the seats you will actually need, not the ones in the first quote.
In that situation, custom software is a way to spend more to own a maintenance burden. We will say so.
Build when
The record is specific: a property and a viewing, a piece of gold, a shipment and a contract, a clinic diary with your rules. Or the packaged tool is in place and every team keeps a side spreadsheet because the tool cannot express the exception that happens daily. Or you are gluing three products together with exports and calling it an operation.
Build the gap, not a clone of the product you should have bought. A custom CRM that recreates a default sales pipeline is a poor project. A custom CRM that holds a brokerage’s listing and lead rules can be a good one.
The hybrid most companies need
Keep the ledger, the identity provider, and the commodity suite. Build the operational system they do not fit, and integrate. That is the ERP and CRM approach on this site. It is also how you stay able to leave a vendor later, because your process is not trapped in a configuration nobody can export.
Buy the commodity. Build the special part.
Buy when
- The workflow is ordinary
- The vendor integrations cover you
- The licence over three years is acceptable
Build when
- The record is the business
- Workarounds already cost more than the process
- You cannot live with their data model
A fair comparison
The three-year cost
Seats, add-ons, and the workaround staff time belong in the packaged number.
The special field
If everything important lives in a note, the package is already failing.
The exit
Ask how you leave either choice with your data.
A fair comparison needs four facts
- 01
Three-year licence
Seats you will actually need, plus add-ons.
- 02
The workaround
The sheet or note where the real record lives.
- 03
The special field
The thing the package cannot hold.
- 04
The exit
How you leave with your data, either way.
Marks buy-versus-build stays two answers
- 01
The special step
Build is tied to the part a package cannot model.
- 02
The commodity stays bought
Mail, accounts, and calendars are examples of what not to rebuild.
- 03
Licence pain is real first
A custom build is compared with the cost of the current workaround.
- 04
Both can be right
The article allows either outcome.
Questions we hear
Is custom always slower?
A narrow custom tool can be in use before a suite is configured, migrated, and worked around. A broad custom platform is slower than buying. Scope decides, not the word custom.
What about lock-in?
You can be locked into a vendor or locked into a codebase nobody else can read. Contracts should give you the code, the data export, and the accounts. Buying should give you an export too. Ask for both.
Where do AI features sit?
Inside whichever system holds the record. A separate AI subscription that cannot see your CRM will draft fluent and useless text.