LumenRadar Sample Reports | Evidence-chain showcase

Boundary

Public samples may use static fixtures or sample evidence. They do not prove revenue impact, do not replace professional advice, and require manual review before any paid report scope.

Owner-only sample report

PostHog Competitive Intelligence

Fixture-safe public product-positioning sample for evidence-chain presentation.

Sample / preview label

0.76 confidence5 evidence refsPreview onlyNot customer delivery

Mobile summary

PostHog Competitive Intelligence

Fixture-safe public product-positioning sample for evidence-chain presentation.

Evidence: 5 refs
Confidence: 0.76
Review: Needs review
Delivery: Sample only

Evidence table is kept in the full report view so the mobile card stays readable.

View evidence details

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.76
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`posthog-positioning-01`	Product analytics positioning	0.84	Public positioning copy emphasizes product analytics, session replay, and feature usage workflows.	Static sample; does not prove private roadmap, revenue, or customer adoption.	Map each positioning claim to a public source before quoting a deeper competitive report.	pass
`posthog-oss-02`	Open-source repository signal	0.78	Public repository metadata can be used as a transparency and community signal.	Repository activity does not prove commercial momentum.	Separate repository evidence from unsupported market-share assumptions.	review
`posthog-pricing-03`	Pricing / plan page	0.76	Pricing page structure can support a limited packaging comparison.	Public pricing copy may change and does not prove discounting or private contracts.	Snapshot pricing evidence before writing any quote-sensitive claim.	pass
`posthog-docs-04`	Documentation maturity	0.72	Public docs can indicate onboarding and implementation maturity.	Documentation volume does not prove customer success quality.	Score docs by setup path, troubleshooting clarity, and integration coverage.	pass
`posthog-community-05`	Community / issue signal	0.68	Public community or issue activity can show engagement patterns.	Issue volume can indicate either adoption or support burden; human review is required.	Mark community signal as partial unless multiple public sources agree.	review

IDposthog-positioning-01

Source typeProduct analytics positioning

Quality0.84

Evidence snippetPublic positioning copy emphasizes product analytics, session replay, and feature usage workflows.

LimitationStatic sample; does not prove private roadmap, revenue, or customer adoption.

Next actionMap each positioning claim to a public source before quoting a deeper competitive report.

pass

IDposthog-oss-02

Source typeOpen-source repository signal

Quality0.78

Evidence snippetPublic repository metadata can be used as a transparency and community signal.

LimitationRepository activity does not prove commercial momentum.

Next actionSeparate repository evidence from unsupported market-share assumptions.

review

IDposthog-pricing-03

Source typePricing / plan page

Quality0.76

Evidence snippetPricing page structure can support a limited packaging comparison.

LimitationPublic pricing copy may change and does not prove discounting or private contracts.

Next actionSnapshot pricing evidence before writing any quote-sensitive claim.

pass

IDposthog-docs-04

Source typeDocumentation maturity

Quality0.72

Evidence snippetPublic docs can indicate onboarding and implementation maturity.

LimitationDocumentation volume does not prove customer success quality.

Next actionScore docs by setup path, troubleshooting clarity, and integration coverage.

pass

IDposthog-community-05

Source typeCommunity / issue signal

Quality0.68

Evidence snippetPublic community or issue activity can show engagement patterns.

LimitationIssue volume can indicate either adoption or support burden; human review is required.

Next actionMark community signal as partial unless multiple public sources agree.

review

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.76
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`posthog-positioning-01`	Product analytics positioning	0.84	Public positioning copy emphasizes product analytics, session replay, and feature usage workflows.	Static sample; does not prove private roadmap, revenue, or customer adoption.	Map each positioning claim to a public source before quoting a deeper competitive report.	pass
`posthog-oss-02`	Open-source repository signal	0.78	Public repository metadata can be used as a transparency and community signal.	Repository activity does not prove commercial momentum.	Separate repository evidence from unsupported market-share assumptions.	review
`posthog-pricing-03`	Pricing / plan page	0.76	Pricing page structure can support a limited packaging comparison.	Public pricing copy may change and does not prove discounting or private contracts.	Snapshot pricing evidence before writing any quote-sensitive claim.	pass
`posthog-docs-04`	Documentation maturity	0.72	Public docs can indicate onboarding and implementation maturity.	Documentation volume does not prove customer success quality.	Score docs by setup path, troubleshooting clarity, and integration coverage.	pass
`posthog-community-05`	Community / issue signal	0.68	Public community or issue activity can show engagement patterns.	Issue volume can indicate either adoption or support burden; human review is required.	Mark community signal as partial unless multiple public sources agree.	review

IDposthog-positioning-01

Source typeProduct analytics positioning

Quality0.84

Evidence snippetPublic positioning copy emphasizes product analytics, session replay, and feature usage workflows.

LimitationStatic sample; does not prove private roadmap, revenue, or customer adoption.

Next actionMap each positioning claim to a public source before quoting a deeper competitive report.

pass

IDposthog-oss-02

Source typeOpen-source repository signal

Quality0.78

