The product is intentionally not one master score. Different instruments answer different questions: who deserves attention, where access exists, whether the network has enough capacity, how relationships are changing, where the network is concentrated, and what evidence supports the next move.
Opportunity intelligence combines objective relevance with relationship access while keeping the two concepts separate. The product explains the portfolio instead of hiding the answer inside one opaque number.
Radar shows the objective-relevant portfolio and an objective-aware reading of what the current portfolio contains. Target context can change the strategic reading without changing the canonical scoring math.
Predictive conclusions carry evidence, timing, unknowns, confidence and history so a recommendation can be inspected rather than treated as a mysterious forecast.
The daily view leads with why a relationship deserves attention and the action the evidence supports now.
Matching a title is not the same as having credible relationship capacity. Runway and Coverage expose absence, concentration and fragility—not just opportunity.
Runway asks the objective's strategic question while preserving one underlying capacity engine. The same network can therefore be read as consulting capacity, career access, capital reach, partnership capacity or another objective without changing the facts.
Relationship Capital examines strategic reach, fragile joins, independent routes, concentration and deterioration risk rather than publishing a vanity balance-sheet number.
Coverage shows whether relationships span seniority, functions and independent routes, or whether apparent access is concentrated in one narrow corner of the organization.
Relationship behavior is directional, historical and uncertain. RelationshipsIQ keeps those distinctions instead of converting everything into engagement points.
Weather is applied only where enough relationship evidence exists to support the claim. A quiet weak connection is not automatically called dormant.
Where message evidence is sufficient, the system can distinguish inbound-heavy, balanced and outbound-heavy interaction direction. Insufficient evidence remains insufficient.
Written recommendations count as advocacy evidence. Endorsements remain skill validation rather than being promoted into sponsorship.
Reciprocity supports relationship-first moves such as reconnecting with context or offering useful help before making a transactional ask.
Some questions are about one person. Others are about a company, several routes, an alumni cluster or a combination of relationships that create useful coverage together.
See company clusters, direct relationships, bridge routes and named-target coverage. A target company can be highlighted for inspection without artificially changing relationship strength.
Rooms bring relationships together around complementary roles and coverage while keeping missing roles, risks and unknowns visible.
Dispersion distinguishes confirmed alumni movement from unverified candidates instead of inferring a departure merely from connection timing.
Reachability reports factual channel availability and provenance. It does not invent a preferred channel, best time or likelihood of response.
Objective context belongs between canonical relationship intelligence and the recommendation—not inside the factual producers themselves.
The interpretation layer resolves the current goal, template provenance and explicit target context, then explains what the existing intelligence means for that workspace. Persona labels alone do not change rankings.
Positions, skills, recommendations and published topics can be read against the active goal while platform limitations and missing signals remain visible.
Observed facts, inferred conclusions and user-verified relationship knowledge are different classes of information. RelationshipsIQ keeps them different and lets user correction outrank inference.
Dates, message direction, current employer, recommendations, positions, skills and other source facts.
Strategic conclusions and relationship interpretations stay traceable and keep uncertainty intact.
Confirm, correct, suppress and add context. Explicit user knowledge outranks the inferred layer.
Ask who could support a consulting objective, where a target company has real coverage, which relationships are cooling, or who should be warmed before an ask. The answer separates evidence, reading, recommendation and uncertainty.
