NDA A website with online booking and payments.
We designed and built a website for a local service company: customers choose services, see available times, book and pay online. As a result, enquiries increased.
The business needed more than a brochure site. It needed a working sales tool: clear service presentation, real-time booking, payments and enquiry handling in one system.
- Challenge
- Simplify the path from discovering a service to booking, generate more enquiries and reduce manual handling.
- Studio role
- UX analysis · UI/UX design in Figma · Development · Integrations · Admin panel
- Outcome
- Customer enquiries increased, while booking, payments and enquiry handling now work in one flow.
Abstract illustration. Real layouts, screens, the client name and links are not shown because of an NDA.
Customers struggled to book a service quickly
The company offers several service areas, so visitors arrive with different needs: some know exactly what they want, others are comparing options. To find out about availability and price, people had to call or message a manager. At that point, some potential customers simply never got in touch.
Internally, the process also took time: enquiries had to be clarified by hand, and website updates depended on a developer.
We found where the business was losing enquiries
We reviewed the customer journey from the first visit to a confirmed booking, the service structure, the mobile experience and how enquiries reached the team. This produced a clear list of design and development decisions.
- Choosing a service needed a clearer structure and dedicated pages.
- There were too many manual steps between interest and booking.
- Customers needed to see real availability instead of waiting for a reply.
- The team needed all enquiry details in one place.
We designed a clear path from service to booking
We began in Figma with the site structure, prototypes of the key flows and UI/UX design for desktop and mobile. The focus was on service pages, time selection, booking and payment, so customers always understood the next step.
Once the designs were approved, we built the website on Laravel, connected online booking and payments, set up enquiry delivery to staff and created an admin panel for independent content updates. Technical SEO and analytics were planned before launch.
More enquiries and less manual work
After launch, customer enquiries increased. People can choose a service, see available times and complete a booking without calling, while the team receives enquiries with the right context and spends less time clarifying details.
Exact figures and client details are not published because of an NDA.


What we built
- The catalogue and booking work with an external scheduling service, with availability based on staff, service duration and occupied slots.
- Checkout combines online payment, instalments and payment on site.
- Enquiries are stored in the database and sent to staff by messenger and email, with page context and advertising source.
- A custom admin panel lets the team edit pages, services, the blog, media and integration settings.
- Reviews and portfolio content have a fallback if external services are unavailable.
- Technical SEO and analytics cover metadata, structured data, the sitemap, redirects and key user actions.
Services in this project
The next project
your idea.
Tell us what you want to build or improve. We’ll define the main journey, necessary features and the first step together.
A few sentences are enough to start. You don’t need a finished specification.
