
CRM System build
- or -
Post a project like this- Posted:
- Proposals: 77
- Remote
- #4476216
- Open for Proposals





Description
Dan M.
0% (0)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-

To make sure the AI generated reports truly save lawyers’ time, would it make sense to define a standard hierarchy of claim data fields now, so the database structure, prefilling logic, and reporting templates are fully aligned from day one?
-

Dan, thanks for the details. To scope this properly, could you confirm:
1. For Phase 1, which 3–5 items are the priority: Laravel models + pre-populated forms, database libraries, dashboard reporting, document storage, contact tools (or other)?
2. For the AI piece, what are the inputs you want it to read (uploaded documents/PDFs, form data in the CRM, emails, etc.) and what report outputs do you expect first? -

Before I begin, could you share how your current CRM database is structured, specifically how claims, clients, and documents are related? This will help me design the models and database libraries so reporting, document storage, and future AI-based data extraction work efficiently without needing major restructuring later.
-

Hi Dan, Thanks for your job posting and I have some questions:
What is the current database architecture (schema design, relationships, indexing strategy), and are there performance bottlenecks we need to refactor before building the new models and reporting layer?
How do you envision the AI integration working real-time processing on form submission, batch analysis via queued jobs, or document parsing using OCR/LLMs and do you have preferred AI providers (e.g., OpenAI, local models, Azure AI)?
What are the compliance and security requirements (data encryption, audit logs, role-based permissions, GDPR/PII handling), especially considering this CRM will process sensitive legal claim data?
Best.