Give JeremyAI your offer, relevant material, and a clear decision to work on. A short ask like “fix my VSL” leaves important context unclear. A strong brief tells JeremyAI what is known, what is assumed, what is missing, and what to address first.

Use this when you want copy edits, objection handling, a pre-call asset, offer framing, or a funnel diagnosis — and you want a more useful first response with less unnecessary back-and-forth.
​

For help putting the brief together, open the JeremyAI Prompt Guide and use Quick builder. It assembles a prompt from what you enter. You review it, then copy it into JeremyAI with the relevant material.
​

You can also use the template below directly in JeremyAI or draft the brief in another AI first. Claude and MCP are optional.
​

Give JeremyAI as many of these as you have. In a written brief, mark missing information as Unknown. In the web builder, leave unavailable fields empty; the generated prompt marks relevant gaps as [MISSING]. Do not invent numbers, proof, or results to fill a gap.

If a fact would change the recommendation, write it down. If you do not have it, say it is unknown.
​

Thin prompt:

Fix my VSL. Make it convert better.
​

Strong brief — an illustrative example:

I need JeremyAI to improve the VSL for one offer.
​
​Offer: $7,500 fitness coaching program for busy professionals who want to lose weight without extreme dieting.
​Audience: people who have tried multiple diets and cannot stay consistent.
​Current asset: I will paste the current VSL script below.
​Next step after the VSL: application for a strategy call.
​Traffic: cold Meta ads.
​
​Known facts:
​- We already deliver a 12-week coaching program
​
​Assumptions:
​- Click-through to the VSL page seems acceptable, but I have not checked it against a benchmark
​- Applications from people who finish the VSL seem weak, but I have not verified that rate
​- The opener is getting attention
​- The offer is priced correctly
​
​Unknowns:
​- Verified click-through, completion, and application rates, with the dates and sources
​- Which objections show up most on the sales call
​- Whether proof is the leak or the CTA is the leak
​
​Decision:
​Diagnose the most likely constraint first and explain the evidence.
​Do not rewrite the whole script yet.
​Tell me what not to change.
​If the evidence supports a rewrite, rewrite only the section to test first.
​If missing information would change the recommendation, ask me and wait for my answers.
​
​Off-limits:
​- Do not invent testimonials, numbers, or urgency
​- Do not add fulfillment cost
​- Do not add a new deliverable we do not already fulfill
​

The second version gives JeremyAI a scope and makes the gaps visible. The first leaves the task open to interpretation.
​

Copy this into the relevant JeremyAI chat and fill in the brackets. Write Unknown for missing information and Not applicable for fields that do not fit your task.

I want JeremyAI to help me with: [the job — VSL edit, objection handling, pre-call asset, offer framing, funnel diagnosis]
​
​Offer: [what we sell, price, who buys it, how it is delivered]
​Audience: [who they are and the problem they want solved]
​Current asset: [what I am attaching or pasting]
​Where this sits in the funnel: [ad, VSL, application, sales call, follow-up]
​What done looks like: [the specific output I need back and how I will check it]
​
​Known facts:
​- [true, checked; include the source and dates for numbers]
​- [explain what each metric counts, where relevant]
​
​Assumptions:
​- [not checked]
​
​Unknowns:
​- [information I do not have yet]
​
​Proof I can use:
​- [result, testimonial, case, or “proof is missing”]
​
​Decision I need:
​- Address this first: [the problem or asset; ask for diagnosis if the cause is unknown]
​- Do not change yet: [what to leave alone]
​
​Off-limits:
​- Do not invent facts, numbers, quotes, or testimonials
​- [my actual budget, delivery, claims, or scope constraints]
​- Do not use generic claims a competitor could paste unchanged
​
​First, restate the job in two lines and list any gaps.
​If missing information would materially change the output, ask up to 3 questions and wait for my answers before doing the job.
​If you can proceed without those answers, do the job and clearly state your assumptions.
​Check the result against “what done looks like.”
​

You can use Claude to interview you and write the brief, then paste that finished prompt into JeremyAI chat. This can help when the task or missing context needs more discussion.
​

Do this:

For this workflow, send the finished brief and relevant source material. Keep the prompt-building system file, workspace rules, and Claude setup instructions in the drafting environment. Earlier conversations and attachments do not automatically travel with the copied prompt.
​

MCP is not required. It lets you send the approved brief to JeremyAI from a connected AI client.
​

Creating a Claude project does not establish an MCP connection. First configure the JeremyAI connection and confirm that it works. Then ask Claude to send the approved brief through that connection and retrieve JeremyAI's response. If the connection is unavailable, copy and paste the brief instead.
​

Conversations sent through the JeremyAI MCP connection appear as threads in JeremyAI. This does not automatically transfer every conversation you have in Claude.
​

For setup steps, use Connect Claude Code, Cursor, or claude.ai to JeremyAI (MCP).
​

Use a strong brief when you want JeremyAI to:

For a VSL-specific workflow after the brief is ready, you can also use the VSL Conversion Diagnosis Worker.
​