A service company received enquiries through several channels, checked availability manually and kept history in messengers. We keep the client anonymous while explaining the product decisions.
The starting point
The old website was a brochure. Visitors could read about services but could not select a time or confirm a booking. Managers copied details into spreadsheets and replied manually. The goal was therefore not a visual refresh but a connection between acquisition and operations.
The customer journey
Each service received a clear page. A visitor selects a direction, date and available slot, enters contact details and receives confirmation. Availability is checked again on the server so two customers cannot reserve the same slot. The portal displays appointments, status, documents and support.
The manager workflow
Every request enters one list. The record contains contacts, service, time, notes and change history. Statuses identify new, waiting, confirmed and completed work. Permissions keep system configuration away from ordinary staff.
Technical decisions
Bookings, orders and users share one data model. Validation runs both in the browser and on the server. Notifications are separated from core logic, so a new channel does not require a rewrite. Analytics records completed registrations and orders rather than only page views.
The lesson
No single feature created the value. A clear offer, short booking flow, shared database, permissions, statuses and measurable funnel transformed the website into an operating tool.