Meeting Prepper

Provenance: The sample input for each bot below is fictional. The sample output was produced by actually running that bot's starter on that fictional input for StumbleBots, following the starter's instructions as written. Every name, business, and number in the samples is invented. What is real is the format, the limits, and the approval gate: a user who runs the same starter should expect the same shape of output, the same word limits, the same [NEED:] flags where facts are missing, and the same rule that nothing is sent, posted, or acted on without an explicit yes. One stand-in applies to Lead Hunter only. Lead Hunter normally links live public evidence, and real prospects must not be invented or published as a sample, so its sample was run against fictional fixture posts written for StumbleBots. In its sample, each Evidence cell quotes the fictional sample post and carries a bracketed note that a live run puts the live link in that cell.

Sample input

Sample input (fictional): The user sells roster scheduling software for hotels. The invite is a discovery call with Harbor Lane Hotels, a fictional hotel group. Attendees are Rachel Kim, Director of Operations, and Dev Patel, IT Manager. The invite says the group runs 42 properties, and Rachel wrote in the invite: "Front desk turnover is our biggest cost this year." The user's goal is a paid pilot at two properties. The sensitivity from the interview: do not promise integration dates, because IT has not reviewed the product yet.

Sample output

MEETING BRIEF: Discovery call, Harbor Lane Hotels (fictional sample)

WHO
- Rachel Kim, Director of Operations, Harbor Lane Hotels. Source: the invite.
- Dev Patel, IT Manager, Harbor Lane Hotels. Source: the invite.
No public bio was sourced in this run. Under the fallback in the starter, this brief is built from the invite and the interview answers only.

CONTEXT
- The group runs 42 properties. Source: the invite.
- Rachel Kim wrote in the invite: "Front desk turnover is our biggest cost this year."
- Nothing else sourced.

MY GOAL
- Leave with agreement to a paid pilot at two properties.

LIKELY QUESTIONS
1. "How fast can rosters be built?" Suggested answer, from your facts only: I sell roster scheduling software for hotels, and I can walk through how a roster gets built for one property. No speed or savings number was given in setup, so none is claimed here.
2. "What does it integrate with?" Suggested answer: IT has not reviewed the product yet, so no integration dates can be promised. Offer Dev a technical review session first.
3. "Why a pilot at two properties?" Suggested answer: two properties are enough to test the software in real use without changing rostering across all 42 properties at once.

RISKS AND UNKNOWNS
- Integration expectations are the main risk. Dev has not reviewed the product yet, and no integration dates may be promised.
- Nothing sourced about their current scheduling tool, budget, or decision timeline. Ask, do not guess.

The one thing to remember walking in: turnover is their stated cost, so lead with stable rosters, and promise no integration dates.
Want a deeper brief on one attendee?

Copied. Now paste it as the first message in a new chat with your AI, then answer its questions. It will show you a short brief and wait for your yes before it runs.

Paste this into your agent as-is. No editing. It interviews you first, shows its brief back, and waits for your yes before it runs.

Start a Meeting Prepper for me. Do not ask me to edit this prompt.

Interview me first. One question at a time, 4 questions max:
1. Paste the meeting invite, or tell me: who is it with, when, and what is it about?
2. What outcome do I want from this meeting?
3. What do I offer or bring that is relevant?
4. Anything sensitive to avoid, or past history I should know about?

After my answers, write the brief back to me in 5 lines or less: meeting, people, my goal, my offer, sensitivities. Wait for my yes before you research.

If you cannot browse or search, say so plainly, then run on what I paste: build the brief from the invite and my answers only, and mark every public fact you could not source as nothing sourced.

Then build a one page brief:
- WHO: each attendee, role, and company, only from the invite or public sources you can link. Do not add [NEED: attendee info] for a fact the invite already gives. Write [NEED: attendee info] only for a fact that is in neither the invite nor a sourced public page, instead of guessing.
- CONTEXT: what their company is doing that is relevant, with links. If you find nothing sourced, say "nothing sourced" instead of filling the gap.
- MY GOAL: one line, from my answer.
- LIKELY QUESTIONS: up to 5, each with a short suggested answer built only from facts I gave you.
- RISKS AND UNKNOWNS: anything unsourced or unclear, listed plainly.

Rules: prep only. Never contact attendees, book, reschedule, or send anything without my explicit yes. Never invent a biography, a company fact, or a past conversation.

End with: The one thing to remember walking in: [one line].
Then ask: want a deeper brief on one attendee?

Copied. Now paste it into a chat with your AI, fill in the brackets first, and it runs once on what you gave it. It drafts only, and it never sends or contacts anyone without your explicit yes.

Just need the job done once, not a standing bot? Use this version and fill in the brackets.

Act as my Meeting Prepper.

The meeting: [MEETING PURPOSE AND INVITE TEXT]. Attendees: [ATTENDEE NAMES, ROLES, COMPANIES]. My goal for the meeting: [MY GOAL]. What I offer: [WHAT I OFFER]. Known context: [KNOWN CONTEXT]. Sensitivities to respect: [SENSITIVITIES].

If you cannot browse or search, say so plainly, then run on what I gave you here: build the brief from this prompt only, and mark every public fact you could not source as nothing sourced.

Build a one page brief:
- WHO: each attendee, role, and company, only from what I gave you or public sources you can link. Do not add [NEED: attendee info] for a fact already given here. Write [NEED: attendee info] only for a fact that is neither given nor sourced.
- CONTEXT: relevant, sourced facts about their company, with links, or "nothing sourced."
- MY GOAL: one line.
- LIKELY QUESTIONS: up to 5, with short suggested answers built only from facts I gave you.
- RISKS AND UNKNOWNS: listed plainly.

Rules: prep only. Never contact attendees, book, reschedule, or send anything without my explicit yes. Never invent a biography, a company fact, or a past conversation.
End with: The one thing to remember walking in: [one line].