Evidence snippetPublic repository metadata can be used as a transparency and community signal.

LimitationRepository activity does not prove commercial momentum.

Next actionSeparate repository evidence from unsupported market-share assumptions.

review

IDposthog-pricing-03

Source typePricing / plan page

Quality0.76

Evidence snippetPricing page structure can support a limited packaging comparison.

LimitationPublic pricing copy may change and does not prove discounting or private contracts.

Next actionSnapshot pricing evidence before writing any quote-sensitive claim.

pass

IDposthog-docs-04

Source typeDocumentation maturity

Quality0.72

Evidence snippetPublic docs can indicate onboarding and implementation maturity.

LimitationDocumentation volume does not prove customer success quality.

Next actionScore docs by setup path, troubleshooting clarity, and integration coverage.

pass

IDposthog-community-05

Source typeCommunity / issue signal

Quality0.68

Evidence snippetPublic community or issue activity can show engagement patterns.

LimitationIssue volume can indicate either adoption or support burden; human review is required.

Next actionMark community signal as partial unless multiple public sources agree.

review

Limitations

preview only
no live data if fixture
no private data
cannot prove conversion impact or private roadmap

Next action

Clarify which public source supports each positioning claim.
Separate observed evidence from unsupported growth assumptions.
Request manual quote if a deeper competitive report is needed.

Public sample / not a delivered report / no private data / manual review required before quote.

Limitations and delivery boundary

preview only
no live data if fixture
no private data
cannot prove conversion impact or private roadmap

Next action

Clarify which public source supports each positioning claim.
Separate observed evidence from unsupported growth assumptions.
Request manual quote if a deeper competitive report is needed.

Public sample / not a delivered report / no private data / manual review required before quote.

Owner-only sample report

Plausible Analytics Competitive Intelligence

Static preview fixture showing how public signals become limited claims.

Sample / preview label

0.74 confidence5 evidence refsPreview onlyNot customer delivery

Mobile summary

Plausible Analytics Competitive Intelligence

Static preview fixture showing how public signals become limited claims.

Evidence: 5 refs
Confidence: 0.74
Review: Needs review
Delivery: Sample only

Evidence table is kept in the full report view so the mobile card stays readable.

View evidence details

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.74
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`plausible-privacy-01`	Privacy-first analytics positioning	0.85	Public copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.	Positioning copy does not prove compliance outcome for a specific customer.	Keep compliance wording bounded to public claims and reviewed evidence.	pass
`plausible-oss-02`	Open-source transparency	0.79	Public repository or transparency material can support an openness signal.	Open-source presence does not prove service reliability or support quality.	Pair repository signal with docs and pricing evidence before report judgment.	pass
`plausible-pricing-03`	Pricing page	0.74	Pricing page structure can be used to compare packaging clarity and buyer friction.	Does not prove negotiated pricing or actual customer willingness to pay.	Quote public prices only with fetched date and limitation.	review
`plausible-docs-04`	Documentation	0.71	Docs can show whether setup, integration, and privacy tradeoffs are explained.	Docs do not prove implementation success for every stack.	Use docs evidence to identify setup-risk questions for manual review.	pass
`plausible-market-05`	Alternatives / market comparison	0.66	Public alternative pages can surface how buyers compare analytics options.	Comparison pages may be biased or incomplete.	Treat comparison evidence as context, not final market proof.	review

IDplausible-privacy-01

Source typePrivacy-first analytics positioning

Quality0.85

Evidence snippetPublic copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.

LimitationPositioning copy does not prove compliance outcome for a specific customer.

Next actionKeep compliance wording bounded to public claims and reviewed evidence.

pass

IDplausible-oss-02

Source typeOpen-source transparency

Quality0.79

Evidence snippetPublic repository or transparency material can support an openness signal.

LimitationOpen-source presence does not prove service reliability or support quality.

Next actionPair repository signal with docs and pricing evidence before report judgment.

pass

IDplausible-pricing-03

Source typePricing page

Quality0.74

Evidence snippetPricing page structure can be used to compare packaging clarity and buyer friction.

LimitationDoes not prove negotiated pricing or actual customer willingness to pay.

Next actionQuote public prices only with fetched date and limitation.

review

IDplausible-docs-04

Source typeDocumentation

Quality0.71

Evidence snippetDocs can show whether setup, integration, and privacy tradeoffs are explained.

LimitationDocs do not prove implementation success for every stack.

Next actionUse docs evidence to identify setup-risk questions for manual review.

pass

IDplausible-market-05

Source typeAlternatives / market comparison

Quality0.66

Evidence snippetPublic alternative pages can surface how buyers compare analytics options.

LimitationComparison pages may be biased or incomplete.

Next actionTreat comparison evidence as context, not final market proof.

