CRM systems
Salesforce + HubSpot
Planned account, contact, plan, opportunity and activity mapping.
PlannedIntegrations + API roadmap
Your workspace, today.
Connections, next.
Plan intelligence and CRM work together in 5500RADAR now. Connections to external systems are on the roadmap.
Connection status at a glance
Current pre-launch product
One plan workspace.
Public filing intelligence, available financial statements and plan-aware CRM activity.
Controlled access by request.Planned connections
Salesforce · HubSpot · DocuSign · PandaDoc · APIs · webhooks
These external connections are not available today.Evidence and action.
Already in one record.
The native workspace keeps the filed source alongside plan history and your team’s next step.
Public source
DOL / EBSA filings
Form 5500 history, schedules and available audited financial statements.
Current pre-launch product
5500RADAR workspace
Plan and sponsor records, provider history, opportunities and team activity.
Planned
External systems
Future CRM, document and developer connections that preserve the source context.
Public DOL / EBSA data is a source, not a vendor partnership. 5500RADAR is not affiliated with or endorsed by the Department of Labor.
Where connections
go next.
Named products describe intended interoperability. Release dates and compatibility are not promised.
Document workflow
DocuSign + PandaDoc
Planned proposal, engagement-letter and document-status handoffs.
PlannedDeveloper platform
Public APIs + webhooks
Planned access for approved CRM, data and internal workflow use cases.
PlannedPublic-company context
SEC 11-K document linking
Direct SEC document context is being developed and is not available in the product today.
In developmentCompany context
Company news + acquisition signals
Planned company-event context alongside filing and provider history.
PlannedWhat the status labels mean
- Available now
- Usable in the current pre-launch product, with controlled access by request.
- In development
- Active product work that is not yet available. Scope and timing may change.
- Planned
- Direction under consideration or design, without a promised release date or compatibility.
Planned developer platform
Keep the source
with the data.
The planned API is being specified around stable plan objects, explicit permissions and source lineage. Evidence responses are intended to retain the filing year, document and supporting coordinate.
Future access is intended to be tenant-scoped, with filed facts, product derivations and user-recorded activity distinguished. APIs and webhooks are not currently available.
Discuss an integration use caseWhere does your
plan record need to go?
Tell us which CRM, document or internal workflow you use and which source-linked fields matter most.