> For the complete documentation index, see [llms.txt](https://jmperafan.gitbook.io/meetups/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jmperafan.gitbook.io/meetups/before-the-meetup/marketing.md).

# Marketing

## Organic <a href="#organic" id="organic"></a>

The first couple of meetups are the most difficult ones to fill. After a while, you will have a crowd and will get much easier to fill a room.

## Paid ads <a href="#paid-ads" id="paid-ads"></a>

One might argue that paid ads are a bit counterproductive. They might make the event feel more commercial or less personal. Also, part of the charm of meetups is that they happen organically. You can try paid ads, but I would personally use it as a last resource.

## Word of mouth <a href="#word-of-mouth" id="word-of-mouth"></a>

Reach out to all your colleagues, currently clients, former clients, and even people you might not know but follow on LinkedIn or Slack. Personal message are quite effective!

## Reach out personally <a href="#reach-out-personally" id="reach-out-personally"></a>

Sending a direct message and addressing people on a personal basis works much better than mass messages. Part of the reason people don’t engage with meetups is because they fill that the event will happen with or without their participation. But reaching out makes it personal.

## Ask speakers to invite somebody <a href="#ask-speakers-to-invite-somebody" id="ask-speakers-to-invite-somebody"></a>

All methods above work extra well when every speaker (and co-organizer) does it! Most speakers have a personal interest in having a full room.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jmperafan.gitbook.io/meetups/before-the-meetup/marketing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.