Landsight

Landscape design firms check a developer's drawing package by hand before they can price it, and it takes about two weeks. I've seen it done, and the idea came out of conversations with property developers. Try it in a browser, no install: https://landsight.co/try You drop the folder in as it came: CAD sheets, scans, Excel bills, backups. Landsight gives every file a verdict, counts and measures what's drawn, and checks the bill against the drawings, the firm's price list and the local building code. Findings come sorted the way developers work: send the nonsense back, flag the rest. Every finding opens on the drawing it came from, nothing counts until a person confirms it, and it drafts the change request and the reply to the developer. Geometry goes first. Muse Spark 1.3 reads only what geometry can't settle, in a fixed JSON schema, and writes the prompts SAM 3.1 uses to measure coloured plans. Drawings are confidential, so the whole review can also run on Muse Spark Open, Meta's open weights, on Baseten or a deployment the firm controls, and Muse Wonder learns each firm's habits from what it confirms. Real drawings are under NDA, so I built synthetic packages with planted errors and put the answer keys in the repo: 28 of 30 found, 2 flagged for a person, none missed. What's next: I want to turn Landsight into a company. A prize would pay for setting it up, pilots with landscape firms on private deployments, and the product work, and I'd like to talk with Meta about private deployment. Everything in the repo was built during the hackathon, Nov 1–4.