review

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.74
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`plausible-privacy-01`	Privacy-first analytics positioning	0.85	Public copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.	Positioning copy does not prove compliance outcome for a specific customer.	Keep compliance wording bounded to public claims and reviewed evidence.	pass
`plausible-oss-02`	Open-source transparency	0.79	Public repository or transparency material can support an openness signal.	Open-source presence does not prove service reliability or support quality.	Pair repository signal with docs and pricing evidence before report judgment.	pass
`plausible-pricing-03`	Pricing page	0.74	Pricing page structure can be used to compare packaging clarity and buyer friction.	Does not prove negotiated pricing or actual customer willingness to pay.	Quote public prices only with fetched date and limitation.	review
`plausible-docs-04`	Documentation	0.71	Docs can show whether setup, integration, and privacy tradeoffs are explained.	Docs do not prove implementation success for every stack.	Use docs evidence to identify setup-risk questions for manual review.	pass
`plausible-market-05`	Alternatives / market comparison	0.66	Public alternative pages can surface how buyers compare analytics options.	Comparison pages may be biased or incomplete.	Treat comparison evidence as context, not final market proof.	review

IDplausible-privacy-01

Source typePrivacy-first analytics positioning

Quality0.85

Evidence snippetPublic copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.

LimitationPositioning copy does not prove compliance outcome for a specific customer.

Next actionKeep compliance wording bounded to public claims and reviewed evidence.

pass

IDplausible-oss-02

Source typeOpen-source transparency

Quality0.79

Evidence snippetPublic repository or transparency material can support an openness signal.

LimitationOpen-source presence does not prove service reliability or support quality.

Next actionPair repository signal with docs and pricing evidence before report judgment.

pass

IDplausible-pricing-03

Source typePricing page

Quality0.74

Evidence snippetPricing page structure can be used to compare packaging clarity and buyer friction.

LimitationDoes not prove negotiated pricing or actual customer willingness to pay.

Next actionQuote public prices only with fetched date and limitation.

review

IDplausible-docs-04

Source typeDocumentation

Quality0.71

Evidence snippetDocs can show whether setup, integration, and privacy tradeoffs are explained.

LimitationDocs do not prove implementation success for every stack.

Next actionUse docs evidence to identify setup-risk questions for manual review.

pass

IDplausible-market-05

Source typeAlternatives / market comparison

Quality0.66

Evidence snippetPublic alternative pages can surface how buyers compare analytics options.

LimitationComparison pages may be biased or incomplete.

Next actionTreat comparison evidence as context, not final market proof.

review

Limitations

preview only
no live data if fixture
no private data
requires human review before any future delivery path

Next action

Turn high-confidence public observations into a limited report outline.
Flag unsupported claims before they reach a reviewed report.
Use manual review before quoting any deeper analysis.

Public sample / not a delivered report / no private data / manual review required before quote.

Limitations and delivery boundary

preview only
no live data if fixture
no private data
requires human review before any future delivery path

Next action

Turn high-confidence public observations into a limited report outline.
Flag unsupported claims before they reach a reviewed report.
Use manual review before quoting any deeper analysis.

Public sample / not a delivered report / no private data / manual review required before quote.

Owner-only sample report

Website Commercial Health Check

Public website sample showing how evidence, confidence, limitation, and next action are separated for a business health check.

Sample report / public launch v1

0.71 confidence5 evidence refsPreview onlyNot customer delivery

Mobile summary

Website Commercial Health Check

Public website sample showing how evidence, confidence, limitation, and next action are separated for a business health check.

Evidence: 5 refs
Confidence: 0.71
Review: Needs review
Delivery: Sample only

Evidence table is kept in the full report view so the mobile card stays readable.

View evidence details

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.71
Review status: Needs review
Delivery status: public sample / not delivered report

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`health-hero-01`	Hero / CTA clarity	0.83	Hero copy, primary CTA, and supporting badges show the first-screen promise.	A clear hero does not prove conversion uplift.	Rewrite unclear first-screen copy before testing paid acquisition.	pass
`health-request-02`	Request flow	0.81	Request page explains manual review, quote later, and no automatic payment.	Form completion data is not available from this static sample.	Track request completion and drop-off after launch.	pass
`health-pricing-03`	Pricing boundary	0.77	Pricing copy states no checkout, no webhook, and manual quote after review.	Manual quote readiness does not prove payment-provider readiness.	Keep automatic checkout disabled until a separate payment gate passes.	pass
`health-policy-04`	Policy / trust signals	0.74	Policy content separates allowed public-source analysis from prohibited access.	Policy copy does not replace legal advice.	Keep security, privacy, and terms links visible in footer.	review
`health-friction-05`	Conversion friction	0.70	Multiple disabled states and manual review notes may slow some buyers but reduce overclaiming.	Requires real funnel data before ranking as a business blocker.	Use first request logs to decide which boundary copy can be shortened safely.	review

IDhealth-hero-01

Source typeHero / CTA clarity

Quality0.83

Evidence snippetHero copy, primary CTA, and supporting badges show the first-screen promise.

LimitationA clear hero does not prove conversion uplift.

Next actionRewrite unclear first-screen copy before testing paid acquisition.

pass

IDhealth-request-02

Source typeRequest flow

Quality0.81

Evidence snippetRequest page explains manual review, quote later, and no automatic payment.

LimitationForm completion data is not available from this static sample.

