đ Works best with your CRM and calendar. Connect GoHighLevel or HubSpot and Google Calendar and Jeremy AI reads your team's real booked-call numbers and your check-in times. It only reads. It sends nothing.
Paste your role facts. Get one file back: a 30-60-90 day plan table, a short welcome email, a first week checklist, a not-provided list and a check table. Nothing is sent.
You'll see the SAMPLE role facts pasted in with the rules, the plan built in about 4 seconds on screen (the real wait was about 37 seconds), the file saved with nothing sent, the plan table, the welcome email, the first week checklist, the not-provided list and the check table.
What this use case does and who it's for
You just hired someone. Their start date is coming. You know they need a plan. Then the week gets busy and the plan turns into "we'll figure it out." The new hire starts with no goals and no clear first week.
Here's the shortcut. Paste the facts you already know about the role. Jeremy AI turns them into a plan. It uses only what you stated. Five parts:
A plan table. Four columns: phase, goal, support and check-in. Three rows: days 1 to 30, days 31 to 60 and days 61 to 90.
A welcome email draft. A subject and a body of 80 words or fewer. It has placeholders for the start date and the manager name.
A first week checklist. Six items. Each one uses only the tools and training you listed.
A not-provided list. Everything a plan would need that you didn't give, like salary or tool logins.
A check table. Three columns: item, source and status. It shows where each fact came from.
It's for sales managers, coaches, agency owners and anyone onboarding a remote hire. It's drafts only. Jeremy AI doesn't send anything.
What you need before you start
A Jeremy AI account. Nothing to connect to try the sample.
Your role facts. The sample is made up: a remote appointment setter on the SAMPLE Harbor Sales Team who reports to the sales manager.
Your tools. The sample lists three: the CRM, the shared inbox and the call dialer.
Your training. The sample lists 3 recorded call-script lessons, a weekly team call on Mondays and a buddy for week 1.
Your targets, stated by you. The sample says 40 outbound dials per day by day 30, 10 booked calls per week by day 60 and 15 booked calls per week by day 90.
Your check-ins. The sample has a 15-minute Friday check-in with the sales manager.
Honest gaps. The sample says start date, manager name, salary, commission, quota beyond the targets and tool logins are "not provided."
The rules. The sample uses HARD RULES: copy the targets exactly, never calculate a new number, never invent a tool, mentor, salary, commission or quota, never predict performance, never claim what most new hires do, never mention discounts, probation, firing or pay changes, and never address you by name.
How to set it up
You use the default Jeremy AI worker. There's nothing to build.
Open Jeremy AI. From the dashboard, type in the main box. Check the worker selector says Jeremy AI.
Paste the prompt below. Swap your own role facts, tools, training, targets and check-ins in where the sample ones are.
Click Send message.
Wait. The walkthrough speeds this part up. In real time it took less than 40 seconds.
When it says the file is saved, read the chat summary first.
Open the file card and read the plan table.
Scroll to the welcome email, the checklist, the not-provided list and the check table.
The prompt
This is the exact prompt from the walkthrough. The team, the buddy and every number are SAMPLE and made up. Replace them with yours.
Act as my "New Hire Plan" worker for SAMPLE Harbor Sales Team, a sales team at a coaching company (all data below is made up). Turn the SAMPLE role facts below into a 30-60-90 day plan for a new appointment setter. Create ONE file named new-hire-30-60-90-plan.md using the file tool (reply with a short summary only) with: 1) a PLAN TABLE with exactly 4 columns (phase, goal, support, check-in), one row each for days 1 to 30, days 31 to 60 and days 61 to 90, 2) a WELCOME EMAIL DRAFT with a subject and a body of 80 words or fewer, 3) a FIRST WEEK CHECKLIST of 6 items using only the stated tools and training, 4) a NOT PROVIDED list, 5) a CHECK table with exactly 3 columns (item, source, status). Use the placeholders "[start date: not provided]" and "[manager name: not provided]" in the email. HARD RULES: goals use only the stated targets, copied exactly, never calculate a total, average, percentage or new number; never invent a tool, mentor, salary, commission, quota or detail not stated; write "not provided"; never predict performance and never claim what most new hires do; never mention discounts, probation, firing or pay changes; every table has 4 columns or fewer and cells of 12 words or fewer; never address me by name anywhere in the chat reply or the file. Drafts only, nothing is sent.
ROLE FACTS (SAMPLE):
- Role: appointment setter, remote, reports to the sales manager.
- Tools: the CRM, the shared inbox, the call dialer.
- Training that exists: 3 recorded call-script lessons, a weekly team call on Mondays, a buddy for week 1 (SAMPLE buddy: Jordan R.).
- Targets stated: 40 outbound dials per day by day 30, 10 booked calls per week by day 60, 15 booked calls per week by day 90.
- Check-ins that exist: a 15-minute Friday check-in with the sales manager.
- Not provided: start date, manager name, salary, commission, quota beyond the targets, tool logins.
Prompting tips and how to adapt it
State your targets yourself. The prompt lists the targets and says to copy them exactly. Jeremy AI doesn't pick a number for you. If you have no target for a phase, say so and it writes "not provided."
List only what really exists. The checklist can only use the tools and training you list. If you don't list a tool, it can't appear.
Say who the buddy is, or say you have none. The sample names a buddy for week 1 only. The plan keeps it to week 1.
Use placeholders for what's missing. The prompt says to use "[start date: not provided]" and "[manager name: not provided]" in the email. You fill them in before you send.
Ban new numbers. The prompt says never calculate a total, average, percentage or new number.
Ban predictions. The prompt says never predict performance and never claim what most new hires do.
Cap the length. The email body is 80 words or fewer. Cells are 12 words or fewer and tables have 4 columns or fewer.
Adapt it. Swap in any role: a closer, a coach, a support rep or an editor. Change the phases or the check-in rhythm.
The result to expect
One Markdown file named new-hire-30-60-90-plan.md, titled "New Hire 30-60-90 Day Plan: Appointment Setter (SAMPLE Harbor Sales Team)." It starts with a line saying it's a draft and nothing has been sent. With the sample data you should see:
A 4-column plan table with three rows. Days 1 to 30 has the goal "40 outbound dials per day by day 30." Days 31 to 60 has "10 booked calls per week by day 60." Days 61 to 90 has "15 booked calls per week by day 90." The support column uses your listed training and tools. The check-in column says the 15-minute Friday check-in with the sales manager.
A welcome email draft. A subject and a short body. It names the role, lists the CRM, the shared inbox and the call dialer, and mentions the 3 recorded lessons, the Monday team call, the week 1 buddy and the Friday check-in. It has "[start date: not provided]" and "[manager name: not provided]" in it.
A first week checklist with six items. Confirm access to the tools, watch the 3 recorded lessons, meet the week 1 buddy, join the Monday team call, practice outbound dials in the call dialer and attend the Friday check-in.
A not-provided list. Six items: start date, manager name, salary, commission, quota beyond the stated targets and tool logins.
A 3-column check table. Each fact you gave is marked "Confirmed" with the source "Stated role facts." The start date, the manager name and "salary, commission, tool logins" are marked "Not provided" with the status "Pending."
The chat reply summarizes the file and says nothing was sent.
These are sample results from a made-up team. Wording changes from run to run. Read every line before you send anything.
Common mistakes and fixes
A goal has a number you never gave. Delete it. Remind it: "Goals use only the stated targets, copied exactly."
A tool, mentor or perk appears that you never listed. Delete it. Remind it: "Never invent a tool, mentor or detail not stated."
Pay, commission or quota details show up. Delete them. Remind it: "Write not provided for salary, commission and quota."
Probation, discounts or firing language appears. Delete it. Remind it: "Never mention discounts, probation, firing or pay changes."
A prediction appears, like "they'll hit quota fast." Delete it. Remind it: "Never predict performance."
A claim about most new hires appears. Delete it. Remind it: "Never claim what most new hires do."
The email runs long. Remind it: "The body is 80 words or fewer."
A support cell lists something you didn't plan. Fix it by hand. The sample plan table mentions "call dialer practice" in the support column. It's a tool you listed, but check that you really want that in the plan.
You send the email with placeholders still in it. Don't. Fill in the start date and the manager name first.
You send it as is. Don't. Read the plan once, then share it yourself.