> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Fundraising signals

> Qualify a dated funding event before proposing an account action.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/signal-fundraising.md)

> [!NOTE]
>
> Review a funding observation and choose a supported account action without
> inferring purchase intent.

A funding announcement is evidence of a financing event. It is not proof of
available budget, purchase intent, or a particular team's priorities. This page
owns the event-specific evidence and decision boundary. The shared execution
and account-contact safeguards live in [signal playbooks](https://deepline.com/docs/plays/signal-playbooks.md).

## Required evidence

* A public announcement or structured source URL and its observed date.
* The round details that source actually supports.
* The account's ICP-fit and existing customer or opportunity state.
* A current, relevant initiative or a second verified signal when one exists.
* The account owner and proposed next action.

Do not infer an active project from round type, amount, or investor alone.

## Choose the next action

| Evidence result | Decision |
| - | - |
| ICP-fit account with a current, relevant initiative | Draft a reviewed account-research or outreach angle. |
| ICP-fit account with only the financing event | Keep as a research candidate. seek a second signal. |
| Existing customer | Route the evidence to the account owner for an expansion decision. |
| Missing date, weak source, or non-ICP company | Retain the evidence or take no action. |

## Prepare the review file

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Review target-accounts.csv for recent public funding events.
For each candidate, return the announcement URL, observed date, supported round
details, ICP-fit result, account status, any second verified signal, and one
proposed action.
```

## What is the best timing window for post-funding outreach?

Use this table to define a test. The statements are hypotheses, not facts about
the company.

| Window | Question to test | Action |
| - | - | - |
| **Week 1** | Is the company ready to discuss the relevant problem? | Verify fit before you contact the company. |
| **Week 2-3** | Has an owner or initiative become public? | Use only verified context in the message. |
| **Week 4-8** | Is the event still relevant to an active initiative? | Keep or lower priority based on evidence. |
| **After week 8** | Does another current signal support outreach? | Require a current signal before contacting. |

Use these windows as planning examples. Measure response and conversion rates
for your market. Change the windows when your results support a different rule.

## Keep the message factual

Use only public, verified funding details. The message should connect an
observed event to a specific, relevant problem. It should not claim that the
round created budget or a project. For combined evidence, follow the
[signal-combination policy](https://deepline.com/docs/plays/signal-deal-risk.md) and make one reviewed
account decision rather than sending separate trigger messages.

***

**Related:** [Champion Tracking](https://deepline.com/docs/plays/signal-champion-tracking.md) | [Hiring Signals](https://deepline.com/docs/plays/signal-hiring.md) | [Company News & Social](https://deepline.com/docs/plays/signal-company-news.md) | [Deal Risk & Signal Combos](https://deepline.com/docs/plays/signal-deal-risk.md)

## Verify this task

Confirm company identity, event date, source, and the distinction between reported funding and the proposed outreach reason.

Ask your agent to explain a failed check before repeating work or expanding the scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.