Building a Connected Website
and Booking System

The existing setup kept the website, the booking process and day-to-day customer administration apart. That left Matthias with limited control over the customer experience and too little space to explain his approach, his specialist services and his work on hoof health. The project therefore started from a broader goal than improving a website: to build an owned digital environment that is clear and credible for customers and practical for Matthias in daily use.

For a mobile farrier business, a booking is more involved than picking an available slot. One appointment can cover several horses, different services with different durations, a stable address that differs from the billing address, travel between yards and an interval before the next visit. Matthias also needed a workable way to keep customer, horse and hoof-care records without private journal information ending up in an external marketing system.

The relaunched site presents Matthias under the public identity Matthias Greye · Hovvård & Hovslageri and went live on 26 July 2026. Alongside the core service pages it carries deeper content on Duplo, specialist shoeing and common hoof problems, which is where most customers arrive with an actual question rather than a general interest.

That structure does two things at once. It gives a prospective customer enough context to judge whether Matthias is the right person for their horse, which matters more than price in specialist work. And it establishes a content foundation that can be extended systematically into a hub around hooves, hoof care and hoof health, rather than a fixed brochure that has to be rebuilt when the business develops.

The booking application at boka.hovar-hast.se gives customers a branded Swedish self-service journey instead of a generic scheduling widget. Standard booking tools assume one customer, one service and one slot. A mobile farrier visit does not work that way, and forcing the business into that model would have pushed the complexity back onto Matthias.

A customer can add several horses to one visit, give stable and billing information separately, and later reschedule or cancel through a protected link. Service selection carries duration with it, so the calendar reflects the real length of a visit rather than a fixed block.

The administrative interface brings appointments, customers, horses, services, locations, hoof-care journals, photographs and follow-up dates together in a single view. Lovable and Supabase form the operational source of truth, with authentication and row-level security controlling what is accessible.

The practical value is in the follow-up interval. Hoof care is recurring work, and the record of what was done last time, on which horse, with which observations, is what makes the next visit efficient. Keeping that alongside the appointment data, rather than in a separate notebook, is what turns the system into something used daily instead of something maintained reluctantly.

An ICS feed makes the schedule visible in the calendar Matthias already uses. This is a one-way feed, not a two-way synchronisation.

The project created a coherent customer journey across discovery, evaluation, booking and follow-up. Customers can understand the offer and manage their appointment through a dedicated branded experience. Matthias has a single operational view of what a mobile hoof-care visit actually requires, and the routine communication around each appointment is triggered automatically.

What matters beyond the launch is ownership. The website, the booking application, the customer and horse data and the content structure all sit inside a system Matthias controls and can extend. The site can grow into a content hub for hoof care and hoof health without a rebuild, and the booking application can take on new services without changing how it works.