StruktLab: AEC Delivery Platform

StruktLab is a construction delivery platform built for the workflows that matter on real projects: RFIs, submittals, drawings, daily logs, punch lists, change orders, and project health summaries — with stronger UX and pricing than legacy incumbents.

At a glance

• Problem: AEC teams juggle Procore-scale complexity with tools that feel bolted together. Project managers need one place to see what's blocked, what's due, and what's at risk.
• Approach: projects as the central aggregate — most modules attach via project_id with centralized authorization, Supabase RLS, and a widget-based dashboard.
• Stack: Next.js 16 · React 19 · TypeScript · Supabase · Tailwind · TanStack Query.
• Status: Live at www.struktlab.com — active development toward feature parity on core delivery workflows.

What I'm building

The platform covers the delivery surface area construction firms actually use daily:

• RFIs and submittals with approval chains and audit trails
• Drawings and document control with version tracking
• Daily logs and site reports with geolocation snapshots
• Punch lists and change orders tied to budget and schedule
• Project health summaries powered by structured activity data and LLM-assisted rollups

Authorization is route-level and project-scoped — service-role access never bypasses permission checks. Every API input is Zod-validated; schema changes flow through Supabase migrations with generated types.

What I'd do differently

Ship narrower vertical slices earlier. The aggregate model is right long-term, but user feedback loops are faster when a single workflow (e.g. RFIs end-to-end) is polished before expanding surface area.

Observability from day one. Structured logging and error tracking (Sentry) should ship alongside the first production route, not after the first incident.

Stack & links

• Next.js 16 (App Router) · React 19 · TypeScript · Supabase
• Live product: www.struktlab.com

Related portfolio work: LeadSignal, DocSignal, SignalVision.