Data you can understand. Intelligence you can verify.
PlacePulse separates active evidence, estimated context, pending layers, and roadmap capabilities — so decision-makers can see exactly what supports a recommendation before they act.
What PlacePulse analyzes today.
The public story stays careful. Every layer is labeled so prospects can tell the difference between active, estimated, pending, and roadmap capability.
Review intelligence
Imported review intelligence and recurring review themes for a specific location anchor.
Place registry metadata
Place registry metadata and coverage status that anchor every profile to a record.
Visit movement context
Estimated visit movement context where source-backed feeds are not yet connected.
Public signals
Public mentions and public signals where available, labeled by recency and source.
AI interpretation
Meridien interpretation over source-linked evidence — always with caveats attached.
POI & Place Context
Nearby anchors, competitors, category density, transport access, and surrounding demand signals — activated per location from public, provider-enriched, or client-supplied POI sources.
Coverage varies by place. Where a layer is estimated or not yet connected, it is labeled — never dressed up as verified.
Review intelligence
ActiveReview evidence is classified into themes, sentiment, and recurring friction patterns — active where coverage exists, then connected to location context and benchmark comparison.
Visit movement context
RoadmapVisit movement and dwell context are treated as roadmap layers until verified source connections are in place. Estimated visit movement is used as directional context, never presented as verified total visitation.
Public signals
ActivePublic mentions and signals are incorporated where available, labeled by recency and source so the read stays honest about coverage.
POI & Place Context
PendingPOI & Place Context identifies nearby anchors, competitors, category clusters, transport access, hospitality, retail, F&B, business density, and other surrounding signals that help explain why a place performs the way it does. Evidence is public/available-source by default, provider-enriched where configured, and client-provided where supplied — always source-labelled and confidence-scored.
EvidenceGraph concept
RoadmapEvidenceGraph is the planned source-lineage layer that will connect each insight to its contributing sources, readiness labels, recency, and caveats — not a claim of current universal coverage.
Privacy-first principles
Principle- Aggregate signals wherever possible.
- Keep source provenance visible.
- Avoid exposing private user or session data.
- Label modeled or estimated layers clearly.
Responsible interpretation
CaveatCoverage varies by place and estimated layers are directional. Recommendations are decision support with stated limitations — not guarantees of outcome.
Every recommendation, traceable end to end.
Nothing reaches a decision-maker without passing through the full chain — and the caveat travels with it.
Signal
Public review, mention, or registry input.
Readiness label
Active, estimated, pending, or roadmap.
Interpretation
Meridien reads the labeled evidence.
Recommendation
A briefable next action for the team.
Caveat
Stated limits travel with the read.
Disciplined evidence, plainly labeled.
Walk through the methodology with our team and see exactly how a recommendation is built, sourced, and qualified before it reaches a decision.