Next actionTrack request completion and drop-off after launch.

pass

IDhealth-pricing-03

Source typePricing boundary

Quality0.77

Evidence snippetPricing copy states no checkout, no webhook, and manual quote after review.

LimitationManual quote readiness does not prove payment-provider readiness.

Next actionKeep automatic checkout disabled until a separate payment gate passes.

pass

IDhealth-policy-04

Source typePolicy / trust signals

Quality0.74

Evidence snippetPolicy content separates allowed public-source analysis from prohibited access.

LimitationPolicy copy does not replace legal advice.

Next actionKeep security, privacy, and terms links visible in footer.

review

IDhealth-friction-05

Source typeConversion friction

Quality0.70

Evidence snippetMultiple disabled states and manual review notes may slow some buyers but reduce overclaiming.

LimitationRequires real funnel data before ranking as a business blocker.

Next actionUse first request logs to decide which boundary copy can be shortened safely.

review

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.71
Review status: Needs review
Delivery status: public sample / not delivered report

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`health-hero-01`	Hero / CTA clarity	0.83	Hero copy, primary CTA, and supporting badges show the first-screen promise.	A clear hero does not prove conversion uplift.	Rewrite unclear first-screen copy before testing paid acquisition.	pass
`health-request-02`	Request flow	0.81	Request page explains manual review, quote later, and no automatic payment.	Form completion data is not available from this static sample.	Track request completion and drop-off after launch.	pass
`health-pricing-03`	Pricing boundary	0.77	Pricing copy states no checkout, no webhook, and manual quote after review.	Manual quote readiness does not prove payment-provider readiness.	Keep automatic checkout disabled until a separate payment gate passes.	pass
`health-policy-04`	Policy / trust signals	0.74	Policy content separates allowed public-source analysis from prohibited access.	Policy copy does not replace legal advice.	Keep security, privacy, and terms links visible in footer.	review
`health-friction-05`	Conversion friction	0.70	Multiple disabled states and manual review notes may slow some buyers but reduce overclaiming.	Requires real funnel data before ranking as a business blocker.	Use first request logs to decide which boundary copy can be shortened safely.	review

IDhealth-hero-01

Source typeHero / CTA clarity

Quality0.83

Evidence snippetHero copy, primary CTA, and supporting badges show the first-screen promise.

LimitationA clear hero does not prove conversion uplift.

Next actionRewrite unclear first-screen copy before testing paid acquisition.

pass

IDhealth-request-02

Source typeRequest flow

Quality0.81

Evidence snippetRequest page explains manual review, quote later, and no automatic payment.

LimitationForm completion data is not available from this static sample.

Next actionTrack request completion and drop-off after launch.

pass

IDhealth-pricing-03

Source typePricing boundary

Quality0.77

Evidence snippetPricing copy states no checkout, no webhook, and manual quote after review.

LimitationManual quote readiness does not prove payment-provider readiness.

Next actionKeep automatic checkout disabled until a separate payment gate passes.

pass

IDhealth-policy-04

Source typePolicy / trust signals

Quality0.74

Evidence snippetPolicy content separates allowed public-source analysis from prohibited access.

LimitationPolicy copy does not replace legal advice.

Next actionKeep security, privacy, and terms links visible in footer.

review

IDhealth-friction-05

Source typeConversion friction

Quality0.70

Evidence snippetMultiple disabled states and manual review notes may slow some buyers but reduce overclaiming.

LimitationRequires real funnel data before ranking as a business blocker.

Next actionUse first request logs to decide which boundary copy can be shortened safely.

review

Limitations

sample report only
does not prove revenue impact
does not replace legal, financial, or security advice
manual review required before any paid scope

Next action

Submit a public URL or business question through Start a report.
Review the source plan and limitations before quote.
Use the 7-day actions as hypotheses, then measure 30-day indicators.

Public sample / not a delivered report / no private data / manual review required before quote.

Limitations and delivery boundary

sample report only
does not prove revenue impact
does not replace legal, financial, or security advice
manual review required before any paid scope

Next action

Submit a public URL or business question through Start a report.
Review the source plan and limitations before quote.
Use the 7-day actions as hypotheses, then measure 30-day indicators.

Public sample / not a delivered report / no private data / manual review required before quote.

Owner-only sample report

PostHog Competitive Intelligence

Fixture-safe public product-positioning sample for evidence-chain presentation.

Sample / preview label

0.76 confidence5 evidence refsPreview onlyNot customer delivery

Mobile summary

PostHog Competitive Intelligence

Fixture-safe public product-positioning sample for evidence-chain presentation.

Evidence: 5 refs
Confidence: 0.76
Review: Needs review
Delivery: Sample only

Evidence table is kept in the full report view so the mobile card stays readable.

