Website, app or automation: how to start with the problem

People often arrive with a solution label: a new website, an app, a portal or automation. A clearer starting point is the current situation — who is trying to do what, where the process stalls and what a better outcome would look like.

Describe the process in order

Follow one real piece of work from start to finish. Note where information is requested, copied, checked, approved and followed up. This usually reveals whether the problem is customer-facing, internal, between existing systems or a mixture of all three.

Choose a website when the problem is customer-facing

A website is often the right answer when people need to understand services, find a location, request a quote, book, order or make contact. Better content, forms and navigation can solve these needs without requiring a separate app.

Choose an app or internal tool for structured work

An internal tool becomes relevant when staff need different access, jobs move through stages, records require approval, or management needs consistent reporting. It can be focused on one workflow rather than trying to run the whole business.

Choose automation when the tools already work

If the main problem is people moving information between functioning systems, automation may be the better answer. Predictable steps such as creating a record, sending confirmation, notifying a staff member or scheduling follow-up can often happen without replacing either system.

Expect combinations

One business problem can involve a public website, an enquiry form, an automation and a small staff dashboard. Design the overall workflow first so each part supports the same process.

A real example: online ordering

Scott’s Burgers did not need a newly invented ordering platform. The existing commercial kitchen needed a website, Square ordering and payments, and a practical kitchen workflow using a tablet and thermal printer. The technology choices followed the operational need.

Questions to answer before features

• Who is using this?
• What are they trying to complete?
• What happens now?
• Where does it go wrong?
• What information is needed?
• Who decides what happens next?
• What is the smallest useful improvement?

Once those answers are clear, unnecessary features tend to fall away. The result may be an existing platform, a website improvement, one connection between systems or a focused custom tool. The technology comes second.