Website or custom web app?
The useful distinction is the work people need to accomplish. A website can explain a service and receive inquiries. An application may need to manage records, permissions, and a process that continues after the first visit.
List the actions, not the pages
“Home, About, and Contact” describes a page list. “Understand the offer, see examples, and request an estimate” describes a visitor’s job. Start with the latter, then decide which pages and tools support it.
For a property business, photographs, practical information, and a clear inquiry route might be enough. Accepting real reservations introduces a different set of responsibilities: availability, conflicting requests, confirmation, cancellations, and possibly payments.
Use a website when the main job is communication
A business website is a sensible starting point when people need information, evidence, and a way to respond. It can connect to an existing booking or customer-management tool without rebuilding that tool.
A form still needs a complete journey. Visitors should understand what to enter, recover from errors, and know whether their inquiry was accepted. Test the form on small screens and with a keyboard as well as a mouse. Clear submission feedback is more useful than a decorative confirmation animation.
Consider an application when people manage ongoing work
A custom application may fit when staff repeatedly create, edit, assign, approve, or reconcile records and the existing tools leave important gaps. Define who can see or change each record and what happens when two people work on the same item.
Before commissioning a build, compare the required workflow with software you already use. An integration or a smaller extension may address the problem. A custom app also needs an owner for maintenance, access management, backups, and changes to connected services.
- Who uses it, and what can each person do?
- Which records must survive between visits?
- What are the important status changes?
- Which existing tools must stay connected?
- How will you export or recover your information?
Choose the smallest complete first release
Separate essential actions from conveniences. A dispatch prototype might demonstrate assignments with fictional bookings; a production dispatch system also needs the operational checks appropriate to real users and records. Those are different scopes.
Write one realistic scenario the first release must complete from start to finish. Use that scenario to discuss the work, dependencies, and acceptance criteria. The interface can grow after the core task is reliable.
What to take away
Bring the actions your visitors and team need to complete, the tools already in use, and one example of a successful end-to-end task.