Context Map

The graph that shows how work actually influences work.

Supported company objects and relationships form a map you can investigate. The interactive example below uses a sample workspace; your map depends on available evidence.

LoreflowLoreflowNotionGuided OnboardingNotionQ2 RoadmapFigmaOnboarding specsGitHubPR #2841LinearRelease 4.9SentryIncident 118IntercomActivation feedbackZoomCustomer callsPostHogActivation funnelStripeExpansion MRRHubSpotEnterprise pipelineGoogle DocsPricing v3Google DocsActivation over SSOAirtableHire 2 growth eng.Google DriveBoard pack May
Drag nodes to move · drag the canvas to pan · click a node to inspect
Loreflow logo

Loreflow

Company

Your company brain. Everything connects through here.

Imported from Notion · Company · influence 100/100 · 7 direct relationships

Related objects — click to expand the map around them

StrongMediumWeak16 nodes · 23 links

Nodes per cluster

How the graph groups your company.

  • Company4
  • Product4
  • Engineering3
  • Customer2
  • Revenue3

Clusters

Product

Guided OnboardingMobile InvitesChecklist TelemetryRoadmap Q2

Engineering

Release 4.9PR #2841Incident 118Workflow automation

Revenue

Expansion MRRChurn cohortPricing testEnterprise pipeline

Company

Board decisionsHiring planOKRsFundraising

Follow one thread from feature to hiring plan.

Notion logoGuided OnboardingOwned by Priya RamanFeature
GitHub logoPR #2841 — onboarding checklistMerged May 12 · 24 filesPull Request
Linear logoRelease 4.9Shipped May 14 · 100% rolloutRelease
Intercom logoActivation feedback cluster41 conversations · 12 accountsCustomer Feedback
Stripe logoExpansion revenue$182k MRR · +4.1% MoMRevenue
Google Docs logoPrioritise activation over enterprise SSOLogged May 21 · High confidenceBoard Decision
Airtable logoHire 2 growth engineersOpen · Target start JulyHiring

FAQ

About the context map.

Relationships and provenance.

Open the live demo

Company objects and relationships supported by available evidence or explicitly recorded company state. The public tour uses a sample workspace.

Select an object or relationship to inspect its available context and provenance. A relationship is not proof of causation.

Available actions depend on the object and your permissions. Recorded assertions and their evidence are distinct from source observations.

Coverage depends on connected sources, validated mappings and available relationships. Missing evidence must not be filled with invented links.