AI Automation Specialist

• Make.com
• Zapier
• n8n

• Bonsai
• Wave
• HoneyBook

• Miro
• Loom
• Notion

I'm a no-code automation consultant. My client runs a [business type, e.g. real estate agency / e-commerce store / law firm] with [number] employees. Their current manual processes include:

[List 3-5 processes the client described, e.g.:
- Manually copying lead info from contact forms into their CRM
- Sending follow-up emails one by one after sales calls
- Pulling weekly sales data from Shopify into a Google Sheet by hand]

Tools they currently use: [list their existing stack, e.g. HubSpot, Gmail, Slack, QuickBooks]

Please do the following:
1. Rank these processes by automation ROI (time saved × frequency × error risk)
2. For each, suggest a specific Zapier or Make.com workflow that solves it
3. Flag any processes that are NOT good automation candidates and explain why
4. Estimate realistic hours saved per week for each automation
5. Suggest 2-3 additional automations they probably haven't thought of, based on their stack

Be specific. Name the exact triggers, actions, and apps involved in each suggested workflow.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

I'm a no-code automation consultant preparing a proposal for a prospective client. Here are the details:

Client: [business name and type]
Problem they described: [1-2 sentences on their pain point]
Processes I plan to automate: [list 2-4 specific workflows]
Tools I'll use: [e.g. Make.com, Airtable, Slack, Gmail]
Estimated build time: [X hours]
My hourly rate: $[rate] OR I want to price this as a fixed project

Please write a professional but plain-English project proposal that includes:
1. A brief problem statement (their words reflected back to them)
2. Proposed solution — what I'll build and how it works in plain language (no jargon)
3. Deliverables list (specific, not vague)
4. Timeline with 3-4 milestones
5. Investment section — give me both a fixed-price option and a retainer option
6. A short 'What happens next' CTA section

Tone: confident, clear, not salesy. This client is a small business owner, not a tech person. Avoid buzzwords like 'synergy' or 'leverage.' Keep total length under 600 words.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

I just finished building an automation for a client and need to write an SOP so they can understand, maintain, and troubleshoot it without calling me every time.

Here's what I built:
- Platform used: [Zapier / Make.com / n8n]
- What it does: [describe the workflow in plain English, e.g. 'When a new lead fills out the Typeform, it creates a contact in HubSpot, sends a personalized welcome email via Gmail, and posts a Slack notification to the sales channel']
- Trigger: [what starts the automation]
- Steps/actions in order: [list each step]
- Tools/apps connected: [list with login info placeholder]
- Known edge cases or failure points: [e.g. 'If the email field is blank, the Zap errors out']

Please write an SOP document that includes:
1. One-paragraph plain-English summary of what this automation does and why
2. Step-by-step flow diagram in text format
3. How to test it manually
4. Common error messages and what they mean
5. How to pause or turn it off in an emergency
6. Who to contact if it breaks (leave placeholder)
7. Monthly maintenance checklist

Write this for a non-technical business owner. No code, no jargon.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

I'm a no-code automation consultant specializing in helping [target niche, e.g. real estate agents / dental practices / Shopify store owners] save time by automating their repetitive admin work using tools like Zapier and Make.com.

I want to send cold outreach to [channel: LinkedIn DMs / cold email / Instagram DMs].

My ideal client profile:
- Business type: [describe]
- Size: [e.g. solo operator to 10-person team]
- Likely pain points: [e.g. drowning in manual data entry, losing leads because follow-up is inconsistent, spending hours on weekly reporting]
- They probably use: [list 2-3 tools common in this niche]

Please write 3 variations of outreach messages:
1. Ultra-short version (under 50 words) — curiosity-driven
2. Medium version (75-100 words) — problem-focused with a specific example
3. Follow-up version (50-75 words) — for people who didn't reply to message 1

Rules:
- Do NOT start with 'I' or compliments
- Lead with their problem, not my service
- Include one specific, believable result (e.g. 'saved 6 hours/week')
- End with a low-friction CTA (not 'schedule a call' — something easier)
- Sound like a human, not a marketing email

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

Always scope by estimated hours with a complexity buffer. Use a discovery call specifically to map the full workflow before quoting.

Make SOP documentation a required deliverable in every contract, not an optional add-on. Build a 1-hour 'walkthrough call' into your project pricing where you screen-record yourself explaining the automation to the client. Charge for ongoing support separately as a retainer.

Qualify hard during discovery. Ask: 'How many times per week does someone on your team do this task?' If the answer is under 20, the ROI math usually doesn't work.

Get proficient in at least Zapier AND Make.com before taking clients. Know which to recommend when: Zapier for non-technical clients who'll self-manage; Make.com for complex multi-step workflows; n8n for clients with developers on staff who want self-hosted control.

Use a simple service agreement for every project, even small ones. HelloSign or DocuSign for signatures — free tiers work fine to start.