Full-Stack Developer — Build & Deploy Integrated CRM (Fixed Price)

# ABOUT THE PROJECT We are a UAE-based legal and corporate services group operating across five departments: * Business Development * Debt Collection * Accounts * Litigation * Corporate Legal Services We are developing one integrated CRM that gives each department its own operational workspace while keeping clients, matters, payments, tasks and cross-department handoffs connected and traceable. Although this Upwork post is technically listed as “Hourly” because the job type cannot be changed after publication, we are not seeking an open-ended hourly engagement for the core production build. Shortlisted candidates will be asked to provide a fixed-price milestone proposal and fixed total for the core implementation after reviewing the reference CRM and requirements. Post-go-live support may be hourly or retainer-based. We have already built a substantial **interactive functional reference CRM** using React / Next.js / TypeScript. The current build demonstrates the intended: * screens and navigation; * dashboards; * client/debtor/matter workspaces; * workflow stages; * task centres; * cross-department handoffs; * selected automation/trigger logic; * realistic demo data; * client and matter reference structure. However, this is **not a production-ready application and should not simply be taken over and expanded as-is**. We need an experienced developer or small team to review what exists, validate the business logic with us, determine what should be retained vs. rebuilt, and engineer the proper production system. --- # CORE CHALLENGE The main challenge is maintaining reliable data and workflow relationships across five departments with very different operating processes. Examples: * Business signs a client and hands work to Accounts / Legal. * Accounts confirms payment and allocates the engagement. * Collection may escalate a debtor to Litigation. * Litigation may request Corporate support such as a POA or Legal Notice. * Existing clients may return later for new services while retaining the same permanent client identity. The production CRM must prevent: * duplicate clients; * disconnected matters; * broken parent references; * duplicate automation; * lost departmental handoffs; * inconsistent statuses. Management must also have a consolidated view of the client relationship across the group. --- # CURRENT BUILD — IMPORTANT CONTEXT The existing CRM is best treated as a **functional and visual reference for the intended system**. It contains substantial working UI and workflow concepts across: * Business Development; * Debt Collection; * Litigation; * Corporate Legal Services; * Accounts. It also contains preliminary database/schema work. However, the production system still requires: * proper server-side database and persistence; * production authentication; * server-enforced role-based permissions; * proper audit trail; * production automation architecture; * document/storage strategy; * workflow validation; * codebase restructuring/refactoring where required; * deployment architecture; * backup and disaster recovery. Some current logic is demo-oriented and some workflows may still require clarification or alignment before production implementation. We therefore **do not expect the developer to blindly reuse the existing codebase**. --- # WHAT WE NEED ## 1. Discovery / Technical Assessment Review the existing reference CRM and identify: * what should be retained; * what should be rebuilt; * missing or conflicting workflow logic; * duplicated logic; * production architecture; * final data model; * permission model; * automation design; * deployment approach. We expect constructive technical challenge, not simple replication. ## 2. Production Architecture Build a proper production system including: * backend/database; * authentication; * server-side RBAC; * durable data storage; * APIs/service layer; * audit trail; * task/workflow architecture; * secure document handling; * validation and error handling; * logging; * backup/recovery. ## 3. Department Modules Production implementation and validation of: * Business CRM * Collection CRM * Accounts CRM * Litigation CRM * Corporate Legal CRM ## 4. Cross-Department Workflow The final system must correctly support: * client onboarding; * department allocation; * payment confirmation; * Collection → Litigation escalation; * Litigation → Corporate support; * task generation; * approvals; * document handoffs; * status changes; * permanent parent/child record traceability. ## 5. UI / UX The existing CRM provides the intended operational direction. The production version should retain useful workflow concepts while improving: * consistency; * reusable components; * 360/client/matter workspaces; * tables; * search/filtering; * dashboards; * performance; * maintainability. --- # HOSTING / INFRASTRUCTURE Our environment includes a true **on-premises Windows Server** on physical/local-network infrastructure controlled by us. Staff may access the CRM through: * internal network; and/or * our existing VPN. We are not prescribing the final stack. Your proposal must explain: * whether you recommend retaining React / Next.js; * recommended backend; * recommended database; * what runs on Windows; * whether you recommend any Linux component; * IIS/reverse proxy or Windows Service approach; * database and application backup; * disaster recovery; * staging and production deployment; * monitoring/logging. We particularly value candidates with real experience deploying production web applications on **on-premises Windows Server**. --- # CRITICAL REQUIREMENTS * Permanent client/matter hierarchy and traceability. * No duplicate client IDs for the same signed client. * Server-side role-based access control. * Full audit history for important actions. * Durable backed-up storage. * Clean, non-duplicated automation. * Secure handling of legal and financial data. * No silent data loss. * Staging/UAT deployment before production go-live. * Maintainable production codebase. --- # COMMERCIAL STRUCTURE We require a **fixed-price production build**. A short, separately priced discovery/technical assessment phase is acceptable and may be preferred. Please provide: * discovery price; * fixed-price development phases; * total estimated project price; * timeline; * milestone structure; * assumptions and exclusions. The core production build will not be awarded on an open-ended hourly basis. --- # WHAT TO INCLUDE IN YOUR PROPOSAL Please address: 1. **Your understanding** In 2–3 sentences, explain what you believe the main challenge is. 2. **Existing reference build** Explain how you would decide what to retain vs. rebuild. 3. **Technical approach** Recommended frontend, backend, database, authentication, RBAC, automation and audit architecture. 4. **Windows Server experience** Have you personally deployed production Node.js / Next.js or comparable applications on on-premises Windows Server? Briefly describe how. 5. **Relevant projects** CRM, legal-tech, debt collection, case management or multi-department workflow systems. 6. **Fixed-price phases** Proposed milestones, price and timeline. 7. **Deployment** Confirm staging/UAT and production deployment are included. 8. **Ongoing support** Availability and commercial model after go-live. Shortlisted candidates will receive access to the CRM reference build and additional functional documentation privately before final scope/quotation. We are looking for a developer or small team who can turn a detailed functional reference into a **properly engineered production CRM**, not simply continue adding features to demo code.