View evidence details

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.76
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`posthog-positioning-01`	Product analytics positioning	0.84	Public positioning copy emphasizes product analytics, session replay, and feature usage workflows.	Static sample; does not prove private roadmap, revenue, or customer adoption.	Map each positioning claim to a public source before quoting a deeper competitive report.	pass
`posthog-oss-02`	Open-source repository signal	0.78	Public repository metadata can be used as a transparency and community signal.	Repository activity does not prove commercial momentum.	Separate repository evidence from unsupported market-share assumptions.	review
`posthog-pricing-03`	Pricing / plan page	0.76	Pricing page structure can support a limited packaging comparison.	Public pricing copy may change and does not prove discounting or private contracts.	Snapshot pricing evidence before writing any quote-sensitive claim.	pass
`posthog-docs-04`	Documentation maturity	0.72	Public docs can indicate onboarding and implementation maturity.	Documentation volume does not prove customer success quality.	Score docs by setup path, troubleshooting clarity, and integration coverage.	pass
`posthog-community-05`	Community / issue signal	0.68	Public community or issue activity can show engagement patterns.	Issue volume can indicate either adoption or support burden; human review is required.	Mark community signal as partial unless multiple public sources agree.	review

IDposthog-positioning-01

Source typeProduct analytics positioning

Quality0.84

Evidence snippetPublic positioning copy emphasizes product analytics, session replay, and feature usage workflows.

LimitationStatic sample; does not prove private roadmap, revenue, or customer adoption.

Next actionMap each positioning claim to a public source before quoting a deeper competitive report.

pass

IDposthog-oss-02

Source typeOpen-source repository signal

Quality0.78

Evidence snippetPublic repository metadata can be used as a transparency and community signal.

LimitationRepository activity does not prove commercial momentum.

Next actionSeparate repository evidence from unsupported market-share assumptions.

review

IDposthog-pricing-03

Source typePricing / plan page

Quality0.76

Evidence snippetPricing page structure can support a limited packaging comparison.

LimitationPublic pricing copy may change and does not prove discounting or private contracts.

Next actionSnapshot pricing evidence before writing any quote-sensitive claim.

pass

IDposthog-docs-04

Source typeDocumentation maturity

Quality0.72

Evidence snippetPublic docs can indicate onboarding and implementation maturity.

LimitationDocumentation volume does not prove customer success quality.

Next actionScore docs by setup path, troubleshooting clarity, and integration coverage.

pass

IDposthog-community-05

Source typeCommunity / issue signal

Quality0.68

Evidence snippetPublic community or issue activity can show engagement patterns.

LimitationIssue volume can indicate either adoption or support burden; human review is required.

Next actionMark community signal as partial unless multiple public sources agree.

review

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.76
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`posthog-positioning-01`	Product analytics positioning	0.84	Public positioning copy emphasizes product analytics, session replay, and feature usage workflows.	Static sample; does not prove private roadmap, revenue, or customer adoption.	Map each positioning claim to a public source before quoting a deeper competitive report.	pass
`posthog-oss-02`	Open-source repository signal	0.78	Public repository metadata can be used as a transparency and community signal.	Repository activity does not prove commercial momentum.	Separate repository evidence from unsupported market-share assumptions.	review
`posthog-pricing-03`	Pricing / plan page	0.76	Pricing page structure can support a limited packaging comparison.	Public pricing copy may change and does not prove discounting or private contracts.	Snapshot pricing evidence before writing any quote-sensitive claim.	pass
`posthog-docs-04`	Documentation maturity	0.72	Public docs can indicate onboarding and implementation maturity.	Documentation volume does not prove customer success quality.	Score docs by setup path, troubleshooting clarity, and integration coverage.	pass
`posthog-community-05`	Community / issue signal	0.68	Public community or issue activity can show engagement patterns.	Issue volume can indicate either adoption or support burden; human review is required.	Mark community signal as partial unless multiple public sources agree.	review

IDposthog-positioning-01

Source typeProduct analytics positioning

Quality0.84

Evidence snippetPublic positioning copy emphasizes product analytics, session replay, and feature usage workflows.

LimitationStatic sample; does not prove private roadmap, revenue, or customer adoption.

Next actionMap each positioning claim to a public source before quoting a deeper competitive report.

pass

IDposthog-oss-02

Source typeOpen-source repository signal

Quality0.78

Evidence snippetPublic repository metadata can be used as a transparency and community signal.

LimitationRepository activity does not prove commercial momentum.

Next actionSeparate repository evidence from unsupported market-share assumptions.

review

IDposthog-pricing-03

Source typePricing / plan page

Quality0.76

Evidence snippetPricing page structure can support a limited packaging comparison.

LimitationPublic pricing copy may change and does not prove discounting or private contracts.

Next actionSnapshot pricing evidence before writing any quote-sensitive claim.

pass

IDposthog-docs-04

Source typeDocumentation maturity

Quality0.72

Evidence snippetPublic docs can indicate onboarding and implementation maturity.

LimitationDocumentation volume does not prove customer success quality.

Next actionScore docs by setup path, troubleshooting clarity, and integration coverage.

pass

IDposthog-community-05

Source typeCommunity / issue signal

Quality0.68

Evidence snippetPublic community or issue activity can show engagement patterns.

LimitationIssue volume can indicate either adoption or support burden; human review is required.

Next actionMark community signal as partial unless multiple public sources agree.

review

Limitations

