The reasoning should stay with the project.
A site decision can shape a project long after the meeting where it was made. We are building LinkWave so the information behind that decision is easier to find, inspect, and carry into the next stage of work.
A decision should survive the meeting where it was made.
The company thesis is practical: preserve enough context that another person can inspect the basis, understand what changed, and continue the work.
- Site basis
Property, jurisdiction, available source material, and the development question.
- Proposal
Scenario geometry, program, financial assumptions, and the option under review.
- Design evidence
Drawing revision, criterion, provided information, and the condition being evaluated.
- Decision record
Conclusion, reason, unresolved question, responsible person, and the change that should reopen it.
The problem we are working on
A project accumulates parcel information, studies, code questions, drawing revisions, and conversations. Each can be useful on its own. The difficulty comes when the next person needs to understand how they fit together: which source was used, which assumption changed, and why the team chose a particular direction.
Start where the decisions begin
LinkWave brings site feasibility and drawing compliance review into the same product. A development team can examine a property and preliminary options; a design team can inspect a plan-set finding and the evidence attached to it. Project information and conversations support the work around those reviews.
Make the result inspectable
Our product work centers on a simple expectation: people should be able to look behind a result. A reference, a provided value, or a location on a drawing gives a reviewer something concrete to investigate. That is more useful than asking them to accept an unexplained answer.
Build alongside the people doing the work
Architects and developers are central to the product. We want to understand the actual questions they face, the material they have available, and how an answer moves through their team. A walkthrough is an opportunity to examine that fit on a real project.