> 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/marketing/content-engine.md).

# Content Engine

Most people are familiar with the concept of content marketing—creating and publishing content to attract an audience—but fail to turn content into an engine that reliably grows.&#x20;

The most common mistake we see founders make is publishing blog posts ad hoc, sharing the link on the company's social media pages, and calling that a content strategy. Unless you already have a massive online following, this will not work. Or, it will take so long to gain momentum you'll give up before it does.

Not all content needs to be a blog post, and you should be publishing in many different places, in addition to your website.&#x20;

Before you start creating content, research and document some basics:

1. Who are you trying to reach?&#x20;
2. What do they care about?
3. Where do they get their information?&#x20;

Spend maybe an hour or two on this initial investigation at most. You don't need all the right answers, just a foundation to start with.&#x20;

### Know your audience

Understanding who you're trying to reach and why will influence where and what you publish. Form an initial opinion and get to know your people.&#x20;

Start by making a list of 50 companies you think would make great customers. Detail why, and find out who would be in charge of implementing and using it. Contact them and ask if they are willing to be interviewed. Offer them something for their time (e.g., a gift card or tokens).&#x20;

### Know your channels

If you're targeting business executives, LinkedIn is a great place to be active, but if you're targeting developers, X tends to be a better channel. It's OK if you've never been active on these channels before. Anyone can build an audience online, but you will need to spend some time getting to know the platform and how to best engage in that space.&#x20;


---

# 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/marketing/content-engine.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.
