Contacts and relationships

The tenant-owned system of record for government, partner, industry, and internal stakeholders, their engagement history, influence, and pursuit coverage.

Relationship record

Domain	Behavior
`Contact`	Identity, organization, agency, office, program, channels, stakeholder role, relationship owner, tags, watchlist state, and source provenance.
`Interaction`	Emails, meetings, calls, capability briefings, industry days, conferences, notes, and follow-ups with attendees, decisions, actions, risks, outcomes, and dates.
`Stakeholder link`	Connects a person to an opportunity, program, contract, document, meeting, agency, or partner and records decision-maker and influencer status.
`Relationship action`	Tracks outreach, meetings, call plans, follow-ups, meeting briefs, and research with owner, due date, priority, status, and response state.
`Archive`	Removes a contact and its open work from live metrics, coverage, search, and calendar views while retaining historical records and audit evidence.

Scores and coverage

Relationship strength is a bounded 0-100 score derived from interaction frequency, recency, engagement depth, continuity, linked entities, and recorded responses. The bands are Cold (0-25), Developing (26-50), Established (51-75), and Strategic (76-100). Influence is separate: stakeholder role, decision authority, influence flags, linked-entity breadth, and watchlist priority determine who matters even when the relationship is weak.

Opportunity and program maps evaluate recorded coverage for program ownership, contracting, technical evaluation, small-business advocacy, and executive sponsorship. Missing classes produce evidence-based recommendations; WinLayer never invents an unnamed stakeholder.

Connected workflows

Surface	Connection
`Global Search`	Managed contacts, interaction subjects, meeting notes, decisions, actions, risks, and stakeholder links are tenant-searchable.
`Calendar`	Open relationship actions with due dates appear beside capture tasks, workflow milestones, solicitations, and predicted procurement events.
`Signal Intelligence`	SAM.gov contacts remain provenance-backed discovered leads and can be imported into the managed workspace without losing their source reference.
`Relationship Advisor`	Answers common relationship questions deterministically and returns the contact, agency, opportunity, program, or interaction evidence used.

Permissions and concurrency

Control	Behavior
`Read`	All authenticated workspace roles can read managed relationships, history, coverage, and advisor answers.
`Write`	Owner, Admin, Growth Leader, and Business Development can manage contacts, interactions, links, and actions. Viewer receives a read-only workspace and API 403 on mutation.
`Version`	Contact updates use an optimistic version. A stale write returns HTTP 409 instead of overwriting another session.
`Isolation`	Every mutable row carries tenant id, every object lookup includes it, and foreign contact or activity ids resolve as not found.
`Audit`	Contact, interaction, link, action, import, and archive lifecycle events record actor and bounded metadata without copying private notes into the audit log.

API

Endpoint	Purpose
`GET /api/v1/contacts`	Returns metrics, managed contacts, agency heat map, coverage gaps, recommendations, members, facets, and discovered leads.
`POST /api/v1/contacts`	Creates a validated tenant-owned contact; PATCH and DELETE update or archive one contact.
`POST /api/v1/contacts/import`	Promotes a provenance-backed discovered federal contact into the managed workspace.
`GET /api/v1/contacts/:id`	Returns one contact with complete interaction, stakeholder-link, and outreach-action history.
`POST /api/v1/contacts/:id/interactions`	Records meeting intelligence; nested PATCH and DELETE correct or remove one interaction.
`POST /api/v1/contacts/:id/links`	Adds a stakeholder association; nested DELETE removes it.
`POST /api/v1/contacts/:id/actions`	Plans outreach; nested PATCH updates lifecycle and response state, and nested DELETE removes it.
`POST /api/v1/contacts/advisor`	Returns a deterministic answer with evidence identifiers and confidence state.

Open the operational surface at /contacts. Organization-level teaming records live in the Partner Workspace.