Herafy GEE: Home-services marketplace

Who it is for

If you run a home-services marketplace, you know how requests get lost in phone calls and chat groups. Customers ask who is coming and when, and your team searches chats for each job. In Herafy GEE the customer books a craftsman in the app, the job reaches one named craftsman, and both sides follow it to completion.

How a working day runs

The customer searches for a service such as AC maintenance, compares independent craftsmen and companies by rating and years of experience, and sees who is available now. They pick one, describe the problem and set the address. With an independent craftsman they also book the day and time slot. If they choose a company, the company assigns the job to one of its craftsmen from its portal. The job reaches the craftsman's app among their new requests, with its description and address. The customer then follows its status and the craftsman's arrival on the map, and can call them from the app. Admins see every job, who it went to and where each craftsman is on one dashboard.

What makes the difference

• Craftsmen sign up as independents or under a company, so customers find both in one app.
• Each company assigns jobs to its craftsmen and tracks their work from its portal, without seeing other companies' jobs.
• The craftsman's app keeps working when the signal drops on site and syncs once the connection returns.
• The customer app, the craftsman app and the dashboard read the same job, so everyone sees one status.

How it is built

We built the customer and craftsman apps in Flutter, so both run on phones from one codebase. The company portal and admin dashboard use React, because dispatchers need tables and maps on a wide screen. Firebase holds each job's state, so every update reaches all sides as it happens. Maps shows the craftsman's route, and the craftsman app is offline-first: it works without a connection and syncs later.