> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/use-cases/ai-startup-founders.md).

# AI Startup Founders

Startup founders, especially those building in AI, face one major challenge—time. With so many priorities, crafting and sending timely, well-written email updates to users, investors, and stakeholders often falls through the cracks. Gathering content from multiple sources like websites, docs, and release notes only complicates things further.

Humanic makes email marketing effortless. You can reference existing content, let AI refine your rough drafts, and build on past updates to quickly create polished, on-brand, and grammatically correct emails.

{% hint style="success" %}
For startup founders, the most important thing is getting the message out. Humanic makes it easy to create brand-cohesive, grammatically correct emails for investors, prospects, and customers.
{% endhint %}

Try it out for your yourself [click here](https://www.humanic.ai/) to sign up


---

# 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://humanic.gitbook.io/humanic/use-cases/ai-startup-founders.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.