Web development for domestic cleaning booking platform

Hi James,
There are just too many clarification question to post here. Do you have a complete development documentation of this project? something that lists all the features, functions, processes etc and maps the user journey?
There is a great need for a clearly defined scope with a project of this complexity to ensure that we deliver as expected.

Hi James,

Thanks for the invite.

A few important questions before finalizing scope:

1. Is the frontend already connected to any API structure, or is backend integration completely open?

2. Do you already have designs/screens for customer, cleaner, and admin portals?

3. Will cleaner matching be postcode-based only, or distance/radius-based?

4. Do you require SMS notifications as part of the MVP?

5. Should cancellations/refunds be automated through Stripe?

Looking forward to discussing the workflow and reviewing the existing frontend structure.

Best Regards.

* What is the frontend currently built with, and is it already wired to any auth/API logic or still mostly static UI?

* How do you want cleaner service areas defined: postcode list, radius from a base location, towns/boroughs, or custom zones?

* Should the system auto-assign cleaners immediately based on availability and area, or should admin approve/adjust assignments before confirmation?

* For recurring cleaning, should customers be charged immediately on booking, after each clean, or on a repeating subscription schedule through Stripe?

* Do customers need full self-service rescheduling/cancellation rules, or should changes go through admin approval at MVP stage?

* How should cleaner availability work: fixed weekly availability, ad-hoc calendar slots, holiday blocking, or all of these?

* Are booking prices fixed, or do they change based on property size, frequency, location, extras, or cleaner type?

* Do you already have email templates/booking rules prepared, or should those workflows be defined during the backend build?

Hi James, Your project sounds clear overall, though I’d love to confirm a few details before proceeding — what framework is the current frontend built with, should cleaners be auto-assigned or manually managed by admin, do you already have Stripe subscriptions configured, and how would you like cleaner coverage areas handled between postcode radius, cities, or custom zones? Also, should customers fully manage rescheduling/cancellations themselves, and do you want deployment plus hosting setup included in the MVP build?

A few quick questions:
1. Is the frontend already connected with APIs or only UI is completed?
2. Do cleaners need their own login dashboard separately?
3. Will bookings be auto-assigned or admin will manually assign cleaners initially?