Full-Stack Developer Required to Build Custom, Secure CRM System

Hi Tony,

A few things I’d want to clarify before locking a proper fixed quote:

1. Will associates / related contacts just hold profile + notes data, or do they need their own timeline / attachments / activity history too?

2. Can a property / asset case link to more than one person/case, or is it always one-to-one back to a core individual?

3. Will the CRM need document uploads / evidence storage / file management as part of the case workflow?

4. How many user roles do you expect, and do permissions vary a lot between them?

5. Do you already have a preferred stack in mind, or are you genuinely open on Laravel / Node / React etc.?

In addition to full custom CRM development, we can also offer different implementation / licensing approaches depending on what makes the most sense for your business operationally and commercially.

Depending on your preference, that can range from:

-ready-made CRM foundations for faster deployment
-semi-custom builds where core CRM structure already exists and we tailor the workflows around your use case
-fully custom ownership-based CRM development where the system is built specifically around your internal process and you have full control for future expansion
-ongoing support / optimization / scaling after the first release

So if helpful, we can also talk through whether this is best approached as a ground-up bespoke build or whether there’s a more practical hybrid route depending on your workflow, team size, and long-term plans.

Looking forward to your response.

Best,
VConn Pvt Ltd.

Will the CRM require granular role-based permissions (e.g., admin, researcher, manager, read-only users) with audit logs showing who viewed or modified sensitive records, or is access currently intended to be the same for all authenticated users?

Can you please answer me about this first then I will placed a bid on your project.

Given the sensitive nature of the data, do you have any specific compliance, hosting, or data residency requirements (e.g., GDPR, ISO 27001, UK/EU data storage, encrypted backups, audit logging, user activity tracking)?

How would you like case relationships to function when an individual is connected to multiple assets/properties and vice versa? Should the CRM support many-to-many relationships, relationship mapping, and visual link tracking between individuals, associates, and assets?

What reporting and workflow management capabilities do you envision for the platform? For example, would users need custom dashboards, advanced search and filtering, case status workflows, task assignments, reminders, notifications, and exportable reports?

~ How many user roles and permission levels do you anticipate (e.g., Researchers, Analysts, Administrators), and what actions should each role be allowed to perform?
~ Will the CRM require document management features such as file uploads, version history, audit trails, and secure document sharing within cases?
~ Do you expect integrations with external services (e.g., email platforms, property databases, identity verification tools, or reporting systems) either in the initial release or future phases?

Hello Tony,
1) Custom relationship types: should the relationship labels between an individual and their associates be a fixed list you define, or fully free-form per case?
2) Search and filtering: how do you expect to find records day to day, by individual, by asset, by relationship, or full-text across notes? This affects how we index the data.

A few questions:
1. Will documents, images, or evidence files need to be uploaded and linked to cases?
2. Do you require multiple user roles with different permissions and access levels?
3. Would reporting/export functionality (PDF, Excel, CSV) be part of the initial release?

For Individual Cases and Asset/Property Cases, would you expect the CRM to support many-to-many relationships (for example, multiple individuals connected to multiple assets/properties), or is the relationship structure generally one primary individual connected to related associates and assets?

Understanding this early helps ensure the database architecture is designed correctly from the outset.

A few questions:

1. Will there be multiple staff roles accessing the CRM?
2. Do you require document uploads and storage from day one?
3. Is there a need for email integration or communication tracking?
4. Are there any compliance requirements (GDPR, ISO, etc.) that must be considered?
5. Do you anticipate future client-facing access, or is this strictly an internal platform?

Hi Tony,
What is the main workflow or process you currently use to manage these research cases, and which parts of that process are causing the biggest challenges today? Understanding this will help ensure the CRM is built around your actual operation rather than just a list of features.

- For Individual Cases, how extensive should relationship mapping be? Should users only link associates to a core individual, or do you also require relationship visualization, family trees, business associations, organizational connections, and multi-level relationship tracking across projects?

- What reporting and search capabilities are required within the CRM? Should users be able to perform advanced filtering, global searches, relationship searches, export reports, case summaries, audit reports, and custom dashboards for operational insights?