I’m building an online marketplace where garages can lost their availability and customers can book servicing slots in real time. The solution has three distinct workspaces that need to be coded and wired together: • Vendor dashboard – Each service provider must see a calendar-style view of confirmed and pending bookings. From that same screen they can collect payments, track their analytics (revenue, top services, booking trends) and respond to customer reviews. • Customer portal – Drivers will register via social media and land in a personal garage that stores every vehicle they own. The portal keeps full service history, surfaces tailored maintenance tips and automatically reminds them when the next service is due. • Super-admin area – I’ll manage vendors, customers, listings and payouts from a single control panel with role-based permissions. Account creation relies on social media & email-password combination option is required. Stripe (or a comparable gateway we agree upon) will handle transactions inside the vendor view. For the analytics layer any modern stack is fine—chart.js, Metabase, or built-in dashboards—as long as metrics update in near real time. Acceptance criteria 1. Responsive SPA or PWA works smoothly on desktop, tablet and mobile. 2. Booking flow from customer search to vendor confirmation completes in under 30 seconds on a standard 4G connection. 3. Calendar entries sync instantly across vendor dashboard, customer portal and admin panel. 4. Automated reminders trigger on schedule and log to the customer’s service history. 5. Code is version-controlled in Git with clear setup instructions so I can run the project locally. If you’ve shipped similar multi-tenant SaaS platforms or appointment engines, this build should feel familiar. Let’s discuss tech stack preferences, timeline and any questions you have about the user flows. If quoting, you MUST be able to demonstrate similar past projects