AI Income Intermediate 13 prompts

AI Prompts for AI Automation Services

Prompts for packaging AI automation services, auditing workflows, onboarding clients, and delivering automation projects.

Who These Prompts Are For

Automation freelancers, agencies, consultants, and operators who sell automation services. These prompts help you find client opportunities, package offers, onboard clients, map workflows, and deliver projects that keep running.

How to Use These Prompts

Copy any prompt into ChatGPT, Claude, Gemini, or another AI tool. Replace placeholders like [client], [process], and [tool]. Tell the AI which platform you build on. Don’t paste sensitive client data, describe processes generically.


Automation Audit Prompts

Find client automation opportunities:

Act as an automation consultant. A client runs a [type of business] and does these tasks: [list with rough frequency and tools].

Identify the top 5 automation opportunities. For each: the manual work it replaces, time saved, the tools involved, and risk level. Rank by value-to-effort and recommend where to start.

Prepare an automation discovery call:

Write discovery questions for a client call about automating their operations.

Their business: [describe]. 

Ask 12-15 questions that uncover repetitive tasks, tools, where errors happen, handoffs, and what they wish was automated. Group by theme, keep them plain-spoken for a non-technical owner.

Audit a single process for automation:

A client's process works like this: [describe start to finish, tools, frequency].

Map it, find the manual and error-prone steps, and recommend what to automate, what to keep manual, and where approval steps are needed. Output a clear before/after summary I can show the client.

Service Package Prompts

Create automation service packages:

Help me package my automation services for [client type].

My skills/tools: [list]. 

Create 3 offers (e.g., single automation, automation bundle, setup + monthly maintenance). For each: deliverables, who it's for, the outcome, and a pricing approach tied to value. Keep them easy to understand.

Design a maintenance retainer:

Design a monthly maintenance retainer for automations I've built for clients.

What it includes (monitoring, fixes, tweaks, reporting), the value to the client, and why ongoing support is worth paying for. Make the recurring value visible. Suggest a simple pricing structure.

Write an automation offer statement:

Write a clear offer statement for my automation service.

I help [client type] [achieve result] by automating [what]. 

Give me the one-liner, the problem it solves, the deliverables, and the outcome — specific enough that the right client immediately gets the value. Avoid tech jargon.

Client Onboarding Prompts

Write onboarding questions:

Write onboarding questions for a new automation client before I start.

The project: [describe]. 

Cover: the exact current process, tools and access I'll need, edge cases, who approves what, success criteria, and constraints. Group them and keep them answerable by a non-technical person.

Create an access and credentials checklist:

For an automation project using [tools], list the access and credentials I'll need from the client.

For each: what it is, why I need it, and how to share it securely. Add a note on security best practices (least access, revoking later). Format as a checklist.

Workflow Design Prompts

Map a client workflow:

Design the automation for this client process: [describe the goal and current steps]. Tool: [Make/Zapier/n8n].

Give me: the trigger, the steps, the data passed between them, conditions/branches, approval points, and error handling. Output it clearly enough to build from and to explain to the client.

Plan error handling for a client automation:

Here's an automation I'm building for a client: [describe the flow and tools].

List how it could fail (missing data, rate limits, bad formats, API errors), and design the error handling: what to catch, when to retry vs. stop, and how the client gets notified. Keep notifications useful, not noisy.

Delivery Checklist Prompts

Create a delivery checklist:

Create a delivery checklist for an automation project so quality is consistent.

Cover: testing with real and bad data, confirming approval steps, error notifications, documentation, client walkthrough, and rollback plan. Format as checkboxes I run before marking it done.

Write handoff documentation:

Write client-facing handoff docs for an automation I built.

What it does: [describe]. Trigger: [describe]. Steps: [list]. Tools: [list]. 

Include: a plain-language overview, how to know it's working, what to do if it breaks, what NOT to change, and contact info. Write so a non-technical person can follow it.

Write a results report:

Write a short results report for a client after running their automation for [period].

Cover: what it did (volume, time saved, errors handled), what's working, any issues, and a recommendation for next steps (including upsell to maintenance or a new automation). Keep it clear and value-focused.

Continue learning

Explore related guides, tools, workflows, and prompts that help you go deeper into this topic.

More prompts for every use case

Browse the full prompt library — search by keyword or filter by category to find copy-paste prompts for your work.

Frequently Asked Questions

What does an AI automation service actually sell?

Time saved and fewer errors. Clients pay you to find their repetitive work and automate it reliably. The audit and package prompts below help you turn 'I can build automations' into a clear offer with a measurable result the client cares about.

Do I need to be a developer?

Not necessarily, many automation services are built on no-code tools like Make, Zapier, and n8n. You need to understand the client's process, design a reliable flow, and handle errors. The prompts here help with the planning and client-facing parts.

How do I price automation projects?

Price on value (time saved, errors avoided) rather than hours. A common model is a setup fee plus an optional maintenance retainer. The package prompts help you structure offers; tie the price to the outcome, not the build time.

How do I hand off an automation so it keeps working?

Document what it does, how to monitor it, what not to change, and who to contact. The delivery and handoff prompts below produce client-friendly documentation so the automation survives after you're done, and positions you for a maintenance retainer.

Last updated: