The prompts for running and growing a business — winning sales, getting customers, hiring, and keeping projects moving — each copy-ready with an example output.
A business runs on a hundred small documents: the discovery questions before a sales call, the proposal that follows, the landing page and ad that bring customers in, the job post and the résumé screen, the launch announcement, the project brief. These prompts draft that layer with real constraints and a guardrail against inventing facts, so what comes back is a usable first version — not a blank page.
They’re written for owners and small teams who do all of it themselves. Once a prompt earns its place in your week, the next move is to ship the technical pieces or take yourself out of the loop entirely — the two tools below are where this library hands off.
12 prompts · free to copy · example output on each
ChatGPTGeminiClaude
Discovery call question list
Build a sharp set of questions that surface budget, pain, and decision process.
The prompt 3 fields to fill
I have a discovery call with at . We sell .
Give me a discovery call script with:
1. Two warm-up questions.
2. Five questions that uncover their current pain and what it's costing them.
3. Three questions that reveal budget, timeline, and who else decides.
4. One question to surface the real objection before it kills the deal.
Keep each question open-ended (no yes/no). Add a one-line note on what I'm listening for under each.
Example output
Warm-up
- "Walk me through how your team handles [process] today." → listening for: their words for the pain.
- "What made you take this call?" → listening for: the trigger event.
Pain & cost
- "Where does that process break down most often?" → the symptom they feel.
- "What happens downstream when it breaks?" → the real cost.
- "How are you working around it now?" → urgency and budget for a fix.
...
Decision
- "Besides you, who'd weigh in on a change like this?" → hidden stakeholders.
TipThe "what is it costing you" questions are what let you sell on ROI later — capture their exact numbers and quote them back in your proposal.
ChatGPTGeminiClaude
Reply to a "too expensive" objection
Respond to price pushback by reframing value, without instantly discounting.
The prompt 2 fields to fill
A prospect replied that our price is too high. Write a reply that:
- Acknowledges the concern without getting defensive.
- Reframes the conversation around the cost of the problem they have today, not our sticker price.
- Asks one question to uncover what "too expensive" really means (budget, ROI doubt, or comparison).
- Does not offer a discount.
Their message:
Our price + what it includes:
Example output
Hi [Name],
Totally fair to scrutinize the number — that's the right instinct.
Quick reframe: right now, slow ramp is costing roughly [X hours] per new hire before they're productive. At your hiring pace that's the real line item; our price is a fraction of it.
So I can point you the right way — is the concern the budget itself, the payback timeline, or how we compare to [alternative]? Happy to dig into whichever it is.
[Your name]
TipThe diagnostic question is the key move — "too expensive" means three different things and each needs a different answer. Lead with their cost-of-inaction, not your feature list.
ChatGPTGeminiClaude
Executive summary for a proposal
Condense a long proposal into a one-paragraph summary an exec will actually read.
The prompt 1 field to fill
Write a one-paragraph executive summary to open a sales proposal. It should make a busy executive want to read on.
Cover, in plain language: the business problem, what we propose, the expected result (with a number if I give one), and the investment.
Details:
Keep it under 120 words, confident but not hypey.
Example output
[Company] is spending roughly six weeks getting each new support rep to full productivity — time that costs both salary and senior-rep attention. This proposal outlines an answer layer trained on your existing documentation that gets new reps productive in under two weeks and keeps answers accurate as your docs change. Based on your current hiring pace, the expected payback is under one quarter. The investment is [PRICE] per year, including onboarding and your team's data setup. The sections below detail the rollout plan, security review, and success metrics we'd track together in the first 90 days.
TipPut the result and the payback period in the first three sentences — executives decide whether to keep reading there. Save features for the body.
ChatGPTGeminiClaude
Demo prep brief from prospect research
Get a tailored demo plan so you show the right features to the right buyer.
The prompt 4 fields to fill
Help me prep a product demo. Based on what I know about the prospect, tell me which features to lead with and which to skip.
Prospect: at
Their main pains (from discovery):
Our features:
Give me: a 3-beat demo flow mapped to their pains, the one "wow" moment to land, and two questions to ask mid-demo to keep it a conversation.
Example output
Demo flow (map each beat to their pain):
1. Start at the new-rep view → "here's day one for a new hire." (pain: 6-week ramp)
2. Show a doc update auto-syncing → "answers never go stale." (pain: weekly doc changes)
3. Manager dashboard → resolution rate by rep. (pain: no visibility)
Wow moment: ask them for a real question their reps get, type it live, show the sourced answer.
Mid-demo questions:
- "Is this the kind of question that trips up new reps?"
- "Who on your side would live in this dashboard?"
TipSkipping features is as important as showing them — a demo that covers everything lands nothing. The live "type their real question" moment beats any scripted example.
ChatGPTGeminiClaude
Write landing page copy
Draft conversion-focused landing page copy from a simple brief.
The prompt 3 fields to fill
Write conversion-focused landing page copy for .
Brief:
- Target visitor: [WHO THEY ARE, HOW THEY ARRIVED]
- Their primary problem:
- What the product does:
- Key proof points: [STAT, TESTIMONIAL, OR CUSTOMER LOGO]
- Primary CTA: [ACTION + OFFER, e.g., "Start free trial"]
Sections to write: Hero (headline + subhead + CTA), Problem block (2–3 sentences), Solution block (3 benefit bullets), Social proof (use my proof points), and a closing CTA. Plain language, no filler phrases.
Example output
HERO
Headline: Stop losing 40 hours a month to manual client reporting.
Subhead: Databox pulls your clients' metrics into one dashboard and writes the report for you — automatically, every week.
CTA: Start your free 14-day trial →
PROBLEM
Agency reporting eats time you don't have. Pulling numbers from five tools, formatting slides, chasing missing data — it's two days of work that should take 20 minutes.
SOLUTION
- Connect any source in minutes: Google Analytics, HubSpot, Meta Ads, and 70+ more
- Auto-generated reports your clients can open without a login
- Custom white-label branding on every dashboard
SOCIAL PROOF
"We reclaimed 38 hours a month on reporting alone." — Jordan M., Head of Growth, Trellis Agency
Trusted by 1,400+ marketing teams.
CLOSING CTA
See your clients' data in one place today. No credit card required.
TipSpecifying how the visitor arrived (paid ad, organic search, email) lets the model calibrate how much context to establish in the hero — a cold paid-ad visitor needs more orientation than a warm email click.
ChatGPTGeminiClaude
Generate ad copy variations to test
Produce multiple ad angles and hooks for A/B testing.
The prompt 6 fields to fill
Write ad copy variations for [PLATFORM: Google / Meta / LinkedIn] promoting .
Product:
Target audience:
Primary pain or desire:
Landing page URL:
For each variation, use a distinct angle: e.g., fear-of-loss, social proof, curiosity, direct benefit, objection-first. Label each variation with its angle. Include headline and primary text for each. Stay within platform character limits.
Example output
Platform: Meta Ads
Variation 1 — Direct Benefit
Headline: Client reports on autopilot.
Primary text: Connect your data sources once. Databox writes and sends branded reports to every client, every week. No spreadsheets. No formatting. [URL]
Variation 2 — Fear of Loss
Headline: You're spending 2 days a month on this.
Primary text: The average agency wastes 18 hours per month pulling client reports manually. That's time you're not billing. Automate it in an afternoon. [URL]
Variation 3 — Social Proof
Headline: 1,400 agencies already switched.
Primary text: "We got 38 hours a month back just from automating reports." — Jordan M., Trellis Agency. See what you'd reclaim. Free trial, no card needed. [URL]
Variation 4 — Objection-First
Headline: "We tried dashboards. Clients never logged in."
Primary text: That's why Databox sends reports automatically — no client login required. They get it in their inbox, every week. [URL]
TipLabel each variation by its psychological angle before writing — it forces genuine creative diversity. Variations that share an angle tend to produce nearly identical copy, which wastes your testing budget.
ChatGPTGeminiClaude
Announce a product launch on social
Write launch-day posts that drive clicks across platforms.
The prompt 5 fields to fill
Write launch-day social media posts for , a .
Audience:
Key benefit:
Launch offer or hook: [FREE TRIAL / DISCOUNT / WAITLIST, if any]
Link:
Write one post each for: Twitter/X, LinkedIn, and Instagram. Each post should use a different angle — don't repeat the same hook. Include platform-appropriate formatting and a CTA.
Example output
Twitter/X:
We just shipped something I've wanted for 2 years.
Databox now writes your client reports automatically — every week, without touching a spreadsheet.
14-day free trial, no card required.
👉 [URL]
---
LinkedIn:
Today we launched something that's been in the works since early 2023.
Client reporting is one of the biggest time sinks for agency teams — not because the data is hard to find, but because pulling it from 6 tools, formatting it, and making it readable is a full day's work every week.
We automated all of it. Connect your sources, choose a template, and Databox sends a white-labeled report to your client automatically.
First 14 days free: [URL]
If you run an agency and reporting is a pain, I'd genuinely love to know what you think.
---
Instagram:
Reporting day 😅 vs. reporting day now ✨
We just launched automated client reports — your data, your branding, delivered weekly without you touching it.
Link in bio to try it free.
TipAssign each platform a genuinely different angle (Twitter/X: intrigue, LinkedIn: backstory, Instagram: before/after visual contrast) before writing — posts that share an angle just feel like reposts, which reduces saves and shares.
ChatGPTGeminiClaude
Plan a monthly content calendar
Turn topics into a scheduled, channel-mapped calendar.
The prompt 3 fields to fill
Build a one-month content calendar for targeting .
Input:
- Content pillars: [LIST 3–4 TOPICS]
- Channels: [e.g., blog, LinkedIn, email newsletter, Instagram]
- Publish frequency by channel: [e.g., blog 2x/week, social daily]
- Any upcoming dates or campaigns to build around:
Output format: a week-by-week table with columns: Week | Date | Channel | Content Type | Topic / Title | Primary Keyword or Theme | Goal (awareness / consideration / conversion)
Example output
Week 1 | Jun 2 | Blog | Long-form guide | "How to Onboard Remote Employees in Under 2 Weeks" | remote employee onboarding | Awareness
Week 1 | Jun 3 | LinkedIn | Thought-leadership post | Stat from the guide: 6-week average ramp | onboarding efficiency | Awareness
Week 1 | Jun 5 | Email | Newsletter | Curated: 3 onboarding templates + blog CTA | — | Consideration
Week 2 | Jun 9 | Blog | Comparison post | "Loom vs. Notion for Async Onboarding" | async onboarding tools | Consideration
Week 2 | Jun 10–14 | LinkedIn + Instagram | Daily tips (5 posts) | One tip per day from the guide | onboarding tips | Awareness
Week 3 | Jun 16 | Blog | Case study | "How [Client] Cut Ramp Time from 6 to 2 Weeks" | onboarding case study | Conversion
Week 3 | Jun 19 | Email | Product email | Case study + free trial CTA | — | Conversion
TipIncluding the Goal column on every row forces you to verify that the full calendar moves buyers through awareness, consideration, and conversion rather than clustering at one stage.
ChatGPTGeminiClaude
Create interview questions for a role
Generate role-specific behavioral questions that predict performance.
The prompt 2 fields to fill
You are a hiring manager writing an interview guide. Create behavioral interview questions for a role at a .
The role's most important competencies are: [LIST 3–4 KEY COMPETENCIES, e.g. stakeholder communication, technical judgment, execution under ambiguity].
For each competency, write:
- One behavioral question (past-tense, "Tell me about a time...").
- What a strong answer looks like (2–3 signal words or phrases to listen for).
- One follow-up probe.
Avoid questions that can be answered with rehearsed platitudes. No "What's your greatest weakness?"
Example output
**Stakeholder communication**
Q: Tell me about a time you had to deliver bad news to a client or executive who didn't want to hear it. What did you do?
Strong answer signals: gave early warning (not surprise), separated facts from opinions, had a proposed path forward.
Follow-up: What did they say, and how did it end?
**Execution under ambiguity**
Q: Describe a project where the requirements changed significantly mid-way. How did you handle it?
Strong answer signals: re-scoped rather than absorbed scope, renegotiated the deadline, communicated tradeoffs explicitly.
Follow-up: What would you do differently?
**Technical judgment**
Q: Tell me about a technical decision you made that you later regretted. What did you learn?
Strong answer signals: owns the decision rather than blaming constraints, describes what they'd change, shows updated mental model.
Follow-up: Did you change how you make that type of decision now?
TipWrite "what a strong answer sounds like" before you run the interview — interviewers who don't know what they're listening for get captured by confident delivery instead of actual signal. The follow-up probe is where you separate prepared storytellers from people who actually did the thing.
ChatGPTGeminiClaude
Promote a job opening on social
Write a social post that gets a role shared and applied to.
The prompt 4 fields to fill
Write a LinkedIn post promoting a job opening that earns shares, not just clicks.
Role:
Company:
What makes this role genuinely interesting: [2–3 REAL DRAWS]
Who we want to reach:
Application link:
Rules:
- First line must stop the scroll — no "We're hiring!" opener.
- Tell the reader what's actually interesting about the work, not just the perks.
- Under 150 words.
- End with one clear action.
Example output
The person we're looking for has probably built a sourcing function from scratch before — and has opinions about what they'd do differently.
[Company] is hiring a Head of Talent. We're 80 people, pre-IPO, and have never had a full-time recruiter. The next 18 months will add about 40 more. You'd build the process, pick the tools, and own the brand — no inherited playbook.
What we're not: a slow-moving machine where you manage a pipeline someone else designed.
What we are: a team that wants to hire well and is willing to invest in doing it right.
If this sounds like the kind of problem you want, the details are here: [link]
If it sounds like someone you know, tag them.
TipWriting for shares, not just applications, changes the structure — you need a reader who is not a fit themselves to understand why a friend would care. Write for that second-degree reader.
ChatGPTGeminiClaude
Screen a resume against a job spec
Summarize how a resume matches a role, with gaps flagged honestly.
The prompt 2 fields to fill
Screen the resume below against the job spec and give me a structured summary.
Job spec:
Resume:
Format:
- Overall fit: Strong / Possible / Weak (one line of reasoning)
- Matches: bullets of where they meet the spec directly
- Gaps: bullets of missing requirements — be honest, don't soften
- One question worth asking them on a call
Don't invent qualifications. If something is ambiguous, say so rather than guessing.
Example output
Overall fit: Possible — strong on the technical side, light on the team leadership the spec asks for.
Matches:
- 6 years in data engineering, all in fintech (spec asks 4+).
- Hands-on with dbt and Snowflake, which the spec names explicitly.
- Led a pipeline migration project end-to-end.
Gaps:
- No evidence of managing other engineers — spec requires leading a team of 3+.
- No mention of vendor negotiation or tooling budget ownership.
- ML pipeline experience listed but no specifics; could be shallow.
Question to ask: "The role manages two junior engineers from day one — have you had direct reports before, and what did that look like?"
TipAdd "if something is ambiguous, say so" to keep the model from reading gaps charitably. A resume screen that papers over missing requirements wastes everyone's time.
ChatGPTGeminiClaude
Write a project kickoff brief
Align a team on goals, scope, roles, and timeline before work starts.
The prompt 1 field to fill
Write a project kickoff brief for . This document will be shared with the team before the kickoff meeting and should answer every "why are we doing this" question before it gets asked.
Sections:
1. **Problem we're solving** — one paragraph, no jargon.
2. **Goal and success metric** — what does winning look like, with a number if possible.
3. **Scope** — what's in and explicitly what's out.
4. **Roles** — who owns what (use "unassigned" if a role isn't filled yet).
5. **Timeline** — key milestones and the ship date.
6. **Risks** — top 2, one sentence each.
Details: [PASTE PROJECT DETAILS, TEAM, DATES, CONSTRAINTS]
Example output
**Project: Customer Onboarding Revamp**
**Problem we're solving**
New customers take 34 days on average to complete onboarding, against a 14-day target. Half of support tickets in the first 90 days trace back to setup confusion. This is causing churn we can prevent.
**Goal and success metric**
Reduce median time-to-first-value from 34 to 16 days by August 31. Secondary: cut setup-related support tickets by 30%.
**Scope**
In: email sequence, in-app checklist, docs rewrite for steps 1–5.
Out: enterprise onboarding (separate project), SSO configuration.
**Roles**
Project lead: Priya | Docs: Tom | Design: unassigned | Eng: Diego
**Timeline**
Jun 23 — kickoff | Jul 14 — design review | Aug 4 — soft launch | Aug 31 — full rollout
**Risks**
- Design role unfilled; delays design review if not hired by Jul 1.
- Docs rewrite depends on Product sign-off; needs scheduling this week.
TipThe "explicitly out of scope" line prevents the brief from becoming a wish list — stating what you won't do is as important as stating what you will, and it stops scope creep before it starts.
For the writing and synthesis that runs a business: qualifying sales leads, drafting proposals and follow-ups, writing landing-page and ad copy, posting jobs and screening résumés, and planning launches. Use it as a fast first-drafter you review and edit — not a decision-maker — and never paste confidential customer or financial data into an unapproved tool.
Is ChatGPT good for a small business?
Especially so. When you wear every hat, ChatGPT covers the ones you have least time for — marketing copy, a job description, a proposal, a launch plan — at first-draft quality you then refine. The prompts here are written for exactly that: small teams and owners who need a usable starting point in minutes, not a blank page.
What business tasks can ChatGPT actually help with?
Concrete ones: discovery-call questions and pricing-objection replies for sales, proposal summaries, landing-page and ad-copy variations for marketing, product-launch posts and a content calendar, job posts and résumé-screening summaries for hiring, and project kickoff briefs for operations. Each prompt on this page handles one of these with an example output.
Are these business prompts free to use?
Yes — every prompt is free to copy with no signup or paywall, and each comes with an example output so you know what it produces before you run it.