Role
Full-stack engineer
Case Study
Back to work
Internal Tool
SitePulse
A role-aware construction field-operations platform for project setup, daily logs, punch workflows, and commercial change-order review.
ExpressDrizzle ORMPostgreSQLBetter AuthRefineReactTailwind CSS
Case study framing
This page is structured as a product and delivery narrative: what the system needed to do, what constraints shaped it, and how the implementation held up.
Role
Full-stack engineer
Published
Jun 2026
Audience
Construction operations teams and project stakeholders
Outcome
Built unified operations system for projects, field, and commercial workflows with role-based access.
Reading mode
Read this case study through solution, architecture, process, outcomes, walkthrough.
Context
What the product needed to do
A role-aware construction field-operations platform for project setup, daily logs, punch workflows, and commercial change-order review.
Built unified operations system for projects, field, and commercial workflows with role-based access.
Project dossier
A compact read on scope, role, and who the system was designed for.
Work type
Internal Tool
Role
Full-stack engineer
Audience
Construction operations teams and project stakeholders
Published
Jun 2026
Outcome snapshot
Visibility model
4 role-aware surfaces
Workflow span
Field to office
Commercial control
Change-order review
Problem
Construction coordination often breaks down across spreadsheets, chat, and disconnected reporting tools, especially when internal staff and clients need different visibility.
Solution
I structured the product around project setup, daily logs, punch resolution, and change-order review so each role sees the right operational surface without exposing internal workflows unnecessarily.
The platform balances internal coordination with curated client visibility, which keeps accountability high without turning the product into a noisy all-access portal.
Architecture
The backend uses service-layer business rules and scoped authorization checks, while the frontend adapts those flows into role-aware dashboards and project detail views.
That boundary is important because operational systems often fail when internal logic and client visibility rules are allowed to drift out of sync.
Process
The key product decision was to treat the app as an internal operations platform with curated client visibility, not as a flat all-users portal.
That choice kept the MVP more disciplined: it prioritized the workflows that actually unblock project coordination instead of expanding into ERP-style sprawl.
Outcomes
Role-specific dashboards with clearer ownership across project coordination
Daily log workflow that preserves field-to-office continuity
Change-order lifecycle support with commercial review in mind
Client-safe project visibility without exposing internal-only coordination views
Product walkthrough
Walkthrough
Dashboard
Walkthrough
Projects
Walkthrough
Daily Logs
Related Work
See related case studies
Additional work with adjacent product, workflow, or technical characteristics.
MedHub
A healthcare operations platform rebuilt around bookings, departments, services, and audit-safe workflow rules instead of generic admin CRUD.
Re-architected a generic stack into a clinic system with role-based access, safer bookings, and admin visibility.
Veloce Auto Spa
A premium mobile auto detailing booking platform pairing a polished marketing funnel with booking, payment, and operational admin tooling.
Designed a service platform where conversion, scheduling, payments, and operations reinforce each other
Freelance OS
A realtime operations dashboard for solo service businesses that combines lead tracking, tasks, bookings, billing boundaries, and plan-aware limits.
Mapped a solo service business workflow into one product instead of scattered tools.