Free · Dashboard BuilderGet yours→
Company AI Day · Multi-Industry / Cross-Functional · Stage 1

Prompt Library — Universal — Cross-Functional

16 prompts pre-tested for universal — cross-functional. Edit the bracketed placeholders for your situation. Copy into ChatGPT, Claude, Gemini, or Copilot.

1. Meeting notes to action plan · Anyone

You will receive meeting notes or a transcript. Produce: (1) one-sentence summary, (2) decisions made, (3) action items as Owner — Action — Due, (4) follow-up topics, (5) open questions. Be conservative — if an owner or due date isn't specified, mark it as 'unassigned.' Do NOT invent owners or dates.

Notes: [PASTE]

2. SOP from interview · Operations

You are documenting a process as an SOP. Use only the information provided. Structure: trigger, owner, prerequisites, numbered steps with sub-bullets, decision points, tools, expected timing, handoffs, quality check. Output as Markdown. Flag anything that needs more detail to be reproducible.

Process interview notes: [PASTE]

3. Email draft (in voice) · Anyone

Draft an email response in my voice. My voice: [3-5 SAMPLE EMAILS or VOICE NOTES]. Goal of this email: [GOAL]. Recipient: [WHO]. Constraints: [CONSTRAINTS]. Length: [LENGTH]. Do NOT add 'I hope this finds you well' or other generic openers I never use.

Incoming email or context: [PASTE]

4. Customer FAQ answer · Customer service

You answer customer questions using only the company knowledge base provided. If the answer isn't in the knowledge base, say so and recommend escalation. Tone: helpful, direct, no fluff. Do NOT make up policy or pricing not in the knowledge base.

Knowledge base: [PASTE OR ATTACH]
Customer question: [PASTE]

5. Job posting drafter · HR / hiring manager

Draft a job posting for [ROLE] at [COMPANY]. Use the role intake provided. Structure: hook (1-2 sentences), what you'll do, what you'll bring, what we offer, how to apply. Avoid generic corporate language and gendered/coded language. Inclusive tone. Max 350 words.

Role intake: [PASTE]

6. Proposal / quote first draft · Owner / sales

Draft a first-pass proposal for [PROSPECTIVE CLIENT]. Use my company structure: (1) Understanding of the situation, (2) Approach, (3) Timeline, (4) Investment, (5) Next steps. Voice: confident, plain English, no jargon. Use only the data provided — flag any gaps in [BRACKETS]. Do NOT invent qualifications or case studies.

Client context: [PASTE]
Scope notes: [PASTE]
Pricing approach: [FIXED / HOURLY / HYBRID]

Max 800 words.

7. Weekly status update · Anyone

Draft this week's status update. Use only the activity log provided. Structure: headline (1 sentence), what shipped, what's in progress, blockers needing decisions, next week's focus. Tone: clear, accountable, no spin. If the week was slow, say so. Max 200 words.

Activity log: [PASTE]

8. Voice memo to action items · Anyone

I'm going to dictate a brain dump. Convert it into structured output: (1) what I'm trying to do (1 sentence), (2) decisions made vs still open, (3) tasks for me with rough timing, (4) tasks I need to delegate, (5) questions I need to answer, (6) one thing I'm avoiding that I should name.

Voice memo transcript: [PASTE]

9. Cold outreach drafter (B2B) · Sales / BD

Draft 3 variants of a cold outreach message to [PROSPECT]. Each variant should: (1) open with something specific to them (use the research provided, don't fabricate), (2) state one specific value I can offer, (3) make a low-friction ask. NO 'I hope this finds you well.' NO 'quick chat?' Max 80 words each.

Prospect research: [PASTE]
What I do: [PASTE]

10. Social media post pack (LinkedIn) · Anyone building presence

Generate 5 LinkedIn post variants from this raw idea. Mix formats: (1) personal story → lesson, (2) framework / list, (3) contrarian take, (4) question to spark conversation, (5) build-in-public update. Each: 100-200 words, no hashtag walls, opens with a hook line that makes me want to read more. Do NOT use 'Excited to announce' or other LinkedIn cringe openers.

Raw idea: [PASTE]
My voice notes: [PASTE]

11. Document explainer (plain English) · Anyone

Read this document and explain it in plain English. Structure: (1) what it is in one sentence, (2) what it actually says (bullets, no jargon), (3) what's surprising or important, (4) what I should DO based on this, (5) anything that's unclear and needs follow-up. Use only the document — don't fabricate.

Document: [PASTE]

12. Negotiation message drafter · Anyone

Draft a negotiation message. Goal: [WHAT I WANT]. Constraints: [CONSTRAINTS]. Style: professional, firm, collaborative. Avoid emotional language. Reference data where I provide it. Leave a clear opening for response. Max 200 words.

Deal context: [PASTE]
What the other side has said so far: [PASTE]

13. Presentation outline from idea · Anyone

Outline a [N]-minute presentation on [TOPIC] for [AUDIENCE]. Structure: hook, the one big idea, 3 supporting points (each with one example), one objection / counter, call to action. Keep it tight. List slides as: title, key bullet, image suggestion. Max 12 slides.

What I want them to walk away with: [PASTE]

14. Difficult conversation prep · Anyone (manager, founder, partner)

I have a difficult conversation coming up. Help me prep. Output: (1) the actual goal (vs my emotional goal), (2) opening line that names the issue without escalating, (3) 3 things they're likely to say and how to respond, (4) what success looks like vs what I'm trying to avoid, (5) my one boundary or non-negotiable. Tone: human, direct, accountable.

Context: [PASTE]

15. Pricing analysis · Owner / operator

Analyze whether to change pricing on [PRODUCT/SERVICE]. Use only the data provided. Output: (1) current pricing logic, (2) what's changed (cost, demand, competition, perceived value), (3) 3 pricing scenarios with rationale, (4) recommendation with confidence level, (5) how to communicate the change to existing customers.

Data: [PASTE]

16. Project debrief / retrospective · Anyone

Run a retrospective on [PROJECT]. Use only the data provided. Structure: outcomes vs goals, what went well, what didn't, why (root cause, not blame), 3 specific lessons (each actionable), recommendations for next time. Tone: honest, no spin.

Project data: [PASTE]
Free playbook · centraops.com/company-ai-day · © Chelsea Hulin / CH Tech Ventures