Core research
Company research, search, Capital AI, watchlists and core research workflows.
Access
Capital Almanac is sold through a consultative enterprise process. We scope access around your research workflows, required data coverage, integrations and administrative needs.
Company research, search, Capital AI, watchlists and core research workflows.
Public-market, private-market, transaction, investor and screening workflows.
Administration, SSO, integrations, API access and enterprise deployment options.
Structure access around teams, roles and research use cases.
Align source and market coverage with the data your organization actually needs.
Scope spreadsheet, API and enterprise integration requirements with our team.
We scope access based on your team, required data coverage and research workflows.
We scope access based on your team, required data coverage and research workflows.
We scope access based on your team, required data coverage and research workflows.
Source context
Capital Almanac keeps source context, reporting periods, freshness and unavailable-data states visible so researchers can see what supports a record or conclusion.
Source provenance
Keep the provider, document and evidence trail close to the supported fact.
Linked evidence
Open filings, calls, announcements and other source documents from the research view.
Freshness metadata
See reporting period and update context instead of treating every record as equally current.
Connected records
Understand how companies, people, investors and transactions relate to one another.
Capital Almanac
Tell us what your team researches, which markets matter and where source visibility or workflow integration would save the most time.
How Capital Almanac handles source material, unsupported information and the path from a research question to a reviewable answer.
Capital Almanac is presented as a consultative enterprise product rather than a self-service plan with one universal price. Scope can depend on research workflows, required data coverage, integrations, team access and administrative requirements.
A rollout can be discussed around the research surfaces and data coverage the team actually needs first. The final package and expansion path should be agreed during the sales process rather than inferred from capabilities that are not part of the customer's configuration.
Data rights and provider coverage can vary, so a commercial package should not be assumed to include every market, private-company field or licensed source. The sales process should confirm the coverage required for the intended research workflow.