The short answer
Start by testing the software you already have. If it cannot do an important job, compare connecting your tools with building a custom app (software made for your business). Include the cost of keeping either option working.
Start with the job you need done
Ask the person doing the work to show you a recent example. Where do they get stuck? What do they copy by hand? What would a useful result look like?
Example — not a client result
“Our administrator needs to review a completed assessment, record the decision and let the learner see the result.”
This gives you something to test. “We need a dashboard” does not explain what the dashboard should help someone do.
Compare these three options
Use the same real task to judge each option. You may only need to fix one missing step.
Improve what you have
Look here first if: your current tool may already have the form, report or approval step you need.
Check: can someone complete the whole task, including an unusual case?
Watch for: paying for a higher plan just to unlock one feature.
Connect your tools
Consider this if: the tools work well, but staff keep copying information between them.
Check: where the correct record lives and what happens if a connection stops.
Watch for: extra charges, duplicate records and failed transfers.
Build a custom app
Consider this if: an important job still cannot be done well with the other options.
Check: can the first version solve one complete problem?
Watch for: ongoing fixes, backups, account access and support.
A useful stopping point: if your current software passes the test at a cost you can accept, you may not need a new app.
Compare the full cost
Ask for the same costs over the same period for each option. A low starting price can leave out work you still need.
- Getting started
- Setup, design, moving and cleaning records, and staff training.
- Keeping it running
- Subscriptions, hosting (where the app runs), usage charges, backups and support.
- Making changes later
- New features, updates, fixing errors and getting your records out if you leave.
Time saved can be useful even when it does not reduce payroll. Keep that separate from cash savings or extra profit.
Try five cases before committing
Write down what should happen in each case. Ask someone who does the work to check the result.
- A normal task: can the person finish it from start to end?
- A repeated request: does it avoid creating the same record twice?
- Missing information: does it explain what needs fixing?
- The wrong account: is private information kept from someone who should not see it?
- A broken connection: can someone see the problem and recover the work?
Keep this checklist
Your one-page project brief
Answer these before asking for a quote. Use made-up examples or remove names and identifying details; leave out passwords and private customer records.
- The job: what should someone be able to finish?
- The gap: what cannot your current tools do?
- The people: who uses it, and who approves the result?
- The limits: what budget and deadline must it fit?
- The handover: who controls the accounts, records and ongoing support?
Common questions
Is a custom app always more expensive?
No. The answer depends on what it needs to do and how much it costs to keep working. Compare a written list of requirements and full costs, not just starting prices.
Do we need AI?
Only if it helps with a specific task and you can check its answers. Copying a form response may need a simple rule, not AI (artificial intelligence, including software that generates or interprets information). See the checklist before automating a task.
Who should own the app and its records?
Agree this in writing before work starts. Cover account control, access to the code, rights to use it, getting your records out, and what happens when the supplier leaves.