Case study · Clean Fridays

Stylised cleaning marketplace calendar, route and payment motifs for Clean Fridays

Cleaning · marketplace · Marketplace platform + ops tooling

Clean Fridays: Australian cleaning marketplace with Stripe Connect

· 10 min read
  • cleanfridays
  • marketplace
  • stripe-connect
  • firebase
  • next.js
  • cleaning
  • melbourne
  • ndis

How cleanfridays.com.au books vetted cleaners across home, office, Airbnb and end-of-lease jobs using Next.js, Firebase Cloud Functions, Stripe Connect payouts, SMS and admin ops tooling.

Live project: Clean Fridays

Context

Clean Fridays is an Australian cleaning booking platform connecting customers with vetted independent cleaners for home, office, Airbnb and end-of-lease work. Hosts, NDIS introductions and B2B facility portals extend the same core booking and payout rails.

High-intent SEO includes book cleaners Melbourne, end of lease cleaning Sydney, Airbnb cleaning Brisbane and related city pages. Ranking those pages only helps if booking, payment and cleaner acceptance actually complete.

Operational problems a marketplace must solve

  • Matching and booking without phone tag between customer and cleaner.
  • Stripe Connect payouts so cleaners get paid while the platform takes a documented fee.
  • Status pipelines for offers, accepts, reminders, disputes and auto-reassign when someone drops.
  • SMS and email cost control so notifications stay reliable without runaway spend.
  • Admin visibility across cleaners, bookings, payments and exceptions.

Approach

The monorepo centres on Next.js (Vercel, Sydney) with Firebase Cloud Functions v2 in `australia-southeast1`, Firestore, Auth and Storage. Stripe and Stripe Connect handle customer charges and cleaner payouts. Twilio and Mailjet cover SMS and email with idempotency-minded runbooks.

Product surfaces include a multi-step booking wizard, chat-assisted booking, cleaner registration with document checks, Airbnb host jobs, NDIS provider flows, B2B organisation invoicing, and an admin dashboard for day-to-day ops.

Links from amir.melbourne to cleanfridays.com.au are `nofollow`. This case study captures marketplace and Stripe Connect intent for Melbourne cleaning operators evaluating a build vs spreadsheets.

What improved

  • Customers book online instead of coordinating every job by phone or DM.
  • Cleaners receive structured offers and Connect payouts instead of informal transfers.
  • Ops teams work from admin queues and documented payment remediation paths.
  • City and service SEO pages sit on the same platform that fulfils the booking.

When this pattern fits you

Fit for cleaning companies and marketplace operators who have outgrown Sheets plus bank transfers. If you only need forms, CRM and recurring job sync fixed, start on cleaning services or a workflow rescue before commissioning a full marketplace.

For owned reporting across jobs and invoices without a two-sided marketplace, see internal dashboards.