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

# Website

Your website is never finished. It will change many times as your product, customers, and positioning evolve. Your first version should go live within 30 days, and it’s fine for it to be forward-looking: a clear statement of the problem you solve and where you’re headed. Add a pricing page as soon as possible. Pricing signals that you’re a real business, sets buyer expectations, and forces you to get specific about who you serve and what they pay for.

The same principles apply to every version.

1. **Pick one clear message.** Choose a single lane and cut everything that competes with it. That might mean narrowing your homepage to one use case, committing to one product line in a crowded market, or dropping features that blur the core story.
2. **Put your strongest content at the top.** Whatever your pitch is, the headline above the fold should say it plainly, backed by specific, believable claims rather than inflated ones. Put bold positioning at the top of the page, not buried below it. If you have data, case studies, etc., build dedicated pages and drive traffic to them.
3. **Prove claims with real evidence.** Back every claim with specifics a skeptical buyer would believe. As customers arrive, replace promises with proof: real stories, real photos, and real results.

Keep the site in step with the product as it exists today, ensure the pricing page reflects current capabilities, and make sure the basics work: pages load fast, links work, sign-up flow works.

OCV will transfer any [existing domain names](https://handbook.opencoreventures.com/ocv-employees/vc-ops/company-formation-process/company-name#block-477e71191d3e42f58f5eb59046b47ec4) to the founder.

## One website for the project and the company <a href="#block-1d2feb7b074d800eb1e6f2a379e13fe1" id="block-1d2feb7b074d800eb1e6f2a379e13fe1"></a>

If a company can keep [the original project name](https://handbook.opencoreventures.com/ocv-employees/vc-ops/company-formation-process/company-name), it’s best to keep the open source project and commercial company websites together rather than separate, if you can. Two different websites can confuse users and require double the maintenance effort. Much of that effort will be duplicative.

Don’t deprecate the existing open source project website. Instead, make the commercial company website a superset of the two. The commercial site should be the go-to destination for all communication and information. Eventually, the two websites may evolve into one, but that can happen over time. Doing everything all at once may alarm the community. A gradual process works better as the community gains trust in the commercial entity. People are much more receptive to change as long as the commercial company consistently does the right thing.

If combining the open source and company website isn’t an option, create a new website and include a link to the open source project repo in the website footer.

## Lead with your hero statement <a href="#turning-your-hero-statement-into-the-h1-and-h2" id="turning-your-hero-statement-into-the-h1-and-h2"></a>

Put your clearest pitch at the top of the homepage. Say what the product does and who it helps in plain language. Visitors should understand both within a few seconds.

Avoid buzzwords and vague promises. Use the words your users use, make one honest claim, and support it with proof below.

## Choose a primary CTA&#x20;

Give visitors one path into your product: one button, one label, and route other options to the pages where they belong.&#x20;

Open core companies can usually offer several entry points at once: the open source project, a hosted free tier, sometimes a playground, plus a license or a demo. Each one serves someone, so founders tend to put them all on the homepage. The result is a visitor who has to choose before they understand the product, and conversions split across buttons so you can’t tell what’s working.

Pick one primary button and use the same label on every page. If people can both download and sign up, don’t show two buttons side by side. Combine them into one flow behind one button, such as “Get started,” that asks for sign-up first and then hands over the download or install command. “Get started” works when it leads into one clear flow. If something more specific fits, like “Deploy in 5 minutes,” use it, but keep it identical everywhere.

The secondary text link is for a second option, usually for a different audience. Give it clearly less visual weight than the primary button.

## Add tracking and analytics&#x20;

Add analytics to your site before launch, so you have a baseline from day one.

Google Analytics is the default for most teams: it’s free, widely supported, and integrates with Google Search Console and ad platforms. If you’d rather avoid cookies and consent banners, or your audience is privacy-conscious, Plausible is a lightweight, open source alternative. Either is fine.

Start tracking the basics:

* **Traffic and sources:** how many people visit, and where they come from (search, GitHub, social, referrals, newsletters, launches).
* **Top pages:** which pages people land on and which ones they spend time on.
* **Key conversions:** downloads or installs, signups, playground or demo usage, and “talk to sales” or contact form submissions.
* **CTA clicks:** which buttons people click, especially on your homepage and pricing page, so you can tell whether your primary CTA is working.

Set up your key conversions as events or goals right away. Pageviews alone won’t tell you whether the site is doing its job. Check your numbers weekly, and look at them before and after any major change (a new homepage, a launch, a pricing update) so you can see what changed.


---

# 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/fundamentals/website.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.
