Backend Architect Needed for Custom CRM SaaS – Phase 1 (API + Database)

I am building a custom CRM SaaS for service-based businesses (automotive detailing, PPF, tint, and other field service companies).
This project is being built to be scalable and sellable as a standalone SaaS product, not a one-off internal tool.

Phase 1 is backend-only.
This is not a UI-first or template-based project. No mobile app work in Phase 1.

The goal of Phase 1 is to design and implement a clean, well-architected backend foundation that future web dashboards and mobile apps will connect to.

⸻

Phase 1 Scope (Backend Only):
• Database schema & migrations
• API design (REST or GraphQL)
• Authentication and role-based access control (admin / manager / technician)
• Customer and asset management (vehicles)
• Appointments that support multiple jobs under one appointment
• Job status workflow and job timer system (auditable, per job)
• Notification logging (SMS/email triggers such as reminders, on-the-way, arrived)
• Invoices with paid / unpaid tracking
• Basic reporting endpoints (revenue, jobs per tech, average ticket, time per job)
• API documentation and basic deployment setup

Phase 1 deliverable is a working backend platform, not a polished frontend.

⸻

Technical Expectations:
• Strong backend experience (Node.js, Python, or similar)
• Solid relational database design (PostgreSQL/MySQL preferred)
• Experience with RBAC, reporting, and scheduling logic
• API-first mindset
• Clean, maintainable, well-documented code
• Repo must live in my GitHub from day one

Experience building SaaS platforms or CRMs is strongly preferred.

⸻

Engagement Structure:

This project will start with a paid architecture + backend implementation phase.
Long-term work is available if Phase 1 is successful.

I am not looking for the cheapest bidder — I am looking for the right backend architect.

⸻

Required to Apply (Important):

Your proposal must include answers to the following:
1. How would you model one appointment with multiple jobs, each with its own status and timer?
2. How would you store job timers so they are auditable and accurate?
3. One example of a SaaS or CRM backend you personally architected (not just UI work).

Proposals that do not answer these questions will not be considered.