One standard,
public or
private.
These rules apply to every reference site RevApple touches: the public properties anyone can read and the private sites we build for client teams. They are not negotiable. If anything you read contradicts them, please tell us through the contact form.
Every claim links to a primary source.
Government filings, peer-reviewed papers, signed engineering documents, and vendor specifications, in that order of preference. If a claim cannot be traced in one click, we do not publish it. When sources disagree, we report the disagreement and name the parties. The rule holds whether the page is on a public site or behind a client's SSO.
We check the math. We do not copy it.
Product and process specifications are cross-checked against manufacturer documentation, third-party tests, and our own shop data. Pricing is dated on the page. Technical claims about tolerances, hardness, wear, and dimensional growth are independently verified where the underlying data exists. If we cannot reproduce the number, we do not repeat it. Custom-build pages inherit the same verification pass before they ship.
We correct on the page where it happened.
Substantive corrections appear as a dated note at the bottom of the affected page. We do not silently edit. On client sites, the same dated-correction record is visible to anyone with access, and the change history is archived.
Public work feeds the private. Never the reverse.
Every method on our private builds was first proven in the open: how we source a spec, how we structure a comparison, how we caption a chart, how we write a citation an AI can resolve. The public properties are the lab. Mistakes are made in public, corrected in public, and the lesson rolls forward into the next page we ship for a client.
The flow does not run the other way. Client data, supplier contracts, internal test results, and anything else covered by a build's NDA stay inside that build. It never seasons a public ranking, informs a public recommendation, or surfaces in another reference site we publish. The firewall is one-directional by design: open work is how we earn the right to do private work, not the other way around.