Deep Dive · 2024

Construction Management Suite

An ERP for construction teams that actually fits the work

ROLELead Frontend Engineer
DURATION10 months
TEAM2 designers · 3 frontend · 4 backend
TIMELINE2024
ReactTypeScriptRedux ToolkitTailwind

Challenge & Limitations

The operational hurdles, data boundaries, and strict service Level agreements of the system.

The Problem Statement

Construction teams were running warehouse, purchase orders, and expense tracking through three disconnected vendor tools. Numbers never reconciled, approvals stalled in email, and the office was perpetually chasing the field. The brief was an integrated ERP suite that the office and the site could both use without flinching.

Rigid Constraints

  • ·Six interlocking modules — warehouse, POs, expenses, vendors, projects, reporting
  • ·Field-side usage on tablets in patchy network conditions
  • ·Approval flows with multiple sign-off tiers
  • ·An incumbent set of vendor tools the team had used for years

Design & Engineering Decisions

The tactical solutions mapping backend systems, developer experience, and interface layout.

Architecture

  • →Built a modular frontend architecture with clear ownership boundaries — each module is independently deployable and testable
  • →Centralized form, table, and approval primitives so all six modules speak the same visual and interaction language
  • →Adopted optimistic updates with retry-and-reconcile for the field-side flows, so spotty connectivity never blocked work

UX & Interface

  • →Designed a single global navigation surface that scales to many modules without becoming a wall of icons
  • →Used dense, scannable tables — these are users who live in data, not dashboards
  • →Made approvals feel like a conversation with explicit context, not a button on a row

Performance

  • →Module-level code splitting keeps the initial bundle under 180KB gzipped
  • →Tablet-optimized layouts with touch targets sized for gloved hands
  • →Background sync for field-side writes with clear, calm UX when reconciliation conflicts happen
Deliverables

The Outcome & Business Impact

The suite replaced three vendor tools across the rollout. Reconciliation work that used to take days at month-end now happens automatically. The field team adopted the tablet experience faster than anyone in the office expected.

3Vendor tools replaced
−80%Month-end reconciliation
6Modules shipped
Navigation

Interested in exploring other technical projects and DevOps systems?