> For the complete documentation index, see [llms.txt](https://handbook.opencoreventures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.opencoreventures.com/startup-manual/gtm/growth.md).

# Growth

Growth is the single most important factor in determining whether, how quickly, and on what terms companies can fundraise.

OCV companies have \~9-12 months to show meaningful traction. If a company struggles to gain traction, we may wind it down. We measure growth through usage and revenue metrics. Investors want to see an obvious demand for a commercial product. For an enterprise company, meaningful growth could be a handful of logos at a few hundred thousand in [annual recurring revenue (ARR)](https://handbook.opencoreventures.com/startup-manual/gtm/growth/growth-metrics.md#annual-recurring-revenue-arr).

Early-stage startups operate on a weekly growth cadence: week-over-week (WoW) growth goals and product deliverables. That’s why [OCV meets with Pre-Seed companies weekly](https://handbook.opencoreventures.com/founder-experience/office-hours.md).

The [most successful founders drive growth efforts in the early stages](https://handbook.opencoreventures.com/founder-experience/founder-mode.md). Investors will want to know you've figured out growth and deeply understand your growth channels. Understanding your growth channels means you know where to spend to grow more.

## Start with what's unscalable&#x20;

Early growth and scalable growth come from different places.

[**Unscalable behaviors get your first users**](https://handbook.opencoreventures.com/how-we-work/first-principles#unscalable-behaviors-drive-traction)**.** Your personal network, direct outreach to your existing users, direct outreach to potential users, hands-on onboarding, and showing up in the communities where your users spend time. These tactics don't scale, but they're low risk, they work on a small base, and they put you in direct contact with users while you're still finding product-market fit.&#x20;

**Scalable channels sustain growth.** A small number of channels can scale a company because they create feedback loops: word of mouth and product-led adoption, search and AI discovery, paid acquisition, and sales. Revenue funds more acquisition, or new users bring in more users. These channels take months to build, so start testing them while unscalable tactics carry your early growth.

## Measuring impact

Channel impact moves through a chain. Each link is a checkpoint, and a channel is only working when it reaches the end of the chain.

1. **Activity:** what you put in (posts published, emails sent, dollars spent, talks given).
2. **Reach:** traffic or attention from that specific source (visits from LinkedIn, referrals from GitHub, impressions in search).
3. **On-site behavior:** what those visitors do once they arrive. This tells you whether they're the right audience.
4. **Conversion:** signups, installs, and [activation](https://handbook.opencoreventures.com/startup-manual/gtm/growth/growth-goals.md#user-activation) from that source.
5. **Retention and revenue:** whether users from that channel stick around and pay.

{% hint style="info" %}
**Reach and traffic are leading indicators, not results.**

A channel that grows traffic without growing WAU or revenue isn't working yet. It either reaches the wrong audience or sends the right audience to the wrong place.&#x20;

**Example:** A founder invests heavily in posting on LinkedIn. The first thing they should see is growth in website traffic from LinkedIn. Next, they look at what those visitors do on the site. If LinkedIn visitors read the docs, view the pricing page, and sign up, the channel is reaching the right audience. If they land on a blog post and leave within seconds, the posts are earning attention from people who aren't potential users, or they're sending people to a page that doesn't move them forward.&#x20;
{% endhint %}

### Reading on-site behavior

Traffic tells you a channel is reaching people. On-site behavior tells you whether they're the right people. Compare these signals across sources to see which channels bring your audience.

| Signal        | Suggests the right audience                                    | Suggests the wrong audience or wrong landing page |
| ------------- | -------------------------------------------------------------- | ------------------------------------------------- |
| Pages visited | Docs, install guide, pricing, product pages                    | A single blog post or the homepage only           |
| Engagement    | Multiple pages per session, meaningful time on site            | Immediate exits, very short sessions              |
| Conversion    | Signups, installs, demo requests at or above your site average | Few or no conversions despite high traffic        |
| Return visits | Visitors come back over the following weeks                    | One-time visits only                              |
| Activation    | Users from this source reach your activation milestone         | Users sign up but never activate                  |

When a channel's behavior looks poor, figure out which problem you have before you abandon it:

1. **Right audience, wrong destination.** Visitors match your user profile but land on a page that doesn't lead anywhere. Fix the landing page or call to action.
2. **Right audience, wrong message.** The content earns clicks on a promise the product doesn't deliver. Align the message with what the product actually does.
3. **Wrong audience.** The channel reaches people who will never use your product. Tighten targeting or move on.

## Set up attribution before you start

You can't evaluate a channel you can't see. Before you invest in any channel, make sure you can trace a user back to where they came from. Attribution enables [cohort retention](https://handbook.opencoreventures.com/startup-manual/gtm/growth/growth-goals.md#wau) and CAC by acquisition channel.

1. **Web analytics by source.** [Set up Google Analytics](https://handbook.opencoreventures.com/startup-manual/fundamentals/website.md#add-tracking-and-analytics) (or an equivalent) and [Google Search Console](https://handbook.opencoreventures.com/startup-manual/fundamentals/website/seo-and-aeo.md#free-keyword-research). Learn to read traffic by source/medium so you can isolate visits from each channel.
2. **UTM parameters on every link you control.** Social posts, newsletters, paid ads, conference slides, and partner links should all carry UTM tags so traffic is attributed correctly.
3. **Connect web traffic to product signups.** Pass the source through to your product analytics so you can see signups, activation, and retention by channel, not just visits.
4. **Ask users directly.** Add a "How did you hear about us?" field to signup or onboarding, and include options for AI assistants and coding agents. Self-reported attribution catches what analytics misses, like word of mouth, AI recommendations, podcasts, and dark social (links shared in DMs and private Slack communities).
5. **Separate human and automated traffic.** AI crawlers and agents now make up a large share of web traffic. Filter bots out of your human traffic numbers so they don't inflate reach, but track agent activity separately (API signups, CLI installs, MCP connections), because for developer products it can be a real acquisition channel.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://handbook.opencoreventures.com/startup-manual/gtm/growth.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