preview only
no live data if fixture
no private data
cannot prove conversion impact or private roadmap

Next action

Clarify which public source supports each positioning claim.
Separate observed evidence from unsupported growth assumptions.
Request manual quote if a deeper competitive report is needed.

Public sample / not a delivered report / no private data / manual review required before quote.

Limitations and delivery boundary

preview only
no live data if fixture
no private data
cannot prove conversion impact or private roadmap

Next action

Clarify which public source supports each positioning claim.
Separate observed evidence from unsupported growth assumptions.
Request manual quote if a deeper competitive report is needed.

Public sample / not a delivered report / no private data / manual review required before quote.

Plausible Analytics Competitive Intelligence

Owner-only sample report

Plausible Analytics Competitive Intelligence

Static preview fixture showing how public signals become limited claims.

Sample / preview label

0.74 confidence5 evidence refsPreview onlyNot customer delivery

Mobile summary

Plausible Analytics Competitive Intelligence

Static preview fixture showing how public signals become limited claims.

Evidence: 5 refs
Confidence: 0.74
Review: Needs review
Delivery: Sample only

Evidence table is kept in the full report view so the mobile card stays readable.

View evidence details

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.74
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`plausible-privacy-01`	Privacy-first analytics positioning	0.85	Public copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.	Positioning copy does not prove compliance outcome for a specific customer.	Keep compliance wording bounded to public claims and reviewed evidence.	pass
`plausible-oss-02`	Open-source transparency	0.79	Public repository or transparency material can support an openness signal.	Open-source presence does not prove service reliability or support quality.	Pair repository signal with docs and pricing evidence before report judgment.	pass
`plausible-pricing-03`	Pricing page	0.74	Pricing page structure can be used to compare packaging clarity and buyer friction.	Does not prove negotiated pricing or actual customer willingness to pay.	Quote public prices only with fetched date and limitation.	review
`plausible-docs-04`	Documentation	0.71	Docs can show whether setup, integration, and privacy tradeoffs are explained.	Docs do not prove implementation success for every stack.	Use docs evidence to identify setup-risk questions for manual review.	pass
`plausible-market-05`	Alternatives / market comparison	0.66	Public alternative pages can surface how buyers compare analytics options.	Comparison pages may be biased or incomplete.	Treat comparison evidence as context, not final market proof.	review

IDplausible-privacy-01

Source typePrivacy-first analytics positioning

Quality0.85

Evidence snippetPublic copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.

LimitationPositioning copy does not prove compliance outcome for a specific customer.

Next actionKeep compliance wording bounded to public claims and reviewed evidence.

pass

IDplausible-oss-02

Source typeOpen-source transparency

Quality0.79

Evidence snippetPublic repository or transparency material can support an openness signal.

LimitationOpen-source presence does not prove service reliability or support quality.

Next actionPair repository signal with docs and pricing evidence before report judgment.

pass

IDplausible-pricing-03

Source typePricing page

Quality0.74

Evidence snippetPricing page structure can be used to compare packaging clarity and buyer friction.

LimitationDoes not prove negotiated pricing or actual customer willingness to pay.

Next actionQuote public prices only with fetched date and limitation.

review

IDplausible-docs-04

Source typeDocumentation

Quality0.71

Evidence snippetDocs can show whether setup, integration, and privacy tradeoffs are explained.

LimitationDocs do not prove implementation success for every stack.

Next actionUse docs evidence to identify setup-risk questions for manual review.

pass

IDplausible-market-05

Source typeAlternatives / market comparison

Quality0.66

Evidence snippetPublic alternative pages can surface how buyers compare analytics options.

LimitationComparison pages may be biased or incomplete.

Next actionTreat comparison evidence as context, not final market proof.

review

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.74
Review status: Needs review
Delivery status: NOT customer delivery

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`plausible-privacy-01`	Privacy-first analytics positioning	0.85	Public copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.	Positioning copy does not prove compliance outcome for a specific customer.	Keep compliance wording bounded to public claims and reviewed evidence.	pass
`plausible-oss-02`	Open-source transparency	0.79	Public repository or transparency material can support an openness signal.	Open-source presence does not prove service reliability or support quality.	Pair repository signal with docs and pricing evidence before report judgment.	pass
`plausible-pricing-03`	Pricing page	0.74	Pricing page structure can be used to compare packaging clarity and buyer friction.	Does not prove negotiated pricing or actual customer willingness to pay.	Quote public prices only with fetched date and limitation.	review
`plausible-docs-04`	Documentation	0.71	Docs can show whether setup, integration, and privacy tradeoffs are explained.	Docs do not prove implementation success for every stack.	Use docs evidence to identify setup-risk questions for manual review.	pass
`plausible-market-05`	Alternatives / market comparison	0.66	Public alternative pages can surface how buyers compare analytics options.	Comparison pages may be biased or incomplete.	Treat comparison evidence as context, not final market proof.	review

IDplausible-privacy-01

Source typePrivacy-first analytics positioning

Quality0.85

Evidence snippetPublic copy frames analytics around privacy, lightweight measurement, and cookie-light workflows.

