Case study · Web app

Domio

I am building Domio from scratch, a home services marketplace for Germany: clients book cleaning with independent providers, and the marketplace takes a commission on each order. Full cycle: I described the product and architecture, drew the design system and logo, built a demo with client, provider and admin dashboards and translated it into four languages.

What the site looks like

All names, reviews, orders and amounts in the screenshots are made up demo data. Any resemblance to real people is coincidental.

Marketplace provider catalog with filters and provider cards
Mobile version: Provider catalog

The task

The client wanted a marketplace on the Helpling model: the company keeps no cleaners on staff but connects clients with independent providers and takes a commission on each order. The marketplace has three sides, client, provider and admin, each with its own dashboard and permissions. It starts with cleaning in Germany, then new services, countries and languages. The key question the whole logic depended on was settled with the client before development: the service is provided by independent providers, not by the company itself.

What was built

  • A spec before the first line of codeI described the marketplace modules, database, roles and permissions, payments with provider payouts and the cost of external services. For the production version I chose Laravel, Filament and Stripe Connect, and this plan sets the timeline and budget of every stage.
  • Design system and logoI built a design system and every page of the marketplace: the public part, sign-in and both dashboards. I drew the logo. On phones the site works like an app, with a bottom navigation bar.
  • Client and provider dashboardsBoth sign in by email or with Google, each into their own dashboard, and the database itself keeps other users' data closed. Clients see visits, orders and spending; providers get requests with the amount after commission, manage rates and schedule, and submit documents for verification.
  • Catalog and bookingProviders can be filtered by city, service, price, rating, language and available date. On a profile the client picks a day and time from the provider's calendar, sees the total right away and places the order.
  • An order from request to finishThe provider accepts or declines a request and marks departure, start and end of work. The client can cancel with a reason until work begins. Every step stays in the order history.
  • Admin panelThe admin has a panel of their own: an overview with the key numbers, all orders with the commission on each, users, reviews and the provider verification queue. Provider documents open through a temporary link.
  • Four languagesThe site works in Ukrainian, English, German and Polish, and the chosen language is remembered. Legal pages are always in German, since the German version is legally binding in this market.
  • A spec before the first line of code

    I described the marketplace modules, database, roles and permissions, payments with provider payouts and the cost of external services. For the production version I chose Laravel, Filament and Stripe Connect, and this plan sets the timeline and budget of every stage.

  • Design system and logo

    I built a design system and every page of the marketplace: the public part, sign-in and both dashboards. I drew the logo. On phones the site works like an app, with a bottom navigation bar.

  • Client and provider dashboards

    Both sign in by email or with Google, each into their own dashboard, and the database itself keeps other users' data closed. Clients see visits, orders and spending; providers get requests with the amount after commission, manage rates and schedule, and submit documents for verification.

  • Catalog and booking

    Providers can be filtered by city, service, price, rating, language and available date. On a profile the client picks a day and time from the provider's calendar, sees the total right away and places the order.

  • An order from request to finish

    The provider accepts or declines a request and marks departure, start and end of work. The client can cancel with a reason until work begins. Every step stays in the order history.

  • Admin panel

    The admin has a panel of their own: an overview with the key numbers, all orders with the commission on each, users, reviews and the provider verification queue. Provider documents open through a temporary link.

  • Four languages

    The site works in Ukrainian, English, German and Polish, and the chosen language is remembered. Legal pages are always in German, since the German version is legally binding in this market.

Result

Since July the marketplace has grown in weekly stages, and after each one the client checks the result on the demo under three roles, with test providers and orders. The whole order path works: from finding a provider and booking on the calendar to finishing the job. Next, following the ready spec, come the production version on Laravel and Filament, online payment via Stripe Connect with provider payouts, reviews, chat and notifications.

Start a project

Planning a marketplace
or a booking app?

Leave your email and a few words about your project, and I'll get back to you.

Vitalii Hura, full-stack developer

Vitalii Hura · UkraineOnline until 2 PM New York time and the full EU workday.

A spec, a diagram or screenshots. PDF, images, Word, Excel, up to 20 MB
Got it, thank you. I will reply to within a few hours on working days. A confirmation is on its way. If it is not in your inbox, check your Spam folder.
Reply within a few hours Price agreed upfront Direct or via Upwork

Prefer chat? Message me on Telegram or hire me on Upwork.