Economic coordination layer

Map what people can do. Map what they need.

The Business Graph is 3DVR’s direction for turning outreach into useful economic intelligence: build evidence-backed profiles, discover needs and capabilities, connect businesses that can help each other, and learn from the outcome.

Core model

Businesses are more than leads.

Each business can be a customer, supplier, collaborator, referrer, or all four. A useful profile grows over time instead of disappearing after one campaign.

Facts

Identity + capabilities

Public business facts, services, skills, equipment, infrastructure, locations, and contact paths—with sources.

Needs

Observed + inferred

Visible problems and cautious hypotheses stay separate. Every inferred need carries evidence and confidence.

Edges

Connections + outcomes

Need → provider, customer → supplier, referral → result. The graph gets better when we learn what actually worked.

Working pipeline

Research becomes reusable intelligence.

01

Discover

Find real businesses and public evidence.
02

Profile

Capture capabilities, needs, evidence, and confidence.
03

Analyze

Need Radar finds repeated patterns across businesses.
04

Match

Compare needs with 3DVR or outside supplier capabilities.
05

Act

Prepare a small useful next step or introduction.
06

Learn

Record replies, corrections, outcomes, and successful matches.
The question changes from “Who can we sell to?” to “What does this business need, and who is best positioned to help?”
Decision rules

Supply, connect, build, or learn.

1

Connect existing capability first

If another business already solves the need well, surface the match rather than rebuilding everything inside 3DVR.

2

Use 3DVR when it fits

If we already have a strong capability, offer the smallest useful intervention instead of a giant proposal.

3

Build from repeated unmet demand

Repeated needs with weak supplier coverage are product signals for reusable services, software, or open-source tools.

4

Learn when evidence is weak

Do not convert speculation into a sales claim. Gather better evidence or ask a simple question first.

Trust model

Useful without becoming a dossier machine.

Evidence stays attached

Facts and need hypotheses retain provenance so someone can inspect why the system believes them.

Private stays private

CRM notes, messages, account data, and anonymous local prospect data do not become a public graph by default.

Businesses can correct us

The long-term system should let organizations claim, enrich, correct, or remove appropriate public profile data.

Current direction

We already started.

Campaigns now produces structured business intelligence, Lead Vault preserves it, CRM carries it forward, and Need Radar summarizes repeated demand. The next layer is capability matching and outcome learning.

Business profiles ✓ Needs + confidence ✓ Need Radar ✓ CRM propagation ✓ Capability matching → Durable graph edges → Outcome learning → Business claim/correction →