LimitationPositioning copy does not prove compliance outcome for a specific customer.

Next actionKeep compliance wording bounded to public claims and reviewed evidence.

pass

IDplausible-oss-02

Source typeOpen-source transparency

Quality0.79

Evidence snippetPublic repository or transparency material can support an openness signal.

LimitationOpen-source presence does not prove service reliability or support quality.

Next actionPair repository signal with docs and pricing evidence before report judgment.

pass

IDplausible-pricing-03

Source typePricing page

Quality0.74

Evidence snippetPricing page structure can be used to compare packaging clarity and buyer friction.

LimitationDoes not prove negotiated pricing or actual customer willingness to pay.

Next actionQuote public prices only with fetched date and limitation.

review

IDplausible-docs-04

Source typeDocumentation

Quality0.71

Evidence snippetDocs can show whether setup, integration, and privacy tradeoffs are explained.

LimitationDocs do not prove implementation success for every stack.

Next actionUse docs evidence to identify setup-risk questions for manual review.

pass

IDplausible-market-05

Source typeAlternatives / market comparison

Quality0.66

Evidence snippetPublic alternative pages can surface how buyers compare analytics options.

LimitationComparison pages may be biased or incomplete.

Next actionTreat comparison evidence as context, not final market proof.

review

Limitations

preview only
no live data if fixture
no private data
requires human review before any future delivery path

Next action

Turn high-confidence public observations into a limited report outline.
Flag unsupported claims before they reach a reviewed report.
Use manual review before quoting any deeper analysis.

Public sample / not a delivered report / no private data / manual review required before quote.

Limitations and delivery boundary

preview only
no live data if fixture
no private data
requires human review before any future delivery path

Next action

Turn high-confidence public observations into a limited report outline.
Flag unsupported claims before they reach a reviewed report.
Use manual review before quoting any deeper analysis.

Public sample / not a delivered report / no private data / manual review required before quote.

Website Commercial Health Check

Owner-only sample report

Website Commercial Health Check

Public website sample showing how evidence, confidence, limitation, and next action are separated for a business health check.

Sample report / public launch v1

0.71 confidence5 evidence refsPreview onlyNot customer delivery

Mobile summary

Website Commercial Health Check

Public website sample showing how evidence, confidence, limitation, and next action are separated for a business health check.

Evidence: 5 refs
Confidence: 0.71
Review: Needs review
Delivery: Sample only

Evidence table is kept in the full report view so the mobile card stays readable.

View evidence details

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.71
Review status: Needs review
Delivery status: public sample / not delivered report

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`health-hero-01`	Hero / CTA clarity	0.83	Hero copy, primary CTA, and supporting badges show the first-screen promise.	A clear hero does not prove conversion uplift.	Rewrite unclear first-screen copy before testing paid acquisition.	pass
`health-request-02`	Request flow	0.81	Request page explains manual review, quote later, and no automatic payment.	Form completion data is not available from this static sample.	Track request completion and drop-off after launch.	pass
`health-pricing-03`	Pricing boundary	0.77	Pricing copy states no checkout, no webhook, and manual quote after review.	Manual quote readiness does not prove payment-provider readiness.	Keep automatic checkout disabled until a separate payment gate passes.	pass
`health-policy-04`	Policy / trust signals	0.74	Policy content separates allowed public-source analysis from prohibited access.	Policy copy does not replace legal advice.	Keep security, privacy, and terms links visible in footer.	review
`health-friction-05`	Conversion friction	0.70	Multiple disabled states and manual review notes may slow some buyers but reduce overclaiming.	Requires real funnel data before ranking as a business blocker.	Use first request logs to decide which boundary copy can be shortened safely.	review

IDhealth-hero-01

Source typeHero / CTA clarity

Quality0.83

Evidence snippetHero copy, primary CTA, and supporting badges show the first-screen promise.

LimitationA clear hero does not prove conversion uplift.

Next actionRewrite unclear first-screen copy before testing paid acquisition.

pass

IDhealth-request-02

Source typeRequest flow

Quality0.81

Evidence snippetRequest page explains manual review, quote later, and no automatic payment.

LimitationForm completion data is not available from this static sample.

Next actionTrack request completion and drop-off after launch.

pass

IDhealth-pricing-03

Source typePricing boundary

Quality0.77

Evidence snippetPricing copy states no checkout, no webhook, and manual quote after review.

LimitationManual quote readiness does not prove payment-provider readiness.

Next actionKeep automatic checkout disabled until a separate payment gate passes.

pass

IDhealth-policy-04

Source typePolicy / trust signals

Quality0.74

Evidence snippetPolicy content separates allowed public-source analysis from prohibited access.

LimitationPolicy copy does not replace legal advice.

Next actionKeep security, privacy, and terms links visible in footer.

review

IDhealth-friction-05

Source typeConversion friction

Quality0.70

Evidence snippetMultiple disabled states and manual review notes may slow some buyers but reduce overclaiming.

LimitationRequires real funnel data before ranking as a business blocker.

