Design, traced to execution.

In Revit, a material is generic content.
In reality, it's a decision with a history.

Who chose it. What it costs. Which sample sits in which office. Whether the spec writer signed off, and how it changed between schematic design and construction documents. BIM tools hold geometry — the decisions lived in fractured spreadsheets, email threads, and memory that left with every departure. The final decision lived in a spreadsheet; the institutional knowledge stayed buried deep in a project folder; every new project reinvented the wheel. Across seven offices and two spec-standard systems, there was no shared record of what had been decided, by whom, and why.

Zero to one, self-taught, shipped inside one of the world's most demanding design firms.

I built Lineage end to end while practicing full-time — taught myself the foundations of computer science, shipped the MVP, then earned firm sponsorship for real deployment. It's BIG-sponsored but personally owned. Every feature maps onto how architecture teams actually work: CSI Divisions because spec writers think in them, scratch pads because designers explore before they commit, firm attribution because consultants touch the data too.

Every week I sit down with the people who use it — office specialists across every trade, from BIM and spec to sustainability to project architects — to map the most-wanted features, the wish list, the real pain points, the right workflow. — the weekly loop

Built for a firm's institutional memory and proprietary knowledge — so it had to earn enterprise trust first.

SSO against the firm's identity provider. A five-tier permission model gating data by role and project scope — an outside consultant on one project never sees another's costs. And the long-term architecture: each firm gets its own sovereign, walled instance of its specification history. Firms don't share a database; they own their decisions. That choice, made at pilot stage, is what makes the multi-firm vision credible.

Live in production, across continents.

Architects, project leads, spec writers, and external consultants use Lineage in their real production workflow — with the platform adapting to each market's specification standards. A weekly feedback loop across roles and regions drives the roadmap, and teams increasingly treat Lineage, not scattered spreadsheets, as the source of truth for what's been decided — actively shaping the projects redrawing your city's skyline.