Developer Needed — Take My Existing Claude-Built CRM Live as ONE Unified, Multi-User Web App

I run an integrated real estate and renovation business (1% listing model, buyer representation, contractor/renovation jobs, and a 12-unit rental property) and have an existing CRM built as a single HTML file (via Claude/Claude Code) — dashboard, client cards, financials, tasks, timeline, documents, all currently running on localStorage on my own device. I need this taken to a real, production-ready system. THE CORE ARCHITECTURE DECISION (NON-NEGOTIABLE): I want ONE unified application, not separate apps for different roles. My business is one continuous funnel — a lead becomes a client, becomes a transaction, becomes a closed deal — and the system needs to reflect that. Role-based access control should happen inside one app, not by splitting data across multiple systems. If your proposal involves building separate apps for different user types, that's the wrong architecture for what I need — tell me why your single-app role-based approach works instead. WHAT I NEED BUILT: Migrate from a local, single-device HTML file to a live, cloud-hosted web app accessible from any phone or computer, by me and by my team A real backend and database (not localStorage) so multiple people can use it simultaneously without overwriting each other's work Basic authentication — individual logins per person Role-based access control, with at least these roles to start: Admin (me) — full access to everything: all clients, all financials, all settings, ability to grant/restrict access for other roles Transaction Coordinator — access to transaction-related data (documents, disclosure tracking, deadlines, timeline) on relevant clients; restricted financial visibility unless I grant more Lead Generation — can add new leads, log outreach activity, see lead status; restricted from financials and sensitive client details Built so I can add more roles later (property management admin, automation specialist) without a rebuild An activity log / audit trail — I should be able to see who changed what and when, especially for financial fields and client records (this matters for a multi-person system and wasn't something I'd thought to ask for until now — flag if you have a standard approach) Data backup and recovery — I need to know my client data is safe even if something breaks; tell me your approach Mobile-friendly — most of my own usage will be from my phone in the field; this needs to work well on a phone browser, not just desktop Reasonable load time and reliability — this needs to function as a daily-use business tool, not a fragile prototype ON DESIGN: I'm open to changing the visual design — what exists now was generated quickly and isn't something I'm precious about. What I care about is that the features that currently work (client cards, editable financials per client type, task management with custom labels, timeline logging, document storage/upload, dashboard with pipeline overview) exist in the new version — ideally improved, not regressed. If you have a cleaner design approach that better supports multi-user, role-based use, propose it. WHAT I NEED FROM YOU: Real experience taking a frontend prototype to a production multi-user web app — auth, database, hosting, all of it Specific, demonstrable experience with role-based access control — this is the core technical requirement of the whole project Comfortable working from and improving an existing codebase, not just rebuilding from scratch in your preferred stack for its own sake Clear communication about technical tradeoffs — I'm not a developer, so you need to explain your choices in terms I can actually evaluate (cost, reliability, what happens if X breaks) A realistic plan for ongoing hosting costs — I need to know what this costs me monthly after launch, not just the one-time build cost SCOPE & WHAT HAPPENS AFTER: This is a defined project with a clear deliverable: a live, multi-user, role-based CRM with the roles and features above. Ongoing maintenance, new feature requests, or automation work after launch can become a separate, recurring engagement if you're a good fit — but I'm hiring for the initial build first, so don't assume ongoing work is guaranteed. TO APPLY, TELL ME: What stack you'd recommend for hosting + auth + database for a small business CRM at this scale (roughly 15–30 active clients at a time, 3–5 total users) How you'd implement the 3 roles described above inside one app Your approach to data backup/recovery Your estimated timeline and total cost for the initial build 1–2 examples of similar multi-user, role-based systems you've built