> 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/readme.md).

# Startup Manual

OCV's Startup Manual is for founders building and growing open core companies. It includes strategic guidance from formation through growth. Our mission is to help more people become founders, and our public handbook lets anyone learn from and benefit from our frameworks.

## 90 Day Ramp-Up

Use this plan to navigate your first 90 days. Each phase focuses on the decisions that unlock the next stage.

## First 30 Days

In your first 30 days, you will:

1. [Align the company to an open core model](#open-core-alignment)
2. [Set your vision and start talking to users](#vision-and-icp-hypothesis)
3. [Complete your first launch](#first-launch)

### Open core alignment

The OSS project is the company's foundation. Your relationship with the OSS project and community, and how you approach distribution, integration, and community management, will have a lasting impact. Setting up the open core foundation immediately will help you grow faster.

Start with the technical details: How will you integrate the open source and proprietary code? What visibility do you currently have into usage?

Plan to combine code into [a single repo with two licenses](https://handbook.opencoreventures.com/startup-manual/fundamentals/licensing-and-distribution.md#distribution-guidelines). If that's not possible, [explore recommended alternative paths](https://handbook.opencoreventures.com/startup-manual/fundamentals/licensing-and-distribution.md#building-on-an-oss-repo-when-youre-not-a-maintainer). A single distribution with two licenses is the path of least resistance for upgrades and a better user experience.

Add [default-on telemetry](https://handbook.opencoreventures.com/startup-manual/fundamentals/licensing-and-distribution.md#telemetry-is-default-on) if you haven't already. If this isn't possible or you're not sure how to implement it, bring it up in office hours immediately. Blindness to OSS usage will hinder your growth.

[Open core](https://handbook.opencoreventures.com/how-we-work/open-core.md) products must include monetizable proprietary code; otherwise, it's not open core. Likewise, keep contributing to OSS; [maintaining and improving the open source core is a key tenet](https://handbook.opencoreventures.com/startup-manual/fundamentals/oss-community.md#value-creation-over-reputation-management) of the open core model. Review the buyer-base open core pricing model closely. A solid understanding of this pricing model will save time when you start building new features and decide whether to make them open source or make them proprietary. Read the following short articles from Sid for additional help:

1. [Open core split should be based on features, not code base](https://opencoreventures.com/insights/open-core-split-should-be-based-on-features-not-on-code-base/)
2. [Buyer-based open core: A pricing model](https://opencoreventures.com/insights/a-standard-pricing-model-for-open-core/)

Do a quick audit of the existing [OSS community](https://handbook.opencoreventures.com/startup-manual/fundamentals/oss-community.md). What communication/social channels already exist (i.e., Discord, Slack, X, Reddit), and do you have access to them? If relevant channels don't exist, create them. Whenever possible, avoid creating separate channels for the OSS and the company.

Review open issues and PRs, and [let existing demand guide product development](https://opencoreventures.com/insights/let-demand-steer-early-stage-open-core-product-development/). Stack-rank requests by frequency and build momentum by solving what users ask for most. License and price features based on the most likely user, not who asked for the feature. [Listening to your heaviest users](https://opencoreventures.com/insights/dont-listen-to-the-last-objection) will yield better results than chasing requests from someone who has never used the software.

### Vision and talking to users

Write the first version of your [two-sentence company description](https://handbook.opencoreventures.com/founder-experience/building-blocks#two-sentence-company-description) and the first draft of your hero statement. This will become the [H1/H2 of your website](https://handbook.opencoreventures.com/startup-manual/fundamentals/website.md#turning-your-hero-statement-into-the-h1-and-h2).

Your two-sentence company description should encapsulate your big vision in the simplest terms. It's your elevator pitch—how you would describe what your company does to a friend, neighbor, and investor. Your hero statement is customer-focused. It's the first thing someone sees when they land on your website, and it should quickly communicate the product's value and why someone should care. Treat this first draft as a starting point. You’ll sharpen it once you’ve formed your ICP hypothesis.

Start talking to customers right away, beginning with existing OSS users. Find out who they are, how and why they use the project, what problems it solves for them, what frustrates them, and what they would pay for. Look for people who use the software heavily or in a business context, and ask them for a short conversation. Reach out through your community channels, GitHub, LinkedIn, or wherever your users are most active.

Share insights from these conversations on social media, in blogs, and wherever it makes sense for you to post. This builds an audience early and helps you test whether what you’re hearing resonates at a larger scale.

### First launch

There is no single launch. You will launch many, many times. Your first launch is when you tell the world you've started a new company, why you've started it, and what it will do. How you announce it will depend on who you're trying to reach, but will include a variety of activities (i.e., a blog post and/orvideo, LinkedIn/X announcement, community engagement, network amplification).

To make the most of this announcement, have your [website live](https://handbook.opencoreventures.com/startup-manual/fundamentals/website.md) and set up product and [website analytics](https://handbook.opencoreventures.com/startup-manual/fundamentals/website.md#add-tracking-and-analytics). Do [keyword research](https://handbook.opencoreventures.com/startup-manual/fundamentals/website/seo-and-aeo.md) before writing your website copy, and include an [llm.txt file](https://handbook.opencoreventures.com/startup-manual/fundamentals/website/seo-and-aeo.md#creating-an-llmstxt-file). If you don't have a product ready for sign-ups, give people a way to sign up for future news and announcements.

Update your LinkedIn profile, and ask your network to help amplify the announcement. Ask your network, friends, family, former colleagues, etc., to follow your company's social media pages and start posting to those pages before your launch. People are more inclined to follow you when they see relevant content on your page. [Publishing content often and regularly is the easiest, cost-effective way to start marketing](https://handbook.opencoreventures.com/startup-manual/marketing/content-engine/content-marketing.md) your company and gaining attention and traction. What and where you share depends on who you are trying to reach. The more targeted you can get with topics and distribution, the better.

## First 60 Days

In your first 60 days, you will:

1. [Form and test your first ICP hypothesis](#first-icp-hypothesis)
2. Start your content engine
3. Launch with pricing

### First ICP hypothesis

Use what you learned from your first customer conversations to form an ideal user and/or ideal customer hypothesis. You might come up with a few. Pick one to start with and write it as a falsifiable hypothesis, so you’ll know clearly whether it holds up.

Learn everything you can about your ICP as quickly as you can: what they care about, what they search for, what gets them promoted, what content they consume, and where they consume it. Find more people who match the profile on LinkedIn or wherever your ICP spends time online, and ask to interview them.

Once you have a working hypothesis, revisit your hero statement. It should speak directly to this audience. Keep sharing what you learn publicly to see what resonates, and refine or replace the hypothesis as the evidence comes in.

## First 90 Days

1. Start your growth engine
2. Launch again


---

# 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/readme.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.
