PUBLIC DEMONSTRATION
Correcting B2B SaaS brand facts
This page shows only the customer-facing analysis. The company, website, answers, sources, and recheck numbers are independently written simulations. They do not represent a customer, a live platform result, or material from an internal project.
01What this demonstration checks
| Business | A fictional B2B workflow software company |
| Market | English-speaking US and EU buyers |
| Topics | Data residency, integrations, and support commitments |
| Information | Fictional public pages, fictional third-party pages, and simulated AI answers |
| Result type | Product-shape demonstration, not a customer case or performance claim |
02Start with buyer questions
The demonstration begins with questions a buyer may ask before shortlisting a vendor. The same questions are kept for the later recheck.
- Which workflow tools offer EU data residency?
- Does the product have a native Salesforce integration?
- What should a regulated buyer verify before shortlisting it?
- Which support commitments are publicly documented?
03Compare simulated answers with public statements
| Topic | Simulated answer | Fictional public statement | Potential impact |
|---|---|---|---|
| Data residency | The simulated answer says customer data is US-only. | The fictional trust page says EU hosting is available on selected plans. | A qualified buyer may exclude the product too early. |
| Integration | The simulated answer says Salesforce requires middleware. | The fictional integration page says a native connector is generally available. | Implementation effort may be overstated. |
| Support | One review is generalized into a slow-support verdict. | The fictional support page publishes a plan-specific response target. | An attributed opinion may be mistaken for a universal service fact. |
Opinions are not adjudicated as true or false. Only checkable product scope, policy, and capability claims enter fact correction.
04Where the mismatch may come from
An old comparison page still describes US-only hosting.Simulated source · Outdated
An aggregator predates the native integration release.Simulated source · Version conflict
A single review is summarized as a lasting company-wide service fact.Simulated source · Individual opinion
The public demo explains source type and reasoning only. It does not expose collection records, system objects, accounts, tools, or configuration.
05Turn findings into public content work
| Public asset | Treatment |
|---|---|
| Trust page | State regions, eligible plans, effective dates, and exceptions on one public page. |
| Integration page | Publish availability, supported versions, limitations, and last-updated date. |
| Support policy | Place the documented response target beside its scope and exclusions. |
| Outdated sources | Identify public pages repeating old claims and request correction or refresh. |
The company reviews every public change before publishing. FactRelay does not sign in to websites, auto-publish, or use unapproved customer material.
06Ask the same questions again
| Observation | Simulated baseline | Simulated recheck | Interpretation |
|---|---|---|---|
| Data-residency misstatement | 4 / 5 | 1 / 5 | Directional improvement; not proof of single-page causation. |
| Integration misstatement | 3 / 5 | 3 / 5 | No change; continue observing whether public sources refresh. |
Every number is simulated. A recheck describes a difference between two observations; it is not a ranking promise or causal attribution.
07What the customer sees
- An approved question list and declared review scope;
- A side-by-side view of simulated answers, public statements, and source types;
- Recommended changes to public pages and content;
- A recheck summary using the same questions;
- Sample limitations, unresolved items, and next actions.