Next actionUse first request logs to decide which boundary copy can be shortened safely.

review

Evidence Chain FlowSource -> Evidence -> Claim -> Report

Source

Public source or fixture-safe source candidate

quality checked

public source
source quality
access boundary

Evidence

Snippet, snapshot, and quality fields stay traceable

evidence ref

evidence ref
snapshot/hash
quality score

Claim

Judgment is limited to what the evidence supports

review required

supports / partial / unknown
confidence
limitations

Report

Public sample report with explicit delivery boundary

not customer delivery

public sample
manual review
limitations

Evidence count: 5
Confidence score: 0.71
Review status: Needs review
Delivery status: public sample / not delivered report

ID	Source type	Quality	Evidence snippet	Limitation	Next action	Status
`health-hero-01`	Hero / CTA clarity	0.83	Hero copy, primary CTA, and supporting badges show the first-screen promise.	A clear hero does not prove conversion uplift.	Rewrite unclear first-screen copy before testing paid acquisition.	pass
`health-request-02`	Request flow	0.81	Request page explains manual review, quote later, and no automatic payment.	Form completion data is not available from this static sample.	Track request completion and drop-off after launch.	pass
`health-pricing-03`	Pricing boundary	0.77	Pricing copy states no checkout, no webhook, and manual quote after review.	Manual quote readiness does not prove payment-provider readiness.	Keep automatic checkout disabled until a separate payment gate passes.	pass
`health-policy-04`	Policy / trust signals	0.74	Policy content separates allowed public-source analysis from prohibited access.	Policy copy does not replace legal advice.	Keep security, privacy, and terms links visible in footer.	review
`health-friction-05`	Conversion friction	0.70	Multiple disabled states and manual review notes may slow some buyers but reduce overclaiming.	Requires real funnel data before ranking as a business blocker.	Use first request logs to decide which boundary copy can be shortened safely.	review

IDhealth-hero-01

Source typeHero / CTA clarity

Quality0.83

Evidence snippetHero copy, primary CTA, and supporting badges show the first-screen promise.

LimitationA clear hero does not prove conversion uplift.

Next actionRewrite unclear first-screen copy before testing paid acquisition.

pass

IDhealth-request-02

Source typeRequest flow

Quality0.81

Evidence snippetRequest page explains manual review, quote later, and no automatic payment.

LimitationForm completion data is not available from this static sample.

Next actionTrack request completion and drop-off after launch.

pass

IDhealth-pricing-03

Source typePricing boundary

Quality0.77

Evidence snippetPricing copy states no checkout, no webhook, and manual quote after review.

LimitationManual quote readiness does not prove payment-provider readiness.

Next actionKeep automatic checkout disabled until a separate payment gate passes.

pass

IDhealth-policy-04

Source typePolicy / trust signals

Quality0.74

Evidence snippetPolicy content separates allowed public-source analysis from prohibited access.

LimitationPolicy copy does not replace legal advice.

Next actionKeep security, privacy, and terms links visible in footer.

review

IDhealth-friction-05

Source typeConversion friction

Quality0.70

Evidence snippetMultiple disabled states and manual review notes may slow some buyers but reduce overclaiming.

LimitationRequires real funnel data before ranking as a business blocker.

Next actionUse first request logs to decide which boundary copy can be shortened safely.

review

Limitations

sample report only
does not prove revenue impact
does not replace legal, financial, or security advice
manual review required before any paid scope

Next action

Submit a public URL or business question through Start a report.
Review the source plan and limitations before quote.
Use the 7-day actions as hypotheses, then measure 30-day indicators.

Public sample / not a delivered report / no private data / manual review required before quote.

Limitations and delivery boundary

sample report only
does not prove revenue impact
does not replace legal, financial, or security advice
manual review required before any paid scope

Next action

Submit a public URL or business question through Start a report.
Review the source plan and limitations before quote.
Use the 7-day actions as hypotheses, then measure 30-day indicators.

Public sample / not a delivered report / no private data / manual review required before quote.

Standalone Evidence Samples

Each evidence sample is labeled as dry-run/sample and keeps snippet text separate from verified evidence.

posthog-positioning-01

evidence_id: posthog-positioning-01
source_type: Product analytics positioning
quality: 0.85
type=dry-run/sample: dry-run/sample
status=sample: sample
snippet: Public product copy can support a bounded positioning observation.
limitation: Static sample; does not prove private roadmap or customer adoption.

plausible-privacy-01

evidence_id: plausible-privacy-01
source_type: Privacy-first analytics positioning
quality: 0.85
type=dry-run/sample: dry-run/sample
status=sample: sample
snippet: Public privacy-first messaging can support a limited product-positioning claim.
limitation: Does not prove legal compliance for a specific customer.

health-request-02

evidence_id: health-request-02
source_type: Request flow
quality: 0.81
type=dry-run/sample: dry-run/sample
status=sample: sample
snippet: A review-gated request page can support a safe launch-readiness claim.
limitation: No customer delivery and no private customer data are represented.

Boundary

All samples are examples. Request a review-gated report when you need a scoped analysis and manual quote.