Build a secure multi-firm client management web app (Apex CRM pilot MVP)
$250-1200 AUD
Posted 1 minute ago
•
Ends in 6 days
$250-1200 AUD
Paid on delivery
Apex CRM is a client management product for professional services firms (law, accounting and financial advisory). We have a front-end shell (installable web app, responsive for phone and desktop, offline page, service worker) but no server, database or login, so data only lives in the browser. We need the smallest working version that one firm can use for a 60-day pilot. MUST HAVE 1. Accounts and login: email and password sign-up and sign-in. Passwords hashed with Argon2, bcrypt or PBKDF2 with a high iteration count. Sign out. Stay signed in across phone and desktop. 2. Firms (multi-tenant): each firm's data is private. A user from one firm must never see another firm's data. Explain how you enforce this. 3. Users and roles: an Admin can invite Members by email. Roles: Admin and Member. 4. Clients: add, edit, search and delete. Fields: name, firm or company, email, phone, address, notes, tags or status. Search by name and company. 5. Notes and history: dated notes on each client, showing who wrote it and when. History stays with the firm, not the individual user. 6. Works on phone and desktop: responsive, installable as a web app, data synced through the server. 7. Basic audit trail: record who created, changed or deleted a record and when. Admin can view it. 8. Hosting and security basics: HTTPS only. Data in an Australian region if the host offers one (say so if it does not). No secrets in front-end code. Daily backups. OUT OF SCOPE (do not quote for): billing and subscriptions, tiers, TOTP and device fingerprint login, SAML single sign-on, live location sync, push notifications, public API, offline write queue, native app store apps. ACCEPTANCE TESTS 1. Sign up as a new firm; the user becomes Admin. 2. Add a client with all fields. 3. Add a note and see it in the client's history. 4. Search for the client by name. 5. Sign out and back in on a phone and see the same data. 6. Invite a Member, who signs in and sees the firm's clients. 7. Sign up as a second, different firm; it cannot see the first firm's clients. 8. Delete a client; it is gone and the action appears in the audit trail. DELIVERABLES A live HTTPS URL to test. Full source code in a repository owned by the client, with a short README (how to run, deploy and back up). Admin access to the hosting and database accounts, in the client's name. A short written note on how data is separated between firms and how passwords are stored. OWNERSHIP The client owns all code and work product. The developer signs a confidentiality agreement before seeing the full shell files. No reuse or resale of the code. WHAT APPLICANTS SHOULD INCLUDE Similar apps they have built (links). The stack they would use and why. How they would keep each firm's data separate. Fixed price and timeline split into milestones (suggested: 1 login, firms and users; 2 clients and notes; 3 sync, audit trail and polish). When they can start. Applicants should state their own timeline; no target date has been set. BUDGET Up to AUD 1,200, fixed price, paid by milestone through the platform's milestone payment option. If the full scope does not fit, applicants should quote the smallest version first (login, firms, clients and notes) and price invites and the audit trail as a second stage. Applicants message through the platform.
Project ID: 40805363
About the project
40 proposals
Open for bidding
Remote project
Active 3 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
40 freelancers are bidding on average $750 AUD for this job


Apex needs more than a login screen: the pilot must let staff use the same firm-owned records across devices without exposing another firm’s data. I’d connect the existing shell to Supabase Auth and PostgreSQL in its Sydney region. Passwords stay with managed authentication; every client, note and audit entry is tied to a firm. Database row-level security checks firm membership on each request, rather than relying on the interface to hide records. Admin invitations would run through a server-side function, with no privileged keys in the app. I’d deliver in three milestones: firm sign-up, login and roles; clients, search and dated notes; then cross-device testing, deletion audit, deployment and handover. I’d test the two-firm isolation and phone sign-in scenarios explicitly. I’d also confirm the hosting plan provides daily backups before launch. I can start once the confidentiality agreement is signed and I have the shell repository. The source and hosting accounts will be yours, with a README covering deployment, backups, data separation and password storage. Do you already have a preferred hosting account, or should I set up Supabase in your name?


Hi, I understand you need a secure Apex CRM pilot backend connected to your existing responsive web app. I can build the smallest working MVP with email login, secure password hashing, firm-based tenant isolation, Admin and Member roles, client records, dated notes, search, sync across phone and desktop, audit history, HTTPS deployment, backups, and a short setup guide. I will keep secrets out of the frontend and make sure every request checks the signed-in user’s firm before reading or changing data. The work can be split into login and firms, clients and notes, then invites, audit trail, testing, and deployment. I will use JavaScript with a clear API Development structure so the source remains easy to run and maintain. Do you already have a preferred backend/database host with an Australian region, or should I propose a suitable option for the pilot? I can provide the repository, live test URL, hosting/database access in your name, and the written security notes. Please start chat and let’s discuss the shell, hosting choice, and milestones.


