/ Project: Car service, Kraków (Poland) · 2026 /

A car service website with fixed prices, online booking and repair status

Case study: a Kraków car service site in three languages with model-specific prices, slot booking, worn-part photos and repair status.

Key decisions Slot booking and repair status without phone calls
Type
Websites
Industry
Car service and repair
Year
2026
Build stages 5 weeks
  1. Brief & research ≈ 1 wk
  2. UX/UI design ≈ 2 wk
  3. Development ≈ 2 wk
  4. QA & launch ≈ 1 wk
  • Astro
  • Sanity
  • Twilio SMS
  • Google Calendar API

Product screens 06

  1. 01 Home
  2. 02 Services and prices
  3. 03 Online booking
A car service website with fixed prices, online booking and repair status
  1. 04 Repair status
  2. 05 Fleet service
  3. 06 Reviews
About the project

A website for an independent car service in Kraków, in three languages, where drivers see the price for their car, book a free slot, approve extra work with photos and follow the repair status without calling.

  • Model-specific prices Every service priced for the exact model, with the job duration.
  • Lift slots Bookings go into free time from the schedule, so no lift is double-booked.
  • Photos and approval Worn parts shown in photos, extra cost only after the client agrees.
  • Repair status Repair stages on the order page and an SMS when the car is ready.
01 · The brief

An independent four-lift car service in Kraków took bookings by phone. Half its clients are foreigners with little Polish, so calls dragged on or never happened. Prices were given after inspection, and clients worried about being overcharged. All day the mechanics answered “is my car ready” calls, and a paper diary caused double bookings on the lifts.

02 · What we built

We built a company website on the Lite plan in Polish, English and Ukrainian. Services are priced for the specific car model, and bookings go into free slots from the lift schedule, so two cars never land on one lift. After inspection the mechanic sends photos of worn parts, and the client approves extra work in one click. Repair status is visible on the order page, and an SMS arrives when the car is ready. Google Maps reviews are shown on the site.

  1. Before Phone booking in Polish, so foreigners do not call.

    After Online booking in three languages into a free slot.

  2. Before The price is known only after inspection, clients fear overcharging.

    After A model-specific price before booking, extra work only with photos and approval.

  3. Before Mechanics answer “is my car ready” calls.

    After Repair status on a page and an SMS when the car is ready.

03 · The client’s path

How a person moves through the product, from the first step to the result the business needs.

  1. Picks a service

    Sees the price for their car model and how long the job takes.

  2. Books

    A free slot from the lift schedule, confirmed by SMS.

  3. Approves work

    Gets photos of worn parts and approves extra cost in one click.

  4. Collects the car

    Follows the repair status and gets an SMS when the car is ready.

04 · What is inside the project

  1. Service prices for the car model instead of “from 99 zł”

  2. Online booking into free slots from the lift schedule

  3. Photos of worn parts and one-click approval of extra work

  4. A repair status page and an SMS when the car is ready

  5. The site in Polish, English and Ukrainian

  6. Google Maps reviews on the site

Forecast

Within the first 2–3 months, 40–60% of bookings go online, “is my car ready” calls roughly halve, and lift double bookings all but disappear. A guideline, not a promise.

05 · Architecture

How the product is put together: from what the user sees to the data and services behind it.

  1. User Opens the site on a phone or a computer
  2. Interface What a person sees and taps
    • Astro
  3. Logic Rules, roles and scenarios
    • Twilio SMS
    • Google Calendar API
  4. Data & integrations Where the data lives and what the product talks to
    • Sanity

06 · How a project like this is built

Total: 5 weeks
  1. 01 ≈ 1 wk Brief & research Goals, audience, page structure and what the product must do
  2. 02 ≈ 2 wk UX/UI design Prototype, design of the key screens and the mobile version
  3. 03 ≈ 2 wk Development Front end, CMS, integrations and animation
  4. 04 ≈ 1 wk QA & launch Device testing, speed, SEO groundwork and launch

Typical phase split for a project of this size

07 · Services in this project

Next project Law firm, Berlin (Germany) · 2026 A law firm website with fixed fees, consultation booking and a client portal Legal services

Solutions for a specific job

Ready-made scenarios for your case — with examples and indicative pricing.

More projects

All projects →