One person, one rule: every claim names its page.
Answerlore is built and run by Colby Richard, its founder, from Shreveport, Louisiana. This page says who that is, what every page on this site is held to, and how to get one corrected.
Colby Richard is the founder of Answerlore and, so far, its whole staff: the person who designed the product, wrote the six-phase method it deploys with, built the ingestion and answering pipeline, and writes every page on this site. A guided trial request, a walkthrough booking, or a note to hello@answerlore.com all reach Colby directly, and the reply comes from Colby.
Answerlore is based in Shreveport, Louisiana. It has no customers to name yet and no certifications it has not earned. The Your data page lists the ones it does not hold.
The product refuses to answer from anything but a loaded document. The site follows the same rule. A number on this site either names its source on the page, or it is labelled as an estimate, or it is not here. The walkthrough on the home page is labelled illustrative because it runs on a fictional sample workspace. The founder statement is labelled a founder statement because it is not a customer testimonial. The hold-time guide lists the inputs it estimated so that you can argue with them.
Prices are printed from one file and checked by a script on every change, so the pricing page, the machine-readable pricing.md, and the structured data behind them cannot disagree with each other.
If a page here is wrong, write to hello@answerlore.com with the page address and the sentence. A factual correction is made within a few days, the page's last-updated date changes, and you get a reply saying what changed. That is how a support lead corrects an answer inside the product, and it would be strange to hold the marketing to a lower standard than the product.
The site names no customer without written permission, quotes no person without their title, and publishes no statistic it cannot link to.
Answerlore's design argument is written up in Why it refuses. The loop a technician sees is in How it works. What the first month of work produces is shown in the worked Knowledge Map, on a fictional dealer with the arithmetic shown. Longer pieces land on Resources first.
See it answer. See it refuse.
A guided trial runs on your manuals. Bring the question your best technician is tired of answering.