WinLayer Docs
Product documentation · Beta behavior. A documented path is not production acceptance; availability still depends on source health, workspace plan, provider setup, and deployed evidence.

Company profile

The tenant-owned source of company identity, market eligibility, capability, growth, and delivery context used throughout WinLayer intelligence.

Profile domains

DomainUsed for
IdentityCompany name, UEI, CAGE, DUNS, website, headquarters, business size, and description anchor entity and award matching.
EligibilityBusiness classifications and certifications determine set-aside fit and partner gaps.
CapabilitiesCompetencies, services, products, technology, mission areas, and differentiators ground recommendations and generated artifacts.
MarketsNAICS, PSC, agencies, vehicles, and geography personalize opportunity qualification, early signals, and global search.
PerformanceAgency, program, contract value, vehicle, mission area, and rating evidence support fit and teaming analysis.
StrategyCompetitors, partners, revenue and pipeline goals, win-rate targets, contract-size range, and growth priorities shape portfolio recommendations.
ResourcesCapture, proposal, subject-matter, business-development, consultant, and weekly capacity inputs constrain executable plans.
NotificationsChannels, cadence, quiet hours, minimum priority, and intelligence categories define the tenant delivery policy.

Canonical matching inputs

Detailed profile sections are normalized into canonical NAICS, PSC, agency, vehicle, set-aside, and capability arrays. Existing Radar scoring, PWin, briefs, agents, partner matching, and search therefore consume one stable contract while retaining the richer source context. Excluded agencies are removed from positive targeting and receive a search-ranking penalty.

Completion and personalization

WinLayer scores ten profile sections and reports the missing domains without treating completeness as a model confidence claim. Personalization returns the company archetype, current signal counts, priority themes, and concrete gaps. The configuration center at /profile refreshes both after each save.

Concurrency and permissions

ControlBehavior
ReadAny authenticated workspace member can read the tenant profile through the API; role-shaped navigation limits the editor to relevant operators.
WriteOwner, Admin, and Growth Leader can update. Viewer and Business Development roles cannot mutate the tenant profile.
VersionEvery update supplies profileVersion. A stale version returns HTTP 409 instead of overwriting newer work.
AuditEach save records the actor, resource, changed sections, resulting version, and completeness score without copying profile bodies into audit metadata.
IsolationThe profile has one tenant-unique row, every lookup includes tenant id, and cross-tenant records are never accepted from request input.

API

EndpointPurpose
GET /api/v1/profileReturns the normalized profile, effective configuration, completion, and personalization.
GET /api/v1/profile/insightsReturns completion and personalization without the full profile body.
PUT /api/v1/profileApplies a bounded partial update with validation, optimistic concurrency, canonical derivation, and audit.
GET /api/v1/profile/industriesReturns curated industry baselines used by onboarding and the configuration center.