A job changes hands, and someone has to explain it all over again. The office has the customer's request. The person doing the work has photographs on a phone. A manager keeps the latest instructions in a message thread. Finding out where things stand means asking around.
That is a useful place to begin a conversation about an app. Before deciding what to build, look at the work that keeps getting interrupted and the information people need to carry it through.
Follow one job through the business
Consider a small installation company. This is a hypothetical example: the office books a visit, an installer records measurements and someone else prepares the estimate. When a measurement changes, the person preparing the estimate needs to know which version to use.
An app could keep the job details together and show when they were updated. The installer could add a note at the visit, and the office could see that the job is ready for an estimate. Whether that would help depends on how the company works now.
Ask the people involved to walk through a recent job. Look for repeated copying, missing details or a handoff that depends on one person remembering to send a message. Note how often the problem occurs and what it takes to put right.
A confusing process may need a decision about responsibilities before it needs software. Agree who records the measurement and who approves a change. The app needs a clear process to support.
Work out who would come back to it
An internal app has a defined audience: the people doing the work. A customer app has to earn a place in someone's routine. Describe the reason a customer would open it again after the first visit.
For a business with recurring orders, that reason might be checking an order's progress or placing the same order next week. For an occasional service, a clear website and a confirmation email may do the job. An account should give someone a useful way to manage their information.
Check the software you already pay for. It may have an unused booking feature, a shared job record or a setting that addresses the difficulty. Compare that option with a custom tool, including the effort of moving information and teaching people a new routine.
Choose the form after the task
An app can run in a browser. Staff might open a secure link on a phone at a job, then use the same system on a computer in the office. An app built for iPhone or Android is another option when the task calls for it.
There is overlap between these approaches. As MDN's guide to progressive web apps explains, web apps can be designed for installation and offline use. Support for particular features depends on the device and browser, so the intended task needs testing on the equipment people will use.
Tell the developer where the work happens. A basement with poor reception raises different questions from an office with a reliable connection. If someone records information offline, decide how they will know it has been saved and what happens when two people change the same record.
Accessibility affects the choice as well. Ask users what makes their current tools difficult. A person working on a phone may need larger controls or fewer fields to complete a task. Include those needs in the first version and test with the people who raised them.
Give the first version a job you can assess
For the installation company, the first version might cover the handoff from a site visit to an estimate. Leave room to learn from that route before adding purchasing or payroll.
Decide what a useful trial would show. Could the office prepare the estimate without calling the installer for missing details? Could someone find the latest measurement without searching messages? Use sample records before trying a small set of real jobs.
Plan for the ordinary work after launch. Someone needs to manage access when staff leave, answer questions and arrange fixes. Agree who holds the business's accounts and data, how information can be exported and what ongoing services will cost.
Before a consultation, write down one recurring task and the point where it becomes difficult. Bring an example with private details removed. That gives us something specific to examine together and a way to judge whether an app would help.
