Case study · Home services

Home services booked, dispatched and paid in one place.

A marketplace where customers book a technician, vendors run their teams, and the platform handles chat, dispatch and payment.
Client
JOBIQ
Sector
Home services
What we built
Customer app, vendor portal, admin console and the API behind them.
Platform
Flutter app for iOS and Android, Next.js portals, NestJS and MongoDB API.

In short

JobIQ is three products that have to agree with each other: a customer app, a vendor portal and an admin console. Bookings, technicians, catalogue, chat and reporting all live in one API, so a job booked on a phone appears on the vendor's board and in the admin's numbers at the same moment.

The brief

Three audiences, one booking.

A customer wants a job done, a vendor wants to run a team, and the operator wants to see all of it. Each needs its own screens, and none can be out of date.

What had to be true

  • A booking flow a customer finishes

    Service catalogue, time, address and payment without a call back.
  • A vendor board that runs the day

    Technicians, jobs in progress, completions and chat with the customer.
  • One source of truth

    Booking, catalogue, chat, notifications and reports in a single API, so nothing is retyped.

What we did

We built the API first, then three faces for it.

Customer, vendor and admin are views on the same data, which is why they never disagree.
01

One API, three clients

Bookings, technicians, catalogue, chat and reporting modelled once in NestJS and served to the app, the vendor portal and the admin.

Same record, three screens.

02

Job states the vendor can act on

Booked, in progress, completed, with a map for the technician and a chat thread per job.

The board mirrors the app in real time.

03

Subscriptions and reports built in

Vendor plans, settings and reporting in the admin so the operator can run the marketplace without a developer.

Operations without tickets.

What changed

A marketplace that runs without a phone call.

What the three products give each side.

3

products on one API: customer app, vendor portal, admin

Per job

chat, map and status, visible to customer and vendor

Self-serve

vendor plans and reporting managed in the console

Technology

What this was built with.

Chosen to fit the problem and the team who owns it now.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5verified reviews on Google