Property Scanner
Type a US address or click a roof on the map. The survey brings back the listing, value and rent estimates, the county record, tax history and the ZIP’s Census figures.
Case study · Loep
The records behind a price, on one sheet.
Loep is a research tool we built for people who aren’t professionals. Give it one US address, one stock ticker or one business for sale. It reads the public records and company filings behind it and lays them out as numbered sheets, with each figure’s source beside it. It’s research, never advice.
- Takes
- An address, a ticker or a business for sale
- Built with
- Static HTML, TypeScript, serverless functions
- Engines
- Pure modules that run in the browser
- Status
- Private preview
This page’s own structure, drawn at build from its HTML.
People read the top layer, crawlers follow the middle one and machines parse the bottom one.
21 headings · 52 links · 6 schema nodes
◆ BuildWhat it does
One tool, a sheet for each question.
Every screen in Loep is a numbered sheet, like a page in an atlas. Each one answers one kind of question and ends with a list of its sources.
Market Research
Enter one ticker. The report reads the company’s annual and quarterly filings from the SEC, builds its statements, and prints a conventional, textbook signal beside the rule that produced it.
Business Analyst
Paste the listing for a business for sale, or type its figures. A parser with fixed rules reads them, and nothing becomes an input until you accept it.
Indicators
Chart scripts a person adds to their own charts. The one available today was replicated, tested and revised in our research, and its method and its weaknesses are written out. The rest are marked as in testing.
Research and AI
An indicator our research tested, and one optional note.
The indicator
The indicator Loep offers today is a system our research replicated, tested and revised, working with AI agents. The ones still in testing go through the same process. Its sheet describes the method and leaves the settings out.
The optional note
Loep uses AI to write an optional note that explains figures its own code has computed. No figure, signal or verdict comes from a model, and every sheet is complete without the note.
One property
A scan, start to finish.
Nothing runs until asked
A click only outlines the building and drops a pin. No record is looked up until the person presses the survey button.
Resolved to one address
A typed address or a point on the map is reduced to one normalized address before any property record is requested.
Fetched together
Whatever is out of date is fetched at once, under one deadline. A part that doesn’t arrive is listed as unavailable, with the reason.
Sources on every sheet
The answer comes back as sheets. The last one lists each source and when it was read, and an answer served from cache (a stored copy from an earlier request) says so.
The price is confirmed first
The server returns facts and no verdict. The underwriting won’t run until the person checks a box that says this is the price they would pay.
Underwritten in the browser
Then the engine runs on the person’s own inputs and reruns on every edit. Each assumption shows its default and where the default came from.
Its own rules
What it won’t do.
Loep is held to a short list of refusals. These are the ones a reader runs into on every sheet.
- Every figure carries a label for how it was obtained: retrieved, curated, modeled, an assumption, entered, computed or third party. The build fails if that list drifts.
- A value it didn’t read shows as a dash, never as a zero.
- A sample figure is stamped SAMPLE in its sheet’s header.
- Evidence from filed figures, from a company’s own risk headings and from a provider’s news score stays in three separate tiers. It’s never netted into one number.
- A language model writes one optional note, from figures the code has already computed. Its words are never read back into a number.
How it’s built
Checks that stop the build.
The calculation engines are pure modules. They fetch nothing and call no model, so the same arithmetic runs in the browser and on the server, and their tests need no network.
- Each engine is checked against frozen fixtures that were produced by running the code, not typed by hand.
- An inline script in a built page fails the build. So does a privileged database key anywhere in the output.
- Only one server file may reach a language model. A check fails if a second one does.
- The plan rules are rebuilt from the database’s SQL and from the JavaScript, then run over the same profiles. A disagreement fails the build.
- Every table has row-level security (a database rule that decides who can see each row), deny by default. A person reads only their own rows.
The drawing
Contour lines, computed.
Loep’s hero is a terrain of contour lines, traced by marching squares (a standard way to draw contour lines from a grid) over seeded noise. The algorithm is pure, so one piece of code draws the canvas in the browser and the still picture the build prerenders. Under reduced motion the terrain is drawn complete in the first frame.
Withheld from this page
Where it stands
Built, and not open yet.
Loep is deployed behind a sign-in gate today, so this page doesn’t link to it. Card checkout isn’t connected, and an iPhone app is planned and not built. When the gate comes down, the link goes here.
This page leaves out Loep’s data providers, its prices and plan limits, and the settings behind any signal or verdict. Loep keeps those off its own marketing pages too. This page also leaves out every result of the research behind Loep’s indicator.
Built under
Start here
Tell us what’s slow, or what can’t be found.
One paragraph is plenty. Tell us what you want built, the step that costs the most, or the page that should rank and doesn’t. If you know why the obvious fix hasn’t worked, say that too.
Email
daniel@adjlcapital.com
Daniel reads and answers these himself, usually within a day or two. No sequence, no drip, and nothing sold to anyone.