ShippedReal EstateConstructionProject Management
// build study

GroundUp

A construction project-management command centre for general contractors that keeps schedule, RFIs, budget and the field log in one place — and maps the critical-path recovery the moment a job slips.

Client:General contractor (NDA)
Duration8 weeks
ScopeMVP product design and front-end build of the Project Command board and single-project file, backed by a schedule engine and a critical-path recovery model.

// The Project Command board — a phase gantt over portfolio KPIs, a worst-first jobs table, and RFI aging plus budget-by-division on the rail.

// the numbers

Figures from the engagement, shared under NDA.

We publish them unchanged and can’t break them down any further here. The reference build you can open runs entirely on sample data.

8Active projects
6/8On schedule
-1.4%Budget variance
23Open RFIs
01In brief

If you read one part of this page, read these 4 lines.

  • Puts schedule, RFIs, and budget for a GC's whole book in one command centre
  • Turns an 11-day slip into a sequenced, quantified critical-path recovery plan
  • Every lost day decomposes into a named cause, not a vague 'we're running late'
  • Keeps RFIs and submittals from aging out silently and blocking field work
02Overview

What it does — and which part of it we built.

GroundUp gives a general contractor one command centre for a whole portfolio of active jobs.

It tracks the schedule and milestones on live gantts, keeps every RFI and submittal from aging out silently, watches committed cost against the GMP budget by division, and captures the daily field log — then, the moment the critical path slips, it decomposes exactly where the days went and sequences a recovery plan. BuildspaceLabs designed and built the MVP front end — a Project Command board for portfolio triage and a per-project file for the PM running the recovery — turning a schedule engine and a stream of field signals into a workflow a project manager can act on in minutes.

03The screens

Every screen here is from the reference build, not the client’s system.

The captions say what you are looking at. Every name and record on them is sample data.

04Outcomes

What the engagement left the client with.

  • Delivered a production-quality MVP of the Project Command board and project file in an 8-week engagement
  • Consolidated schedule, RFIs, submittals, budget, and the daily field log into a single PM workflow
  • Gave the GC a real-time view of schedule and budget exposure across 8 active jobs
  • Established a reusable blueprint design system (gantts, schedule pills, RFI aging, recovery cards) for the product's next surfaces
05How it is built

The stack was picked per constraint, not per house habit.

7 technologies across 3 layers — the shape of the stack follows the problem.

Frontend & Mobile
Next.jsReactTypeScriptTailwind CSS
Data & Infrastructure
PostgreSQLMapbox GL
Backend & APIs
Python · FastAPI
Every feature in the build (6)
  • Project Command board with active-project KPIs, a phase gantt, and a worst-first jobs table
  • Schedule and milestone gantts with % complete, a live today line, and baseline-vs-forecast
  • RFI and submittal tracking by age, ball-in-court, and schedule impact
  • Budget-vs-actual by CSI division with committed cost flagged against the GMP budget
  • Critical-path recovery plans with sequenced crew moves, resequencing, and re-baselines
  • Daily field log with weather, crew counts, deliveries, and progress photos tied to the schedule
// see for yourself

Don’t take our word for it — it is running in the frame below.

This is the same page the provenance block links to: our reference build for GroundUp, with its own look, copy and motion. Scroll inside it, or open it full-screen.

// more from the lab

A team that ships across the board.

36products in production
8industries served
68+technologies in play

Closest to GroundUp

// next

Building something in this space?

A 30-minute call is enough for us to understand your situation and tell you whether we're the right team. Usable version in the first two weeks if we are.