DEV Community

devautomation
devautomation

Posted on

15 AI prompts I actually use as a tech freelancer (with the uncomfortable ones included)

#freelance #ai #career #productivity

I've been freelancing in tech for years. These are the prompts that actually save me time -- not the generic "write me an email" stuff, but specific, tested prompts for real freelance situations.

I'll share 15 free ones here. The full pack has 120, organized by use case.

Client communication

Writing a scope clarification without sounding difficult:

I need to write a professional email to a client who is requesting [scope change] which wasn't in our original agreement. I want to explain why this affects the timeline/cost without sounding defensive. Our original scope was: [X]. What they're asking for now: [Y]. Write a short, direct email that opens the door to a conversation rather than closing it.
Enter fullscreen mode Exit fullscreen mode

Following up on an unpaid invoice (firm but professional):

Write a follow-up email for an invoice that is [X days] overdue. The client has been unresponsive. Tone: firm but professional. Don't apologize. Make it easy for them to pay by [payment method]. Amount: [X]. Invoice number: [Y]. This is the [first/second/third] follow-up.
Enter fullscreen mode Exit fullscreen mode

Declining a project without burning the bridge:

I need to decline a project from [type of client] because [real reason: budget too low / not my specialty / timeline unrealistic]. Write a short, warm email that declines clearly but leaves the door open for future work. Don't be vague. Don't offer a referral unless I say so.
Enter fullscreen mode Exit fullscreen mode

Project management

Turning vague client feedback into actionable tasks:

A client sent this feedback: "[paste feedback]". Extract specific, actionable tasks from it. Group by: design changes / content changes / functionality changes / unclear (needs follow-up question). For anything unclear, write the follow-up question I should ask.
Enter fullscreen mode Exit fullscreen mode

Writing a project status update that doesn't sound like filler:

Write a weekly status update for a [type of project] project. Current status: [X% done]. Completed this week: [list]. Next week: [list]. Blockers: [list or none]. The client is [technical/non-technical]. Keep it under 150 words. No fluff.
Enter fullscreen mode Exit fullscreen mode

Creating a meeting agenda that actually gets things decided:

Create a 30-minute meeting agenda for [topic]. We need to make decisions on: [decision 1], [decision 2]. Background context: [brief context]. Format: time blocks with clear decision/outcome for each item. Include 5 min for questions.
Enter fullscreen mode Exit fullscreen mode

Technical writing

Writing a README that developers will actually read:

Write a README for [project/tool/script]. It does: [what it does]. The audience: [developers / non-technical users]. Required sections: what it does, prerequisites, installation, usage with example, common issues. Tone: practical, no marketing language.
Enter fullscreen mode Exit fullscreen mode

Explaining a technical decision to a non-technical client:

I need to explain to a non-technical client why I chose [technical decision] over [alternative]. The real reasons: [technical reasons]. Translate this into plain language. Use an analogy if it helps. Max 3 sentences. No jargon.
Enter fullscreen mode Exit fullscreen mode

Sales and proposals

Writing a project proposal introduction:

Write the opening paragraph of a project proposal for [type of project] for [type of client]. My key differentiator: [what makes me different]. The client's main concern is: [timeline / budget / quality / reliability]. Don't start with "I". Lead with their situation, not my credentials.
Enter fullscreen mode Exit fullscreen mode

Responding to a request that's underbudget:

A potential client has a budget of [X] for a project that realistically costs [Y]. Write a response that: acknowledges their budget without dismissing it, explains what [X] could actually buy, opens the door to a conversation about scope or phasing. Don't be condescending.
Enter fullscreen mode Exit fullscreen mode

Automation and productivity

Writing a bash/PowerShell script comment block:

Write a professional comment block for this script: [paste script]. Include: what it does, requirements, usage example, author, date. Format for [bash/PowerShell/Python]. Keep it concise -- developers will read this.
Enter fullscreen mode Exit fullscreen mode

Turning a messy process into a checklist:

I have this process that I do manually: [describe the process]. Turn it into a numbered checklist that someone else could follow without asking me questions. Identify any steps where decisions need to be made and add decision criteria.
Enter fullscreen mode Exit fullscreen mode

The prompts I use most

The ones I reach for every week:

  • The unpaid invoice follow-up (always uncomfortable, this makes it less so)
  • Vague feedback -> actionable tasks (saves 30 min of confusion on every revision round)
  • Technical decision explanation (clients respond better when they understand the why)

The full pack

These 15 are from a pack of 120 prompts I use in my freelance work, organized into categories: client communication, project management, technical writing, proposals, invoicing, hiring, and automation.

AI Prompt Pack for IT Freelancers -- 120 prompts -- USD.

All prompts are in Polish and English. Tested on Claude, ChatGPT, and Gemini.

Related articles

Full toolkit: devautomation.gumroad.com

What prompt do you find yourself rewriting from scratch every time? Drop it in the comments -- I'll share what I use.

Top comments (0)