Cloud-Based ERP Construction Management Platform
Publicada el 2026-07-16
Descripción de la oferta
Project Overview We are seeking a senior full-stack developer or development team to build Phase 1 (MVP) of a cloud-based Construction Management Platform. This MVP will function as a single-tenant deployment for a primary General Contractor to validate core contracting, compliance, and financial workflows. The application must be built with strict architectural constraints to support a transition to an isolated, multi-tenant (database-per-tenant) architecture in future phases. 1. Scope Overview Building Phase 1 (MVP) of a cloud-based Construction Management Platform. Scope Restriction Notice: Phase 1 is strictly focused on Back-Office Commercial Construction Operations (Contract Management, CA Public Works Compliance, Insurance tracking, Procurement, Financial Ledgers/Billing) and the external Client/Vendor collaboration portals tied to these operations. The platform must be a responsive web application. Do not include estimations for field project management modules (RFIs, Submittals, Drawings). Do not include estimations for HR, Employee Directories, or Timesheet/Timecard workflows. Do not include offline-first mobile sync architecture. If Phase 1 is a success, these modules will be developed in future phases. 2. Required Technology Stack Your proposal must explicitly utilize the following stack. Substitutions will only be considered with a detailed technical justification. Frontend: Next.js (App Router), TypeScript, Tailwind CSS, shadcn/ui. Backend & APIs: NestJS, TypeScript (Designed as a headless API layer to support future integrations). Database & ORM: PostgreSQL or Supabase, Drizzle ORM. DevOps & Storage: Dockerized containers, AWS S3 (with pre-signed URLs for secure document access), client owned Github or Gitlab development environments. Hosting and deployment Architecture: The client requesting this RFP owns or leases the AWS or Google Cloud services (no microservices, or when applicable if an alternative is not possible), VPS, or dedicated servers or server clusters, HA, load balancing, disaster recovery, backup. 3. Core MVP Modules Bids must include the delivery of the following modules, designed to completely digitize our back-office workflows and external collaboration: Module A: Granular Permissions & Role-Based Access Control (RBAC) User Roles: The system must support highly granular, matrix-style permissions. Administrators must be able to create custom roles with specific "None / View / Edit / Admin" toggles for every single module in the system. Project-Level vs. Company-Level: Permissions must be assignable at the global level (e.g., a Corporate Executive) or restricted to the project level (e.g., a Project Manager who can only see financial data for assigned jobs). Focus on the single tenant platform with the option to implement multi-tenancy in a separate Phase. Multi-Tenant Data Isolation: Strict database-level security to ensure external Client and Vendor users can only access data explicitly tied to their assigned contracts. Module B: External Collaboration Portals Vendor / Subcontractor Portal: A secure login area where subcontractors can: Upload and manage their own compliance documents (W9s, COIs, CSLB License details). Upload required Certified Payroll reports for CA Public Works projects. View their signed subcontractor project agreements, SPAs, scope of work (SOW), schedule of values (SOV) Change Orders, time and materials (T&M). Submit invoices directly against their approved Schedule of Values (SOV). Track the status of their payments (e.g., view check numbers, release dates, and held retainage). Client / Owner Portal: A secure login area where project owners can view AIA invoices, track project financials, review Owner Change Orders (OCOs), and monitor overall contract values. Module C: Subcontractor & CA Public Works Compliance Expiration Alerting: Dashboard alerts for the GC's internal team regarding expiring Vendor Licenses and Certificates of Insurance. Certified Payroll Verification: Dedicated tracking for CA Public Works projects, enforcing logic that blocks invoice approval if a subcontractor's Certified Payroll reports are missing or unverified. Automated Contracting: Generate Master Subcontract Agreements (MSA) and Project-Specific Agreements (SPA), integrated with an e-signature API (DocuSign/PandaDoc). Module D: Procurement & Accounts Payable (Subcontractor Payouts) Procurement Engine: Generation and tracking of Vendor Purchase Orders (POs), Vendor Change Orders (VCOs), and Vendor Time & Material (T&M) tags. Custom Retainage & Batch Checks: The system must calculate and track custom retainage withholdings (e.g., 5%, 10%) per vendor invoice, maintaining a running balance of held retainage per project until final release. It must also support Batch Payments, allowing a single outgoing Check Number to be applied across multiple vendor invoices. Flexible SOV & Cost Code Architecture: The database schema for contracts and invoices must support line-item granularity linked to standard CSI Cost Codes (for detailed project tracking), while remaining flexible enough to accept a single "bulk" line item for simpler, lump-sum contracts. Module E: Client Contracts & Accounts Receivable (Client Billing) Owner Contract Management: Support for multiple prime contract types, including Hard Bids, Job Order Contracting (JOC), and General Contractor Time & Materials (T&M) agreements. Tracking of Client POs and Owner Change Orders (OCOs). AIA Invoicing & SOVs: Automate the math and PDF generation for AIA G702 (Application and Certificate for Payment) and AIA G703 (Continuation Sheet) based on the project's overall SOV and incoming client retainage. Automated Aging Reports: Dynamic generation of AR/AP outstanding balances categorized into Current, 1-29 Days, 30-59 Days, 60-89 Days, and 90+ Days buckets. CSV Exports: A custom export utility that formats approved AR/AP data into a CSV structure. Module F: Lien Waiver Tracking Waiver Matrix: Automated tracking of payments against Conditional Progress Payments (CPP), Unconditional Progress Payments (UCPP), Conditional Final (CFP), and Unconditional Final (UCFP) waivers. 4. Proposal Submission Requirements To be considered, your proposal must include: Technical Execution Plan: Detail how you will structure the NestJS API layer and PostgreSQL database to handle AIA G702/G703 SOV math, batch check processing, certified payroll gates, AP/AR retainage tracking, and specifically outline your database schema design for handling matrix style permissions and external user portals. Milestone-Based Project Plan: Provide a timeline broken down into agile milestones. Data Migration Strategy: Explain your approach for providing CSV upload utilities so our team can seamlessly migrate historical vendor, check logs, and invoice data from our current Google Sheets into the new PostgreSQL database. IP Ownership & Warranty: Confirm all source code and infrastructure will be 100% owned by our company, and outline your post-launch bug-fix warranty period.
Skills
- Tailwind CSS
- shadcn/ui
- PostgreSQL
- Next.js
- TypeScript
- Supabase
- CSS
- JavaScript
- Drizzle
- Project Management
- Google Cloud
- Compliance
- Nóminas
- Agile
- AWS
- Recursos Humanos
- Google Sheets
- Microservicios
- Facturación
- NestJS
Fuente original: freelancer