I can build the Apex CRM pilot around your existing responsive installable web-app shell, keeping the implementation focused on the stated acceptance tests. Recommended stack: Node.js/TypeScript with PostgreSQL and a secure REST API. PostgreSQL row-level security plus server-side firm-scoped authorization will ensure every query is restricted to the authenticated user’s firm; firm IDs will never be trusted from client input. Passwords will use Argon2id, sessions will use secure HTTP-only cookies, HTTPS will be enforced, secrets will remain server-side, and daily backups will be configured in an Australian hosting region where available. Suggested milestones: 1. Authentication, firm creation, roles, invitations, and secure tenant boundaries. 2. Client CRUD, search, dated notes, history, and responsive synchronization. 3. Audit trail, deletion tracking, deployment, backup setup, README, and security documentation. I will provide a live HTTPS test URL, client-owned repository access, hosting/database administration under your accounts, and clear deployment and backup instructions. I will review the shell after the confidentiality agreement and start promptly, with scope kept practical for the pilot budget.


Hi there, I build cross-platform mobile apps for iOS and Android, including JavaScript, Web Development and API Development. Recent work includes a React Native app with social login, location search and service packages. For "Build a secure multi-firm client management web app (Apex CRM pilot MVP)" I would keep one clean codebase that is fast and easy to maintain. How I would approach it: - Confirm the screens, user flows and the backend or APIs needed - Build in milestones with test builds you can try on your phone - Prepare the app for store submission at handover Do you already have designs for the screens, or should I help with the UI as well? Message me and I will share a similar app I delivered. Umair


Moving a firm's client records out of the browser and onto a server, with no firm ever able to see another firm's data, is what will decide whether this pilot is trusted. The closest thing I have is a sample SaaS dashboard with logins and roles. I would use Cloudflare Workers with a SQL database, served over HTTPS only, with passwords hashed using PBKDF2 at a high iteration count and sessions kept in secure cookies so one sign-in carries across phone and desktop. Every table would carry a firm ID, and the server would take that ID from the signed-in session, never from anything the browser sends. Every query would filter on it, so a second firm simply gets empty results. I would prove it with your seventh acceptance test and write it up in the short note you asked for. The first piece I would finish is sign-up as a new firm, Admin login, clients with search, and dated notes that show the author and stay with the firm. Invites, the audit trail and sync polish follow in the later milestones. The risky part is the Australian region. I will check what the host offers and tell you plainly if it cannot be pinned there. Do you want the existing shell wired to the new server as it is, or can I adjust its screens where needed? Is the pilot firm's data coming in fresh, or does something need importing?


Hello, Apex CRM’s critical risk is tenant isolation: every client, note, invitation, and audit event must be scoped to the authenticated firm, never merely hidden in the UI. I would connect your existing PWA shell to a Node.js/TypeScript backend with PostgreSQL, secure password hashing, server-side authorization, HTTPS deployment, Australian-region hosting where available, and daily backups. I’ll deliver the MVP in milestones: 1) signup, login, firms, roles, and invitations; 2) client records, search, notes, and history; 3) synchronized responsive data, audit trail, deployment, README, and security documentation. Acceptance tests will guide implementation and verification. My experience building SaaS platforms, API integrations, and full-stack systems is directly relevant. I can deliver the first working pilot milestone within 7 days, with source code and hosting/database access maintained in your accounts. I’m ready to review the shell after the confidentiality agreement and begin with the data model and tenant authorization layer. Best regards, Bohdan


Hello. I understand that developing a secure multi-firm client management app is crucial for your pilot program. Ensuring data privacy between firms is vital, and the multi-tenant architecture will be a key focus. One aspect that stands out is the need for robust security measures like password hashing and data separation, which are essential for maintaining client trust and compliance. I have previously developed a similar multi-tenant application where I successfully implemented user roles and data isolation, ensuring that each firm's data remained confidential. The outcome you're aiming for is a seamless user experience across devices, allowing firms to manage client information effectively while keeping their data secure. To achieve this, I would prioritize a strong authentication system and a clear audit trail. What specific measures do you envision for ensuring data separation across different firms? Thanks, Artiom.


