CRM systemsRelationship + pipeline
Salesforce + HubSpot
Planned account, contact, plan, opportunity and activity mapping.
Integrations + API roadmap
Plan intelligence,connected.
Bring source-linked Form 5500 evidence into the systems your team already uses, without breaking the trail back to the filing.
Available now
5500RADAR plan record
Current pre-launch product. Access by request.
Available now
Plan-aware CRM workflow
Evidence, opportunity and next action in one product record.
In development
SEC document context
Direct 11-K document linking is not yet available.
Planned
External systems + API
CRM, document, webhook and developer connections.
The plan record is the connection point.
Each handoff should preserve the filing year, source document and derivation that made the information useful.
- Form 5500 filing history
- Available schedules and attachments
- Available audited financial statements
- Structured plan and sponsor record
- Multi-year filing and provider history
- Evidence connected to CRM workflow
- CRM account and opportunity records
- Proposal and signature workflows
- APIs, webhooks and internal systems
Public DOL / EBSA data is a source, not a vendor integration or government partnership. 5500RADAR is not affiliated with or endorsed by the Department of Labor.
Status is part of the promise.
The roadmap uses three terms so a future direction is never mistaken for a feature that can be used today.
- Available now
- Usable in the current pre-launch product. Access remains controlled and is provided by request.
- In development
- Active product work that is not yet available to users. Scope and release timing may change.
- Planned
- Product direction under consideration or design. No release date, connector availability or compatibility is promised.
Connection roadmap
From filed evidence to the systems that act on it.
Named products below identify intended interoperability only. They are not available connections today.
Planned
Document workflowProposal + signature
DocuSign + PandaDoc
Planned proposal, engagement-letter and document-status handoffs.
Developer platformRead + event access
Public APIs + webhooks
Planned programmatic access for approved CRM, data and internal workflow use cases.
Public-company contextAdditional source layer
SEC 11-K document linking
Direct SEC document context is being developed. It is not available in the product today.
Company contextExternal events
Company news + acquisition signals
Planned context for understanding company events alongside filing and provider history.
5500RADAR workflowEvidence + CRM record
Plan-aware CRM workflow
Current pre-launch workflow for carrying source-linked plan intelligence into opportunity and next-action records.
Planned developer platform
An API that keeps the evidence attached.
The planned API is being specified around stable plan objects, explicit permissions and source lineage instead of anonymous rows detached from the filing.
Discuss an integration use case
plansponsorfilingevidenceprovider relationshipopportunity
- Source lineage
- Evidence responses are intended to retain the filing year, document and supporting coordinate.
- Explicit permissions
- External access is intended to be tenant-scoped and limited to approved objects and actions.
- Traceable workflow
- Future write paths should distinguish filed facts, product derivations and user-recorded CRM activity.
- Event delivery
- Planned webhooks would deliver defined changes without requiring every system to poll the entire record.
Tell us where the plan record needs to go.
Share the CRM, document or internal workflow your team uses and the source-linked fields that matter most.