Does your business need an app at all?
If your customers cannot find your hours, fix the website. If your staff cannot agree which spreadsheet is current, agree on one list. Neither problem automatically calls for a new app.
Name the work that is getting stuck
Write one sentence: “We copy the same job details into three places.” Then follow one job through the process. Where is information entered, checked, and changed?
A new app can add a fourth place unless it replaces a specific step. Identify that step before discussing screens or features.
Try the smallest change first
A form may be enough when people submit the same few fields. A spreadsheet may be enough for a small shared list. A saved page may be enough for a reference guide. An existing product may already handle reminders or bookings better than a small custom project could.
Test the simple option with a real correction, not just a new entry. If staff can complete the job reliably, stop there. You do not owe the problem a more impressive solution.
Look for a reason to build
A small app becomes more useful when the same task repeats, the screen needs to work well on a phone, or the process needs guardrails that a loose sheet cannot provide. Offline use may also justify a different approach.
Write down who will maintain it. If nobody can own updates, backups, or questions from staff, resolve that before building. A one-person app can be small, but it cannot be ownerless.
Run a short trial
Choose one task and agree how you will judge it. Count the whole effort, including checking and correcting the result. Ask staff which step still feels awkward.
If the new process is not easier, keep the records you need and stop the experiment. Learning that a shared form is enough is a useful result.
Your choice stays on this device. It is not sent to the site owner.