Hi there, Thank you for sharing such a clear and well-scoped project outline. I have extensive experience delivering secure, multi-tenant web applications for professional services, including CRM systems and audit trails. My past projects include multi-firm SaaS portals and role-based management apps (links available on request), with a strong focus on data privacy and compliance. For Apex CRM, I propose a robust stack such as Node.js (Express) for the backend and PostgreSQL for the database, with authentication handled via secure password hashing (Argon2 or bcrypt). Each record will be tagged with a firm ID, and all queries will be strictly filtered server-side by the authenticated user’s firm, enforced at both API and database levels to ensure complete separation. No cross-firm data exposure is possible even if endpoints are manipulated. I will ensure HTTPS-only hosting, daily backups, and deploy to an Australian cloud region if supported (e.g., AWS Sydney). The PWA will remain installable and responsive, with data syncing securely through the backend. The audit trail will log all critical changes, viewable by Admins only. I am confident delivering a pilot-ready MVP, and can provide a clear README, handover of all hosting/database credentials, and a summary note on data separation and password handling. I am ready to sign your confidentiality agreement and begin promptly. Looking forward to helping you build a secure, reliable MVP for your pilot. Best Regards


Hi Building a secure multi-firm client management web app for the Apex CRM pilot MVP requires robust handling of user accounts and firm data segregation. The core technical challenge here is ensuring a secure, multi-tenant architecture where each firm's data remains private. Implementing database row-level security with firm-based scopes will achieve this, ensuring privacy while enabling scalability. My experience as a full-stack developer, with a focus on JavaScript and secure database development, is a perfect match for your needs. Previously, I built a CRM system for a financial advisory meeting similar requirements, employing a PostgreSQL backend with role-based access controls, successfully keeping client firms' data separate and secure. I noticed your emphasis on using either Argon2, bcrypt, or PBKDF2 for password hashing, which aligns with my approach in previous projects to enhance security. I can help bring Apex CRM to life with a live URL to test and a detailed README for deploying and maintaining the system. Let’s walk through how I plan to structure the data separation and talk more about making this pilot a success. Thanks, Shammi


Apex CRM needs a secure backend to move from browser storage to a real multi-tenant system where firms' data stays completely isolated and audit-traceable. I'd build this in three stages aligned to your milestones. Stage 1: Node.js/Express API with PostgreSQL, user authentication (Argon2 hashing, JWT tokens), and firm-level data scoping enforced at the database query layer, every SELECT/INSERT/UPDATE filters by firm ID from the authenticated user's context. No cross-firm data leaks. Stage 2: full client CRUD, timestamped notes linked to firm (not user), basic audit logging. Stage 3: sync logic via HTTP polling, admin audit trail view, and deployment to a secure Australian host with HTTPS, encrypted backups, and confidentiality agreement. I'd start with your existing front-end shell, integrate the API, test all eight acceptance criteria, then hand over the repository and hosting credentials to you. Regards, Savi


Hi, I’m confident I can build the smallest secure MVP for Apex CRM: a responsive, installable web app with firm-level isolation, login, clients, notes, and auditability. My approach would use a clean server-backed architecture so each firm’s data is separated at the database and authorization layer, with passwords stored using a strong hash and no secrets in front-end code. I can keep the scope tightly focused for the 60-day pilot and deliver in milestones, with clear README and deployment notes. Would you like me to prioritise the smallest pilot first, then add invites and the audit trail in a second milestone? Best regards, kartik


Hi Building a secure multi-firm client management app like Apex CRM calls for strict data security and access controls. The key challenge is multi-tenancy, ensuring data isolation between firms. I'll use PostgreSQL with row-level security to achieve this, and Argon2 for password hashing to secure accounts. js and Express app with PostgreSQL that allowed secure authentication and ensured separate data handling for multiple entities. It's great you have a front-end shell ready, making it crucial to integrate it smoothly with server-side logic. I'll also make sure the app is responsive, so it syncs data effortlessly on both phone and desktop. I can definitely help bring your MVP to life, covering all required features securely. Let’s discuss my approach and how it fits your needs. Thanks, Alex


The Apex CRM pilot MVP runs on Supabase in Sydney, with every row tagged by firm_id and Postgres row-level security blocking cross-firm reads. 490 AUD covers login with bcrypt hashing, firm sign-up making the first user Admin, clients with all listed fields and search, and dated, authored notes. First milestone, 98 AUD: a live HTTPS URL where a new firm signs up as Admin and a second firm cannot see the first. The remaining 392 AUD covers clients and notes. Invites and the audit trail follow as a next-stage milestone after you accept this checkpoint. Code goes to your repository with a README and the separation note. Hosting stays in your name, with daily backups on Supabase Pro (about 25 USD monthly). Two revision rounds included. I will sign your NDA before receiving the shell files. Price: 490 AUD fixed · Timeline: 8 working days from access/brief Konrad


Hi, I’ll deliver a secure multi‑firm CRM MVP using NestJS+Prisma on an Australian region, with Argon2 passwords and per‑firm schema partitioning. I’ll expose a simple audit API, sync via WebSocket, and provide a test URL. Let’s discuss milestones—first login, clients, then audit.
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