---
title: "One research foundation. A scope that fits your organization."
description: "Scope Altss Intelligence, Growth OS and separate Console capabilities for your organization. Discuss coverage, named users, workflows, security and contracting."
canonical: "https://altss.com/enterprise"
last-updated: "2026-11-17"
---

# One research foundation. A scope that fits your organization.

Altss Enterprise scopes intelligence coverage, users, workflows and contracting around your organization's research and relationship requirements.

Last modified: 2026-11-17

## Start with what each team needs to accomplish

Investment, research, corporate-development and commercial teams can investigate the same organizations for different reasons. A sourcing team may need ownership context, an institutional-sales team may need relevant people, and an investor-relations team may need allocator research and a pipeline. The deployment should reflect those jobs and the information each team is entitled to use.

Scoped organizational deployment, configuration and contracting. Custom terms do not automatically grant data-feed, export or resale rights.

## Three products, distinct responsibilities

### Altss Intelligence

The intelligence platform for understanding companies, investors, people, capital and relationships across global private markets. Each package defines the research coverage available to its users.

### Altss Growth OS

Altss Growth OS combines the matching Intelligence coverage with native CRM, pipelines, relationship context and customer-controlled workflows. Previously Fundraising OS, it retains the existing fundraising functionality. Switching supported objectives does not require another subscription.

### Altss Console

A separate capability catalog for machine-accessible research and agent execution. Evaluate the available operations, authentication, permissions and usage billing against the integration your organization needs.

## Define the deployment before the agreement

A useful enterprise brief makes the research scope and delivery requirements concrete. These are scoping questions, not promises of custom functionality.

| Requirement | What to specify | What gets confirmed |
| --- | --- | --- |
| Research coverage | Family offices, institutional investors, or full company and market research | The package or contracted scope each team requires |
| People and teams | Named users, departments and permitted working relationships | User access and the agreed organizational deployment |
| Workflow | Research only, or native CRM, pipelines and customer-controlled follow-up | The appropriate Intelligence or Growth OS configuration |
| Agent integration | The available Console capabilities, input types and intended result use | Supported operations, credentials, permissions and funding requirements |
| Procurement | Security review, purchasing process and contracting requirements | The applicable agreement and activation process |


## From requirement to an agreed scope

### 1. Bring representative questions

Show the companies, investor categories or research tasks that matter. Explain what the team needs to decide and which fields or evidence the decision depends on.

### 2. Review the fit

Compare the requirement with available coverage and supported workflows. Inspect source context and any gaps. Discuss security and permitted result use alongside the product review.

### 3. Confirm the configuration

Agree named-user access, product scope and commercial terms through the existing contracting process. Any separately scoped integration or delivery requires an explicit agreement; a discussion does not activate it.

## Keep information rights aligned with the work

Altss combines independently collected public-source business information, Altss-developed research and derived analysis, and commercially licensed contact enrichment. Public facts carry source references, collection dates and relevant evidence; known source restrictions remain applicable. Licensed enrichment follows recorded provider or dataset permissions for the intended use and delivery. Collection method, factual verification, privacy duties and redistribution rights are separate questions.

Enterprise contracting can address organizational requirements, but it does not automatically grant bulk data-feed, export, resale or unrestricted graph-replication rights. State the intended use and delivery model early so the agreement and enabled capabilities match the requirement.

Customer-owned notes and permitted relationship context are distinct from public business intelligence. Review the relevant security information and privacy terms for the proposed deployment, including how access and intended use are controlled.

## Prepare for your review

- [Data coverage and field definitions](https://altss.com/coverage)
- [Data quality and research methodology](https://altss.com/methodology)
- [Security](https://altss.com/security)
- [Trust and subprocessors](https://altss.com/trust)
- [Privacy policy](https://altss.com/privacy-policy)
- [Console connection requirements](https://console.altss.com/connect)

## Enterprise questions

### Do we need Enterprise if the standard plans fit?

Not necessarily. Start with the published Intelligence and Growth OS packages. Enterprise is the route for scoped organizational deployment, configuration and contracting requirements that need discussion.

### Does Enterprise include every dataset or capability?

No. Access follows the agreed coverage, users, permitted uses and enabled capabilities. A custom agreement does not imply that every field, integration or Console action is included.

### Can one deployment support research, deal sourcing and commercial teams?

Discuss each team's objective and coverage needs in the same scoping process. Full Market supports company, ownership and transaction research; Growth OS adds native CRM and supported customer-controlled workflows. Organizational access is defined in the agreement.

### Is Console billing included in an Intelligence subscription?

Console is a separate product with its own approved capability and billing configuration. Confirm the relevant permissions and usage terms for the integration. Standard Intelligence access does not grant unrestricted machine access.

### Does a demo request create a contract or activate access?

No. The demo and Order Form request paths begin review. Scope, agreement, payment and activation follow the applicable commercial process.

[Discuss enterprise requirements](https://altss.com/book-demo?product=enterprise&useCase=ENTERPRISE&source=%2Fenterprise)

[Review standard plans](https://altss.com/pricing)

## Bring the teams, the questions and the constraints.

Altss can review the coverage and workflow fit with you, then define a concrete organizational scope.

[Discuss enterprise requirements](https://altss.com/book-demo?product=enterprise&useCase=ENTERPRISE&source=%2Fenterprise)

[Buy with an Order Form](https://altss.com/subscribe?product=enterprise&useCase=ENTERPRISE&source=%2Fenterprise)

Canonical URL: https://altss.com/enterprise

