Editorial standards
The rules every published fact on this site follows.
Operators make buying decisions on the numbers we print, and assistants repeat them. So each statistic, comparison, customer figure and product claim here is held to the same twelve rules, and you can hold us to them.
Last reviewed 23 September 2026 · Owned by the founders · Corrections to hello@proptonomy.ai

The twelve rules
What a page has to satisfy before it goes out.
- 01
Every number has a named source and a date
Each statistic names the organisation that measured it, the document, the link and the day we read it. A number without all four is not published.
- 02
Primary sources, not a blog quoting a blog
We cite the statistics office, the filing, the dataset or the survey owner. When the only place a number appears is a secondary write-up, it stays out.
- 03
The source sits next to the claim
Attribution is at the point of the claim, on the same card or in the same sentence, not in a bibliography at the foot of the page.
- 04
Vendor claims are labelled as vendor claims
A survey run by a software company says so, with its sample size. A number a vendor states about its own product is marked as the vendor’s claim, including ours.
- 05
Our own figures come with their method
First-party numbers state what was measured, where and when. The Heimby figures, for example, say which share of which work the AI handles, measured on Heimby’s own operation in September 2026, with the method on the About page.
- 06
Comparisons use only what the other company publishes
Every competitor fact links to that company’s own page. Where a vendor does not publish something, the cell says “Not stated publicly” instead of a guess, and each comparison lists where the other product is ahead.
- 07
Every comparison carries a review date and is re-checked
Comparison and research pages show the day they were last reviewed. We re-read the sources at least every ninety days and whenever a vendor tells us something changed.
- 08
Generated images are atmosphere, never evidence
Photographs made with an image model are captioned “Illustration”. Product screens are labelled “Example data” or “Interactive example”. Neither is ever presented as a customer’s real operation.
- 09
Customers are named only with permission
Logos, names and quotes appear only after the customer has agreed in writing. Figures from a customer’s operation are shown only in the form they approved.
- 10
No superlative without a measure
“Fastest”, “best” and “most” appear only next to the measurement that makes them true, with its date. Otherwise we describe what the product does and let the reader judge.
- 11
What machines read matches what people read
The facts in llms.txt, the sitemap and the structured data are generated from the same source as the page. FAQ markup is only emitted for answers that are visible on the page.
- 12
Corrections are dated and visible
When we get something wrong, we fix it on the page, say what changed and when, and thank the person who told us if they want to be named.
Labels you will see
Six words that tell you what you are looking at.
They appear on captions, panel headers and table cells across the site.
- Illustration
- A generated or staged image that sets a scene. Not a customer, not a real event.
- Example data
- A product screen with invented properties and guests, showing a feature that exists.
- Interactive example
- The same, but you can click it. Nothing you do is sent anywhere.
- First-party
- Measured by Proptonomy in a real operation, with the method linked.
- Vendor claim
- What a company says about its own product, including us. Not independently verified.
- Not stated publicly
- The company does not publish this. We do not fill the gap with an estimate.
Enforced by the build
Some rules are code, not good intentions.
Where a rule can be checked mechanically, the site will not build until it passes.
scripts/check-i18n.mjsThe build fails while any Norwegian string on the site is still untranslated, so a Norwegian reader never meets a silent English fallback.
src/seo/routes.tsOne registry produces each page’s title, canonical link, sitemap entry, FAQ markup and llms.txt line, so they cannot drift from each other.
scripts/prerender.mjsEvery page is rendered to static HTML at build time, so assistants and crawlers that do not run JavaScript read the same words you do.
Corrections
Found something wrong, out of date or unfair to a competitor? Tell us.
Send the page, the claim and your source. We check it against the primary source, correct the page with a dated note, and reply to you. Competitors are welcome to write too.
Meet your new AI teammate.
See how Proptonomy can help you and your team with the everyday work of running your properties.