Systrify · Digital Product

ChatGPT Prompt Pack
for Automation Agencies

50 prompts · 8 categories · Works with GPT-4, Claude, Gemini · Version 1.0 · June 2026

What's inside: 50 field-tested prompts for running an automation/web agency — cold outreach, client proposals, social content, onboarding, workflow design, and sales copy. Copy, paste, and customise the [brackets].

💡 How to use these: Each prompt is a starting point. Replace all [brackets] with your specifics before sending. For best results, add "Reply in plain text, no markdown" if you're pasting the output into an email or proposal.

Category 1 — Cold Email & Outreach (8 prompts)

#1 — Write a cold email for a niche

01/50
Write a cold outreach email to a [business type, e.g. "hair salon"] in [city]. The email should be plain text, under 120 words, and pitch a [specific service, e.g. "missed-call text-back and online booking system"]. The tone should be conversational, not salesy. End with a single soft CTA asking if they'd want a 10-minute call. Do not use exclamation marks, emojis, or corporate language.
Use for: personalising the cold email templates to a new niche before upload to your email tool.

#2 — Generate 10 subject lines

02/50
Generate 10 cold email subject lines for a [business type] owner. The subject lines should feel like they're from a human, not a marketing email. Avoid "free", "save", and "boost". Keep each under 50 characters. Focus on their specific pain point: [pain point, e.g. "missed calls losing bookings"].
Use for: A/B testing subject lines in your cold email tool.

#3 — Personalise a cold email from a company website

03/50
Here is a cold email template: [paste template]. Here is what I know about the prospect: [paste website text or LinkedIn bio]. Rewrite the email to feel personalised to this specific prospect. Change only the opening sentence and one sentence in the body. Keep everything else identical.
Use for: high-value prospects where generic copy won't land.

#4 — Write a follow-up email

04/50
Write a follow-up email to send 3 days after this cold email: [paste original email]. The follow-up should be 4 sentences max, reference the original without summarising it, and add one new piece of value or a different angle on the same pain point. Do not apologise for following up.
Use for: generating follow-up variation for every cold email sequence.

#5 — Reply to an interested prospect

05/50
A prospect replied to my cold email saying: "[paste their reply]". Write a reply that confirms their interest, suggests a specific time for a call (use a placeholder like [DATE/TIME]), and keeps it under 60 words. Warm but professional tone.
Use for: responding to hot leads fast without overthinking the wording.

#6 — Objection handler

06/50
A prospect replied to my cold email with this objection: "[paste objection, e.g. 'we already tried automation and it didn't work']". Write a short, honest reply (under 80 words) that acknowledges their experience, asks one question to understand what went wrong, and keeps the conversation open. Do not be defensive or oversell.
Use for: every cold email objection reply.

#7 — LinkedIn connection request note

07/50
Write a LinkedIn connection request note to [name], who is [their role] at [company]. Reference [one specific thing from their profile]. Keep it under 250 characters. Do not pitch anything — just a reason to connect that mentions I work in [your niche].
Use for: LinkedIn outreach without getting flagged as spam.

#8 — First LinkedIn DM after connecting

08/50
Write a first message to send on LinkedIn after connecting with [name], who is [role] at [company]. They [specific detail from their profile]. I want to start a conversation about [problem I solve] without pitching. Keep it under 100 words, conversational, ends with an open question.
Use for: LinkedIn warm-up DM before pitching.

Category 2 — Client Proposals (6 prompts)

#9 — Write a project proposal

09/50
Write a professional project proposal for a [service type] project for [client name / business type]. The proposal should include: 1) Executive summary (2 sentences), 2) The problem we're solving, 3) Our approach (3 bullet points), 4) What's included (5 bullet points), 5) Timeline (3 milestones), 6) Investment (£[amount] broken into phases), 7) Why Systrify. Keep the tone confident and clear, not fluffy.
Use for: any new client proposal. Takes 5 minutes with this prompt vs 2 hours from scratch.

