About
Spun out to focus on one job
Sightline began as the inspection tool inside a broader construction platform. It outgrew that shell, so it now stands on its own.
Inspection reporting is still mostly a memory exercise. Someone walks a site, takes a few photos, and reconstructs the visit hours later at a desk. Details fade, photos lose their context, and the report ends up thinner than the walk it came from.
Sightline closes that gap by recording the walk as it happens, keeping the words and the frames aligned, and drafting the report while the site is still fresh. The inspector reviews and signs rather than reassembles.
The same engine now serves capture from equipment that never gets tired: drones on a facade, a quadruped on a night patrol, an agent running a scheduled progress check. Whoever or whatever carried the camera, the output is one consistent, defensible document.
How we build
Evidence before language
A finding exists because something was seen and said on site. If the capture does not support it, it does not go in the report.
Built for gloves and glare
The capture screen is designed for a phone held in one hand, outdoors, with dust on the lens. Dense, high contrast, and nothing decorative in the way.
Hardware should not decide the workflow
The camera changes constantly on a job site. The report should not. Every input path ends in the same document.
Machines are users too
Drones, robots, and AI agents get the same first-class ingestion path a human does, because increasingly they are the ones walking the site.