Answers that keep the evidence clear.

Capital Almanac is a market-intelligence research platform for working across companies, markets, investors, funds, deals and source documents from connected context. It is designed to help professionals move from a question to evidence without losing the source trail behind important research facts.

No. A field should remain unavailable when a trustworthy source does not support it, especially for sensitive information such as valuation, ownership, deal terms or performance. Missing information should never be silently converted into zero or replaced with a plausible-looking estimate.

Capital Almanac is designed to retain source provenance such as provider, document, reporting period, retrieval context and evidence anchors where the source supports them. The exact evidence available depends on the record, provider and data rights attached to the workspace.

No. Search, profiles, comparisons and AI-assisted research are intended to make source material easier to discover and work with. Material conclusions should still be checked against the underlying filing, document or licensed record when the decision requires it.

No. Market observations may be real time, delayed, end of day or unavailable depending on the provider, exchange rights and product configuration. Capital Almanac should label freshness accurately rather than presenting every current observation as live.

Private-company information can be incomplete because the company is not required to disclose the field, a provider does not cover it or Capital Almanac does not have a trustworthy source for the value. In those cases, the correct product behavior is to show that the information is unavailable rather than infer it.

Not necessarily. Coverage can vary by provider, geography, exchange rights and the commercial scope agreed for a customer. Teams should confirm the markets, fields and source types required for their workflow during the sales and implementation process.

Review the reporting period, freshness and source context before treating a change as economically meaningful. A restatement, provider normalization change or newly available filing can affect a displayed value without representing a new business event.

Capital AI is intended to help users ask questions across connected company, market, transaction and document context and reach relevant evidence faster. It should support the research process, not turn an unsupported statement into a fact simply because it was generated fluently.

No. AI-assisted output is a research aid and does not replace professional judgment, diligence or the original sources behind a material conclusion. Users remain responsible for reviewing evidence and deciding how it applies to their work.

The appropriate response is to communicate that the available sources do not support a reliable answer or to narrow the claim to what can be substantiated. The system should not fill evidence gaps with fabricated company facts, market events or financial metrics.

The product direction includes workspaces, saved searches, lists, monitoring and shared research objects so teams can carry context between people. The exact collaboration capabilities available in a deployment should be confirmed for that workspace.

Capital Almanac is positioned as a consultative enterprise product rather than a self-service subscription with one universal price. Commercial scope can depend on users, research workflows, required source coverage, integrations and administrative requirements.

Not automatically. API availability depends on the documented endpoint, the caller's permissions and the source coverage licensed for that use case. Applications should handle missing or unavailable fields explicitly rather than inventing defaults downstream.

Enterprise identity capabilities should be confirmed for the specific customer configuration before rollout. Public marketing language should not be treated as proof that every identity or provisioning control is enabled in every environment.

Use the enterprise sales and implementation process for questions that depend on contractual terms, deployment architecture, data rights or a particular control. That allows the answer to be tied to the configuration being evaluated rather than a generic public summary.