Buy the package when it fits. Build when the package is the workaround.
Buy a package when your process is close enough. Build when fighting the vendor’s model is the real cost.
Start with the object, not the demo
Packaged products are opinionated databases with a UI. An ERP assumes items, warehouses, purchase orders and a general ledger. A practice-management suite assumes matters, time entries and a billing run. A help desk assumes tickets, SLAs and a knowledge article. If your primary object is one of those, you should spend serious time in the package before you commission a replica. Replicating a mature product is how companies fund a worse version of something they could have configured.
A short checklist you can actually use
- Can the vendor’s primary object store yours without a shadow database?
- Can the worst weekly exception be done in the product, not beside it?
- Do you accept their upgrade and API schedule?
- Who will maintain a custom codebase in two years, named roles, not hope?
- Is v1 one workflow, or a rewrite of the company?
Bring the exception, not the brochure
If you can describe the object and the weekly workaround, we can tell you whether to configure, integrate, or build. Email sales@progley.com or use the contact form.