#10 — Scope of work bullet points

10/50
Write 8 clear "what's included" bullet points for a [service type] project. Each bullet should be specific and concrete — no vague phrases like "ongoing support" without clarifying the scope. Include any explicit exclusions at the end (e.g. "Not included: paid ad spend, third-party software licences").
Use for: the deliverables section of any proposal.

#11 — Pricing justification paragraph

11/50
Write a 3-sentence paragraph that justifies a £[price] investment for [service]. Focus on the ROI or outcome the client will get, not the hours of work. Make it feel like a business investment, not a service fee.
Use for: the "investment" section of proposals where clients balk at the price.

Category 3 — Automation Design (8 prompts)

#12 — Design a Make.com workflow

12/50
Design a Make.com automation scenario for the following business process: [describe the process in plain English]. List each module in order, including the app name, action, and what data it passes to the next module. Flag any steps that might need a Router or Error Handler. Assume I have access to all standard Make.com integrations.
Use for: mapping out any new automation before building it.

#13 — Identify automatable tasks

13/50
Here is a list of tasks a [business type] does each week: [paste task list]. Identify which of these can be fully automated, which can be partially automated, and which require a human. For each automatable task, suggest the tool (Make.com, Zapier, GHL, etc.) and the trigger/action pair.
Use for: discovery calls — run this before the call to come prepared.

#14 — Write a GHL workflow description

14/50
Describe a GoHighLevel workflow that: [describe what it should do]. Include: trigger, conditions (if any), actions in order, wait times, and what happens at the end of the workflow. Also mention any tags that should be added or removed.
Use for: briefing yourself or a VA on any GHL build.

#15 — Explain automation to a non-technical client

15/50
Explain this automation to a non-technical business owner in plain English: [describe the workflow]. Use an analogy to a human doing the same job. Keep it under 100 words. Do not use technical terms like "trigger", "webhook", "API", or "workflow".
Use for: client presentations and onboarding calls.

Category 4 — Social Media & Content (8 prompts)

#16 — LinkedIn post (thought leadership)

16/50
Write a LinkedIn post about [topic related to automation/GHL/web]. Start with a one-sentence hook that stops the scroll. Use short paragraphs (1–2 lines each). Include one specific insight or data point. End with a question to drive comments. Tone: direct, experienced, not salesy. No hashtags in the post body — add 3 at the very end only.
Use for: daily LinkedIn content that builds authority in the automation niche.

#17 — Twitter/X thread

17/50
Write a Twitter/X thread (6 tweets) about [topic]. Tweet 1 is the hook — make it a bold claim or counterintuitive statement. Tweets 2–5 each make one point with an example. Tweet 6 is the CTA (follow for more / link to a resource). Keep each tweet under 240 characters. No emojis unless they add real meaning.
Use for: growing a Twitter following in the automation niche.

#18 — Instagram caption

18/50
Write an Instagram caption for a post about [topic]. The first line should hook in under 10 words. Tell a quick story or share a specific result. End with a CTA. Add 5 relevant hashtags at the end (mix of broad and niche). Tone: authentic, conversational, not corporate.
Use for: agency Instagram content.

#19 — Case study write-up

19/50
Write a 200-word client case study in this format: 1) Who the client is (anonymised if needed), 2) The problem they had before working with us, 3) What we built (be specific), 4) The result (be as specific as possible — numbers, percentages, time saved). Tone: factual and credible, not promotional. First person from the agency perspective.
Use for: website, proposals, and social proof sections.

Category 5 — Sales & Closing (6 prompts)

#20 — Discovery call question list

20/50
Generate 10 discovery call questions for a potential [service type] client. The questions should uncover: their current process, the biggest pain point, what they've tried before, their budget range (indirectly), who makes the buying decision, and their timeline. Order them from most casual to most qualifying.
Use for: every sales call — print this and work through it.

#21 — Handle a price objection

