Writing

Jack AM Austin · 2026-10-10

AI-Powered Client Acquisition: What to Automate and What Must Stay Human

Decide what AI can help with across content, research, tools and tracking while keeping your experience, judgement and promises human.

Jack AM Austin Field Notes: AI and Client Acquisition.

I use AI every day. I also refuse to let it invent the person my customers think they are buying from.

Those two things belong together.

AI helped kill my content agency. Now I pay it every month to help run my business. Slightly awkward relationship, but here we are.

The useful question is not whether AI belongs in client acquisition. It is which part of the job you are handing over, and what the buyer needs to believe about the person behind it.

A machine can organise a real experience. It cannot have the experience for you.

Start with the customer journey

My system connects content, outreach, useful tools, email and offers.

Someone discovers me, watches or reads something, tries a tool or joins the newsletter, and gets to know me before deciding whether to work together.

That is the journey. The subscriptions are the equipment.

You could buy every tool I use and still have no clients. You would just have no clients and considerably more passwords.

Before buying another one, name the handoff it will help with. Will it turn a recording into something people can find? Help identify suitable prospects? Deliver a useful result? Keep track of a reply? Make the next step clear?

If you cannot name the job, buying software is probably not the next job.

Keep the experience human

My rule is simple: if something needs my personality or my experience, it must come from me first.

I record what happened. I talk through a problem. I explain a decision, including the part that did not go as planned.

Then AI can help organise it. Sometimes one ramble contains several useful ideas. Sometimes what feels like a brilliant insight is just me being annoyed about something that should stay private.

I use it to help separate those things. I do not ask it to invent ten opinions that a client-acquisition specialist ought to have.

That distinction matters because a prospective client is trying to understand how I think. If the thinking is generated from the same prompt everyone else uses, there is very little of me left to buy.

Automate the production around the idea

Descript lets me edit a talking-head recording through its transcript and turn longer recordings into clips. Deleting a sentence by deleting the words suits me better than hunting for it on a timeline while listening to myself say it seventeen times.

CapCut handles my skits and more visual edits. The source is still footage of me. The tools make it easier to turn that footage into something somebody can watch.

AI can also turn a recording into candidate posts, email material and shorter extracts. The word candidate matters. The extract still needs to mean what I meant when I said it.

Check whether it has removed a caveat, joined two unrelated moments or made a stronger claim than the recording supports. Repurposing should make the source easier to encounter, not improve the facts until they become fiction.

Use research to find fit, not fake familiarity

I use AI to help find suitable people, check whether they are active and handle the surrounding outreach admin.

I write the messages myself.

There is no invented admiration for a procurement post I have never read. A name at the top of a message does not turn a generic pitch into a relationship.

The offer can be simple: I have made something useful, and I am asking whether they want it. A tool, a relevant session or a concrete resource gives the person something to judge beyond my ability to manufacture a compliment.

Research still needs checking. In my LinkedIn workflow demonstration, the system proposed someone who did not match my criteria. I challenged that choice and asked for the selection rules to be updated.

That is a useful part of the demonstration. An agent making a choice is not evidence that it made the right choice.

Build something the reader can use

Claude Code and Codex help me build websites, landing pages and interactive apps.

Roast My Brand is one example. The person gets a result they can inspect rather than another PDF they can feel guilty about not reading.

The point is to let someone experience a piece of my judgement before buying anything. A tool is useful when its questions and feedback reflect a real problem I can help with.

The code can be generated. The judgement behind the questions, the limits of the answer and the promise made to the user still need an owner.

A working page also needs a working handoff. Check that the result is delivered, the invitation says what the person is joining and the next step leads where it promises. A beautiful diagnostic that ends in a broken link is a very elaborate dead end.

Keep email connected to real work

Beehiiv runs my newsletter and email sequences. My daily emails give people time to understand how I think, what I do and whether they want my help.

AI can help organise the material. It should not invent the story, a client result or a customer quotation because the draft needs a more exciting ending.

I capture things that actually happened and connect them to a useful insight. There is an offer in the business, and I am upfront about that.

The reader gets to decide whether the way I work makes sense for them. That decision needs something real to rest on.

Track what happened

Sheets keeps track of outreach, replies and follow-ups. Drive holds the documents and materials.

Neither is particularly glamorous. Remembering who asked you for something is still useful when you are trying to run a business.

Separate a planned action from a completed one. In the workflow demonstration, the system checked whether a request had been sent and logged the action. That is a better habit than treating a button click as proof of delivery.

Keep the same distinction in reporting. A connection is not an email subscriber. A subscriber is not a customer. A tool being used does not prove that it caused a sale.

Use a handover check

Before handing a task to AI, answer five questions.

  1. What real source will it work from?
  2. What may it change, and what must stay true?
  3. Which decision still belongs to me?
  4. What would a visible failure look like?
  5. How will I verify that the action happened?

For a video extract, the source is the recording and the check is whether the meaning survived. For prospect research, the source is the actual profile and the check is whether the person matches the criteria. For a tool, the source is the method and the check is whether the user receives a useful, honest result.

This check is a practical way to apply the boundary. It is not a claim that a particular automation method is permitted by every platform. Platform rules need their own check.

Keep the part people came for

I want AI to reduce the work around showing up. I do not want it to replace the person showing up.

Let it help with code, editing, research, organisation and tracking. Keep your experiences, your judgement, your promises and your relationships attached to you.

If you want to watch how I connect those pieces, join the daily email. You can see the system from the inside and decide whether the thinking is useful to you.

Sources and further reading

These examples come from my AI workflow video and my LinkedIn workflow demonstration. The handover check is an editorial synthesis of those examples.

For the connected system, read how to get clients without sales calls. For the writing boundary, read how to create content that sounds like you.

Join my daily email