> 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/origination-and-deal-flow.md).

# Origination and Deal Flow

Origination and deal flow is the standing venture sourcing workflow in the VC pack. Depending on pack version and activation state, it may appear as a dedicated origination setup or as part of a pack-backed deal pipeline setup. It configures source coverage, credential readiness, review policy, promotion thresholds, and recurring sourcing work before the pipeline is enabled.

Origination is not a Deal Room. It is the system that finds, enriches, deduplicates, scores, reviews, and promotes candidates into Deal Rooms when they are ready.

## What An Origination Pipeline Tracks

An origination project can track:

* Pipeline name and owner
* Source registry and source readiness
* Review policy and excluded-source policy
* Last run date and status
* Source health and paid-source spend status
* Candidate backlog, new candidate count, and promotion-ready count
* Latest run receipts, candidate batches, enrichment reports, scoring reports, digests, outreach queues, and promotion packages

The source registry is important. It should preserve the source family, source details, freshness, relationship path, evidence quality, dedupe state, and promotion rationale for candidates.

## Setup Flow

An origination setup commonly includes:

1. Choose the sourcing route.
2. Review source readiness, actor or URL scope, budget policy, and read-preview boundaries.
3. Review variables for thesis, source policy, budget, and review thresholds.
4. Review optional sourcing schedules.
5. Enable only the schedules that have been explicitly approved.

Setup does not create Deal Rooms by itself. Deal Room creation happens later through a reviewed promotion task.

## Core Origination Tasks

The pack includes tasks for:

* Configuring the origination pipeline
* Running the sourcing pipeline
* Discovering candidates from approved source surfaces
* Enriching, deduplicating, and scoring candidates
* Reviewing relationship context and portfolio overlap
* Screening active sourcing candidates
* Preparing sourcing digests and outreach draft queues
* Auditing source errors and paid-source spend
* Preparing sourcing IC summaries
* Promoting candidates to Deal Rooms

## Review Gates

Human review is part of the operating model. Do not create Deal Rooms, mutate CRM records, contact founders, or enable recurring schedules from origination work without explicit approval.

Useful approval moments include:

* Source scope approval before discovery starts
* Candidate batch review before enrichment or scoring becomes operational input
* Outreach approval before contacting founders
* Promotion approval before creating or updating a VC Deal Room
* Spend review before enabling paid-source schedules

## Promotion To Deal Room

When a candidate is ready, the promotion package should explain why the company belongs in a Deal Room. It should include the thesis rationale, source path, screening result, evidence quality, key risks, relationship context, and recommended Deal Room posture.

After approval, create or update the VC Deal Room and carry the source trail forward so the opportunity team can see how the candidate entered the pipeline.


---

# 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/origination-and-deal-flow.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.