Atomic CRM Setup & Customization — Broker, Client, Lender and Admin Portals

Hi Jay, Your React and Supabase background appears relevant to a CRM project we are planning for GoKapital, a U.S. commercial financing company. We are evaluating Atomic CRM as the foundation and need initial installation, hosting configuration, and customization for four separate user roles: brokers, clients, lenders, and administrators. Please review the scope below and provide a phased estimate, your earliest availability, and examples of similar projects involving Supabase authentication and record-level permissions. We need a presentation-ready prototype within two days. Please distinguish what you can realistically demonstrate in that timeframe from the work required for a production-ready system. We also want the project prepared so we can continue development with an AI coding agent after your initial implementation. GoKapital is seeking a developer to evaluate, install, and customize Atomic CRM for managing brokers, clients, lenders, and financing applications. Platform under consideration: https://marmelab.com/atomic-crm/ https://github.com/marmelab/atomic-crm Please review the platform before quoting. We need an assessment of which requirements Atomic CRM supports and which require custom development. 1. INDIVIDUAL ACCOUNTS AND FOUR USER ROLES Each person must sign in with their own email and password. • Broker: manage their own clients, submit financing applications, upload documents, and track authorized application updates. • Client: maintain their profile, complete applications, upload requested documents, and view authorized updates. • Lender: access only applications explicitly assigned to their institution, request information, and submit offers or decisions. • Admin: manage users, approve access, assign applications, control document sharing, review offers, and oversee the entire system. Multiple individual users may belong to the same lender institution. Access restrictions must be enforced in the database and file storage, not only by hiding interface elements. Lenders must not see competing lenders’ offers. Internal notes and commission information must have restricted access. 2. CORE DATA AND WORKFLOW The system must distinguish between: • Users and their roles. • Broker profiles and broker companies. • Clients and applicant businesses. • Financing applications. • Individual submissions of an application to different lenders. • Each lender’s response and offer. • Documents, notes, tasks, and activity history. One broker may originate multiple clients and applications. One application may be submitted to several lenders, with separate responses and statuses. Please propose the appropriate data model and identify any limitations of Atomic CRM for this workflow. 3. INSTALLATION AND HOSTING Please quote for: • Installing a stable version of Atomic CRM. • Configuring Supabase and suitable frontend hosting, such as Vercel. • Connecting a GoKapital subdomain. • Configuring authentication emails, invitations, and password recovery. • Creating separate development/test and production environments. • Configuring protected document storage. • Establishing backup and recovery procedures for both database records and uploaded files. All service accounts, source code, repositories, and data must remain under GoKapital’s ownership. 4. INITIAL DATA IMPORT We need CSV templates and an initial import process for broker, client, and lender records. Please include field mapping, duplicate handling, validation, and a small trial import before importing the full dataset. Profile import and creation of login accounts should be handled as separate processes where appropriate. 5. CONTINUED DEVELOPMENT WITH AI After the initial implementation, we want to continue development with an AI coding agent. Please include: • A company-owned GitHub repository. • A documented development environment usable from Windows. • Setup instructions for an appropriate AI coding workflow. • Instructions for testing, publishing, and reverting changes. • Database migrations and documentation of customizations. • A handover session explaining the system and development process. Please clarify whether you have experience with Atomic CRM’s Agent Harness or CRM Builder. 6. TIMELINE AND QUOTATION We need a presentation-ready prototype within two days, using fictional data. Please provide separate pricing and timelines for: A. Technical assessment and initial installation. B. Presentation prototype showing the four roles. C. Production implementation, permissions, and document security. D. Data import, documentation, and training. E. Optional ongoing maintenance. Clearly distinguish simulated prototype features from working authentication, enforced permissions, and persistent data. For each phase, specify deliverables, assumptions, exclusions, estimated hours, hourly rate or fixed price, third-party costs, and earliest start date. 7. EXPERIENCE AND ACCEPTANCE Please answer: • Have you installed or customized Atomic CRM before? • Can you show a comparable multi-role application? • Have you implemented Supabase Row Level Security and private file access? • How will you test that users cannot access another user’s records or documents? • Can you support separate lender submissions and offers for one financing application? • What can you realistically deliver within two days? • What post-delivery bug-fix support is included? We will evaluate the implementation through a demonstration of the complete workflow and cross-account permission tests.