Field guide
Map the work before shopping for software
A useful app decision starts with the handoff that is breaking today.
Start with a real week
Choose one normal week and follow a job, inquiry, appointment, or invoice from start to finish. Write down every place someone looks for information, re-enters a detail, asks for an update, or waits for approval.
Do not begin with a list of desired features. Begin with the moment that makes a customer wait, makes a teammate hunt for an answer, or makes an owner do the same work twice.
Name the handoff
Most small-business friction sits between people and steps: an inquiry moves to a quote, a booking moves to delivery, a completed job moves to an invoice, or a document moves to approval.
For each handoff, name the sender, receiver, required information, and signal that it is complete. That is the requirement an app has to support.
Decide what must change
Keep the first scope narrow. A good first decision might be: appointments need to update availability without three text messages. It is not: replace everything we use.
If the process has no owner or definition of done, fix that before buying software. An app can preserve a clear process. It cannot invent one for the team.