---
title: "Keep the reasoning with the research."
description: "Organize private-market research with questions, lists and evidence. Keep Intelligence coverage separate from Growth OS CRM and workflow capabilities."
canonical: "https://altss.com/intelligence/workspaces"
last-updated: "2026-11-17"
---

# Keep the reasoning with the research.

Intelligence workspaces give a team a place to organize research within its selected coverage and keep the question behind a list in view.

Last modified: 2026-11-17

## The list should survive its author's handoff

A list can lose its meaning when it leaves the person who built it. An investor may have been selected for a historical commitment, a company for a particular business activity, or a person for a disclosed role. The next researcher needs the rationale and the open question as well as the name.

Use Altss research views and working lists to organize the organizations relevant to a defined question. Review the underlying records and available evidence before turning the selection into a decision. Keep your own analysis distinct from the facts supporting it.

## A working brief for the next researcher

Illustrative research organization. This is a suggested research method, not a claim that every row is a dedicated software field.

| Keep with the research | Example | Why it matters |
| --- | --- | --- |
| Question and scope | Find potential partners among industrial-technology companies in a defined geography | Makes inclusion and exclusion decisions understandable. |
| Selection rationale | The example company describes a relevant product line | Separates evidence-based relevance from a name match. |
| Source and open question | Product evidence found; current partnership appetite unknown | Prevents a research gap from becoming an assumed fact. |
| Next research step | Review the company record and relevant leadership before a discussion | Gives the next person a concrete, bounded task. |


## Choose the environment for the work

### Research in Intelligence

Search, filter and investigate the coverage your plan includes. Use research questions and lists to focus attention on the organizations and people that matter.

### Coordinate in Growth OS

Add native CRM, pipelines, relationship context and customer-controlled workflows when research becomes ongoing relationship work. The Growth OS package includes its matching Intelligence coverage.

### Connect agents through Console

Use the separate Console catalog for available API and agent capabilities. Its permissions, funding and structured outputs follow its own contract rather than inheriting unrestricted access to an Intelligence workspace.

## Make the handoff explicit

### 1. Name the decision

Give the research a clear purpose. A market map, investor shortlist and meeting brief can use some of the same records but require different evidence.

### 2. Keep the source accessible

Review the evidence attached to the relevant record. A copied conclusion should not become detached from its date or the qualification that makes it accurate.

### 3. Separate research from action

Decide when the work is ready for a relationship workflow. In Growth OS, the team controls outreach and next steps; completing research does not itself authorize sending or sharing.

## Workspace questions

### Does a workspace broaden the data in my plan?

No. The selected package defines the available research coverage. Organizing a list does not add company data to a family-office package or broaden a regional license.

### When should a team choose Growth OS?

Choose Growth OS when the team needs native CRM, pipelines, relationship context and customer-controlled workflows alongside matching Intelligence coverage. Research-only teams can evaluate Intelligence on its own.

### Can multiple people use one named-user account?

Published plans use named-user access. Team size and additional-user eligibility follow the current plan terms. Discuss organizational requirements through Enterprise rather than sharing an individual account.

### Can I export Altss research into another database?

Standard subscriptions provide in-platform intelligence rather than a bulk data-export license. Customers can export their own data. Separate delivery or agent requirements must follow the scope and permissions of the relevant product.

## Plan the next stage

- [Research people and roles](https://altss.com/intelligence/people)
- [Relationship Intelligence](https://altss.com/intelligence/relationships)
- [Scope an enterprise deployment](https://altss.com/enterprise)
- [Explore the platform](https://altss.com/platform)

## Inspect the intelligence behind your decision

- [Data coverage and available fields](https://altss.com/coverage)
- [Research methodology and provenance](https://altss.com/methodology)
- [Current packages and pricing](https://altss.com/pricing)
- [Explore all Intelligence capabilities](https://altss.com/intelligence)

[Book a demo](https://altss.com/book-demo?product=full-market&useCase=RESEARCH&source=%2Fintelligence%2Fworkspaces)

[Compare Intelligence plans](https://altss.com/pricing#intelligence)

## Bring a real research question.

Review the coverage, relevant fields and evidence your team needs before choosing its package.

[Book a demo](https://altss.com/book-demo?product=full-market&useCase=RESEARCH&source=%2Fintelligence%2Fworkspaces)

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

Canonical URL: https://altss.com/intelligence/workspaces

