Technical Partner — Construction Intelligence Platform

I'm a construction executive with 28 years in the industry and $4B of high-rise work delivered. I'm building the owner-side intelligence platform I spent my career wishing existed: it watches a project's RFIs, change orders, submittals, schedules and pay applications, and tells the building owner what's about to cost them money, with the evidence attached.

The product work is done — complete database schema, written build specification, feature specs, wireframes, dashboard logic documents, and realistic sample project data. First prospects are identified. What's missing is the engineer.

The seat

You own the platform, integrations, and technical client setup. I own product direction, construction domain logic, sales, and client relationships.

Terms are pre-structured, not a negotiation from zero: milestone cash on accepted working deliverables, per-client setup fees as clients come on, equity up to a defined ceiling with 4-year vesting and a 1-year cliff, deliverable-based grant, buyback provision, day-one IP assignment. All platform IP is company-owned. Everything is papered by my attorney.

First engagement

A multi-project analytics dashboard built against the existing specifications: portfolio overview, per-project alert cards with supporting evidence trails, aging and status logic across several document types, document cross-referencing views, and schedule and cost views.

The alert engine is a deterministic rules engine over normalized data — never a language model. It has to be explainable and testable, because owners act on these numbers in disputes with their general contractor.

Stack: Next.js (App Router), Supabase/Postgres, Tailwind, Vercel. Data loads from structured sample files; no third-party integrations in this phase.

This first build runs on sample data. The phases after it are where the platform earns its name: a live API integration with whichever construction management platform the owner runs — Procore, Autodesk Construction Cloud, and Oracle Aconex among them — with the integration layer built so additional platforms follow without a rewrite; an ingestion pipeline for the files the general contractor delivers outside that system, in whatever format they arrive; and a retrieval layer that answers plain-language questions about a single project and cites the document and page each answer came from, returning nothing when there is nothing verified to cite. You should have built production API integrations, file-ingestion pipelines, and document retrieval before. That work is the harder half, and it is why this is a seat and not a project.

You

Senior full-stack, with two or more production Next.js + Postgres applications you can walk me through live. Strong with Postgres specifically — views, derived fields, and date logic are the heart of this build. Clear written English. You want a technical seat in a company, not a contract. You can keep your day job through the first phase.

You are comfortable building software whose output has to be defensible. Owners take these findings into conversations with their general contractor, so every number traces back to a rule and a source document. No confidence scores, no generated conclusions.

One thing to be direct about: this is a defined seat with defined terms. If your interest is renegotiating the instrument rather than the numbers inside it, we're not a fit.

NDA before any specification document is shared. Everything through my attorney.