A modular ERP for project-driven teams — covering projects, packages, sheets, submittals, resource allocation, and analytics. Designed and prototyped end-to-end with Claude AI, shipped as fully interactive HTML prototypes.
This ERP was built for a firm specialising in BIM services — a complex, highly specific operation. To get it right, I followed a deliberate four-stage process: gather, systemise, generate, and refine.
Gathered every requirement directly from the stakeholders — workflows, edge cases, BIM-specific terminology — and consolidated everything into a single living markdown brief.
Built a generic, brand-aligned design system from scratch — tokens, typography, components, states — so every screen that followed would feel cohesive and on-brand.
Used the brief and the design system together to generate the full breadth of screens — projects, packages, sheets, submittals, resourcing, analytics — as interactive HTML prototypes.
Walked through each screen one by one with the team, surfaced issues, refined flows, fixed inconsistencies, and tightened the visual language until every view was production-ready.
JES ERP manages the full lifecycle of BIM projects for a firm split into two departments — Architecture and MEP — from project setup through task execution, QC, submittals and analytics. It supports two business models in parallel: Lumpsum (fixed-scope delivery with budgets) and Resourcing (skilled workers billed by hours consumed per client stakeholder).
The firm was running complex, multi-department BIM projects across spreadsheets and siloed tools — no single source of truth for packages, sheets, tasks, reviews, budgets or time. Managers couldn't see utilisation, PLs couldn't trace review time, and submittals / change orders lived outside the system entirely.
Every screen is built on one primitive — the data table in Read, Edit, or Input mode — wrapped by seven templates (List, Detail, Dashboard, Form, Modal, Wizard, Kanban). A unified status engine drives projects, tasks, sheets, packages, change orders and submittals through shared lifecycles, visible to each role through row-level security.
The production workflow flows top-down through five roles — Operations Manager → Project Manager → Package Lead → Senior Modeler → Modeler — with a sixth Admin role running system-wide configuration. Each role sees a filtered slice of the same data through a hierarchical RLS model.
Biometric check-in/out, per-package coordination time, PL review rollups, planned-vs-actual efficiency, workforce utilisation dashboards and a full submittal + change order pipeline put the entire department's delivery, budget and people metrics in one place — so OMs can run the department, PMs can run projects, and execution roles know exactly what's on their plate.
Owns one department end-to-end. Creates projects, monitors utilisation, manages resource allocation, runs submittals and change orders, reviews timesheets across all roles in the department.
Owns individual projects — runs the planning wizard, creates packages and tasks, builds teams, manages weekly resource allocation, handles client contacts and submittals, reviews delivery.
Runs a work package — allocates unassigned tasks, reviews modeling and sheet work, logs BIM coordination time, manages team check-outs, flags rework and drafts change orders.
Dual role — executes tasks personally while supervising and reviewing Modelers in their team. Handles assignment within the team, self-QC, and internal review of modeling work.
The execution layer — picks up assigned modeling and sheet tasks, runs self-QC, logs daily time via check-out, and tracks personal efficiency and rework metrics.
Superuser running both departments — adds users, configures the calendar, holidays and project settings, manages the BIM library, and serves as the CEO-level cross-department view.
Project list, detail, creation flow and the planning wizard for the OM team.
How packages, sheet groups and individual sheets are organised inside every BIM project.
The daily core of the ERP — checkout flows for every role plus task allocation and BIM coordination.
End-to-end submittal lifecycle plus change requests, descope reviews and feedback loops.
Resource allocation grid, user management and client contact directory.
System-wide configuration, calendar, audit trail and the analytics hub for leadership.