JeremyAI puts Jeremy Haynes's approach to marketing, sales, and business growth at your fingertips. It’s an AI assistant you can turn to for help reviewing your offers, funnels, and ads, working through sales challenges, and deciding what to improve next.

To get started, open a new chat, explain what you want to improve, and share the relevant material. You can ask naturally—you do not need to choose a skill or create a worker first.

Available features depend on what is enabled for your account or workspace.

Use a normal chat when you want to explore a problem, review an asset, or decide what to do next.

Share the relevant context and ask for a specific result. For example:

Here is my landing page. The offer is [offer], and the audience is [audience]. Review it, tell me what is unclear, and recommend the first improvement to make.

When talking is easier, use a voice call. See Calling JeremyAI.

Give JeremyAI the information behind your request, such as offer notes, a landing page, an ad, a script, sales call notes, or performance numbers.

Explain what you want to improve, what you have already tried, and what kind of answer would help.

If JeremyAI cannot access a source, paste the relevant text, provide an export, or share a screenshot with sensitive information hidden.

A skill gives JeremyAI a more specific workflow for a type of task, such as offers, messaging, video sales letters (VSLs), or follow-up.

You can ask naturally or name an available skill. You do not need to browse Skills before every request, but browsing can help you discover workflows and example prompts.

See How to Use JeremyAI Skills.

A worker provides a reusable setup for a specific job, such as diagnosing a bottleneck or reviewing ad performance. It can use instructions, skills, and relevant source material to guide how it handles that job.

Use an available shared worker when it fits. Create a personal worker when you need a setup for your own workflow and material.

See Create a Focused JeremyAI Worker.

A trigger tells a worker when to run and what to do. Use one when a worker should run on a schedule or in response to a supported event.

Before setting up a trigger, test that the worker can complete the task with the available inputs. A trigger does not supply missing source material or connect an account for you.

Model Context Protocol (MCP) is a standard that lets AI applications connect to other tools and services. JeremyAI supports two different setups:

Choose the guide that matches the connection you want to set up.

For sign-in instructions, a walkthrough, and a first prompt to try, see Getting Started With JeremyAI.