When is an off-the-shelf app enough?

Most businesses do not need another app to maintain. They need a job to stop eating the week. Start by writing down that job from beginning to end: what arrives, what changes, what leaves, and who approves it.

Buy when the ordinary version fits

Try an existing product when your workflow is common and its core steps already match the way your team works. Test the export, permissions and the difficult edge cases before committing. The demo’s smooth path is only part of the job.

Build when the gap is the job

A custom tool can make sense when the important part is specific to your business: an unusual handoff, a connection between systems, or a repeated decision that existing products cannot support clearly. Be precise about that gap. “We want AI” is not a specification.

Compare the whole cost

• Buying: subscriptions, setup, training, workarounds and the cost of leaving.
• Building: design, implementation, hosting, updates, support and ownership of the code and data.
• Either: the time your team spends checking, correcting and operating it.

Try the smallest complete workflow

Choose one beginning and one finished result. Keep real approval points in place. Test a missing field, a duplicate request and a failed connection. A useful small system should explain what happened and leave a person able to recover.

Ask who owns tomorrow

Before you sign, name the person responsible for fixes and changes. Get the handover, data export and exit terms in writing. A good system should make your business easier to run after the person who built it has moved on.

The right choice can be a standard product with a small integration around it. You do not have to replace everything to fix one expensive gap.