> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/venture-capital/vc-workspace-setup.md).

# VC Workspace Setup

Set up the VC pack before using it for live deal flow. The setup work makes the workspace-specific choices explicit: which project setups are active, which integrations are authorized, which variables define the fund's strategy, and which recurring work is allowed to run.

**Location:** Administration -> Project Types

This setup path is for Admins and Owners configuring VC workflows for the workspace. Members usually start from the VC projects, deal rooms, files, and tasks that this setup makes available.

## Activate The VC Project Setups

Use **Project Types** to review the VC source templates and activate the setups your workspace needs.

| Setup area                     | What to check before use                                                                                                   |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
| **Origination and deal flow**  | Source strategy, approved sourcing systems, review policy, budget controls, and recurring schedule policy.                 |
| **Deal pipeline or deal room** | Required company fields, source system, CRM import path, deal-room lifecycle, collaborator model, and sync-preview policy. |

Source templates are pack-supplied. If your firm needs a different lifecycle, field model, task set, or integration policy, create or fork a workspace-owned setup instead of changing the source template directly.

## Review Workspace Variables

The VC pack uses workspace variables so tasks can apply the firm's operating context consistently.

Common variables include:

* Fund thesis and thesis areas
* Target stage, geography, sector, and check-size guidance
* Source policy and excluded-source rules
* Review thresholds and promotion criteria
* Meeting, IC, diligence, and reporting cadence
* Confidentiality expectations

Keep variables specific enough to guide work, but do not treat them as a substitute for deal-specific judgment. Opportunity facts still belong in the project, task, or file context where they can be reviewed.

## Connect Recommended Integrations

The pack can recommend integrations based on the selected VC workflow.

| Integration area                          | Typical use                                                                              |
| ----------------------------------------- | ---------------------------------------------------------------------------------------- |
| **CRM and relationship systems**          | Deal source records, relationship context, pipeline stages, and CRM hygiene review.      |
| **File and document systems**             | Founder materials, pitch decks, data rooms, diligence files, and generated outputs.      |
| **Company intelligence and web research** | Company enrichment, market context, source material, and public research.                |
| **Origination sources**                   | Approved source discovery, source previews, candidate batches, and source-health review. |
| **Communication systems**                 | Slack context, handoff notifications, meeting records, and collaboration signals.        |

Selecting an integration records intent. A user or workspace still needs to authorize the connection before Alludium can read from it or propose writes.

## Configure Schedules Carefully

VC project setups can include optional recurring schedules. For example, an origination pipeline can have schedules for core sourcing, source-specific discovery, review and engagement prep, and spend controls.

Schedules should start disabled unless a user explicitly approves them. Before enabling a schedule, confirm:

* The source scope is approved.
* Required credentials are authorized.
* Spend and rate-limit controls are understood.
* The task output has a clear review owner.
* The workspace knows what external systems the task may read from or propose writes to.

## Create The First Projects

Use the origination or deal-flow setup area when you want to operate a standing sourcing motion. Use the deal pipeline or deal-room setup area when you already have a specific opportunity to evaluate.

When a candidate comes from origination, promote it into a Deal Room only after the promotion package has been reviewed. When a partner creates a Deal Room directly, capture the source path, source owner, company name, source material, and current decision context as early as possible.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/venture-capital/vc-workspace-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.