21/50
A prospect just said "[price objection, e.g. 'that's more than we budgeted']" during a sales call. Write 3 different responses I could give — one that reframes value, one that offers a reduced scope, and one that asks a qualifying question to understand the real issue. Keep each response under 50 words.
Use for: sales call prep — practice these before every call.

#22 — Closing email after a call

22/50
Write a follow-up email to send 30 minutes after a sales call with [prospect name]. Summarise: 1) What they told us their problem is, 2) What we'd build for them, 3) The investment, 4) Next step (link to contract/proposal). Keep it under 150 words. Warm but professional.
Use for: every post-call email — send within the hour while they're still warm.

Category 6 — Website Copy (6 prompts)

#23 — Hero section headline options

23/50
Write 5 hero section headline options for a [service type] agency targeting [ICP]. Each headline should be under 10 words, focus on the outcome (not the service), and feel direct and confident. Avoid: "We help", "Transform", "Unlock", "Supercharge", "Next-level". Give each headline a one-sentence subheadline.
Use for: website copy testing — try 2–3 of these and see which converts best.

#24 — Service page bullet points

24/50
Write 6 "what's included" bullet points for a [service] service page. Each bullet should start with a noun (not a verb), be specific enough to feel credible, and avoid vague words like "comprehensive", "tailored", or "bespoke". Add a brief benefit in parentheses after each bullet.
Use for: any service landing page.

#25 — FAQ section

25/50
Write 6 FAQ questions and answers for a [service] service page. Include: how long it takes, what the client needs to provide, whether they need existing tools, what happens after delivery, whether you offer support, and one common objection (phrased as a question). Answers should be 2–3 sentences each.
Use for: handling objections on the page before they happen on a call.

Category 7 — Operations & Productivity (6 prompts)

#26 — Write a client SOP

26/50
Write a step-by-step SOP for [process, e.g. "onboarding a new GHL client"]. Each step should be numbered, start with an action verb, include who does it and what tool they use. Add a note for common mistakes or edge cases after any step that needs it.
Use for: building your operations playbook as you scale.

#27 — Create a project timeline

27/50
Create a realistic project timeline for building [deliverable] for a client. The project starts on [date]. Include: kick-off call, access collection, build phase (broken into milestones), review rounds, and final delivery. Add buffer for delays. Format as a table with columns: Week, Milestone, Who's responsible, Status.
Use for: every new client project — gives both parties clear expectations.

Category 8 — AI-Assisted Delivery (6 prompts)

#28 — Debug a Make.com scenario

28/50
I have a Make.com scenario that's failing. Here's the error: [paste error message]. Here's the relevant module setup: [describe what you configured]. What is likely causing this error and how do I fix it? Give me the most common cause first.
Use for: debugging automation errors without spending an hour on Google.

#29 — Write a GHL SMS workflow message

29/50
Write an SMS message for a GHL workflow that fires when [trigger, e.g. "a lead fills in the enquiry form"]. The message should be under 160 characters (one SMS credit), feel human and warm, include the business name as a GHL placeholder {{business.name}}, and end with a clear CTA. Avoid marketing language.
Use for: every GHL SMS in any workflow — run this before writing it yourself.

#30 — Spot gaps in a client's existing automation

30/50
Here is a description of a client's current automation setup: [paste description]. Identify: 1) What's missing that would improve their results, 2) Any steps that are likely breaking silently, 3) One quick win they could add in under an hour. Be specific and practical.
Use for: existing client upsell calls — run this before every quarterly review.
Prompt #31–50 cover: writing Zapier descriptions, HubSpot email sequences, Figma design briefs, client testimonial requests, agency pricing strategy, retainer upsell scripts, and more. These are in the Extended Pack — available as a free upgrade when you purchase any Systrify done-for-you service at systrify.com/qualify.

© 2026 Systrify · connect@systrify.com · systrify.com · Personal use only. Do not distribute.