Turn One Voice Note Into Customers

You already know the thing your customers need to hear. You say it on the phone four times a week. The problem was never that you have nothing to say — it's that writing it down is a job, and you already have one.

This is the build that removes the job. You talk for ninety seconds. Everything after that is a machine: a page on a site you own, and a post on every network that points back at it. Below are five principles and five paste-ready prompts. Hand them to an AI agent, answer its questions honestly, and you end up with a publishing machine whose only input is you having an idea.

Who this is for

Owners of real businesses — trades, clinics, agencies, firms. You are not trying to become an influencer. You are trying to be the obvious choice when somebody nearby searches for what you do, and to stop renting every click you get.

What you need

• An AI agent that can write files and call an API. Claude Code, or anything with tool access.
• A website you control, with a blog or resources section. Not a social profile. Ground you own.
• A voice recorder. Your phone is fine.
• Ninety seconds a day. That is the whole time commitment.

How it works

flowchart TD
  A["You talk for 90 seconds"] --> B["Agent transcribes and drafts"]
  B --> C["Page publishes on the site you own"]
  C --> D["LinkedIn post"]
  C --> E["X post"]
  C --> F["Threads post"]
  C --> G["Weekly email"]
  D --> H["Reader lands on your page"]
  E --> H
  F --> H
  G --> H
  H --> I["Books a call"]

Read the arrows. Everything points back at the page you own. Social is not the destination — it is the road to it. A post disappears in seventy-two hours; the page is still answering the same question in three years, and it belongs to you.

1. Make your voice the only input

The blank page is what kills content for busy owners — not the writing, the starting. So take the blank page out. You are not allowed to type. You talk, the machine types.

Record the way you'd answer a customer who asked you the question in the parking lot. No structure, no notes, no second take. Rambling is fine. The agent's job is to find the one idea in there and throw the rest away.

Starter prompt:

i'm going to send you voice note transcripts from my business. set up an intake for them. for each transcript: find the single strongest idea in it, name it in one sentence, and tell me what a customer would DO differently after hearing it. if there are two ideas in one note, split them into two pieces — never merge them. if a note has no real idea in it, say so plainly instead of writing something anyway. before you build the intake, ask me 3 questions about my business and who i'm actually talking to.

2. The machine may amplify, never invent

This is the rule the whole build rests on, and the one most people skip.

The agent may sharpen your sentence, cut your throat-clearing, and structure your point. It may not add a fact, a number, a story, or a claim you did not say. The moment it invents a case study you never had, you are publishing fiction under your own name — and the first customer who asks you about it in a meeting will find out before you do.

Write the rule down as a file the agent reads every single time. Not a thing you remember to say. A file.

Starter prompt:

create a constraints file that you read before drafting anything for me, and quote back to me at the top of every draft. the rules: (1) every fact, number, story and claim in the piece must trace to something i actually said in the transcript — if it isn't in there, it does not go in. (2) never invent a client, a result, a statistic or a personal anecdote. (3) if the piece needs a fact i didn't give you, stop and ASK me for it instead of filling the gap. (4) plain words, short sentences, no jargon, no hype. after each draft, list every claim you made and which line of my transcript it came from.

3. Publish on ground you own, first

The page goes live on your own site before a single social post goes out. That is not a preference, it is how search works: you want the version with your name on the domain to be the one that gets found and credited, not four copies of it on networks that keep the traffic.

Give it a real headline, a short URL, and a description written for someone reading search results. Then let the link sit for a day or two before you push it anywhere. By the time anyone clicks it from social, it has been indexed and it has been proven to actually load.

Starter prompt:

set up the publishing path to my own site first. for each piece: write a headline that says exactly what the reader gets, a url slug of 6 words or fewer, and a 155-character description written as a promise to somebody scanning google results — not a summary. publish that page and give me the link. do NOT write any social posts until the page is live. tell me the slug BEFORE you publish it, because the url is permanent once people start sharing it.

4. Write to one person, not an audience

Everything an agent writes by default sounds like it is addressing a conference. Your customers are one person, on a phone, mildly annoyed, looking for whether you can solve their thing.

So give the agent the person. Not a demographic — a person, with a job, a problem, and a sentence they'd say out loud. Then make every piece answer one question that person actually has. One question per piece. If it answers three, it is three pieces.

Starter prompt:

write me a one-page profile of my single best customer: their job, what their week looks like, the exact words they'd use to describe the problem i solve, and the thing they're quietly worried about. ask me questions until you can write it in MY words, not marketing words. then save it and read it before every draft. from now on: one piece answers exactly one question that person has. write it like you're texting them back, not addressing a room. if a draft would answer more than one question, split it.

5. Make it run without you

A machine you have to remember to run is not a machine, it is another task. The finished build should have exactly two moments where you touch it: you record, and you approve.

Everything between those — transcribing, drafting, checking, publishing, reformatting for each network — happens on its own. And build the check into the machine, not into your calendar: if a draft breaks one of your rules, the machine should refuse to publish it and tell you which rule, rather than quietly shipping something you'd be embarrassed by.

Starter prompt:

make this run without me. i want exactly two touch points: i drop in a voice note, and i approve the finished piece. everything else runs on its own — transcribe, draft, check against the constraints file, publish the page, then reformat for each network. build a hard check before publishing: if a draft breaks any constraint, or has no source line for a claim, REFUSE to publish and tell me which rule it broke and where. never fail silently. show me a one-line status i can read in five seconds.

The mistake that kills these machines

Owners build this, love it for two weeks, then quietly stop — and it is almost always the same cause. They let the machine write for them instead of from them.

The second the output stops sounding like you, you start editing every piece by hand. Editing is slower than writing. So you stop. The whole thing dies, and the conclusion everybody draws is "AI writing doesn't work."

The rule in principle two is what prevents this. Keep the machine on a short leash — amplify, never invent — and the drafts keep sounding like you, so you keep approving them in thirty seconds instead of rewriting them in thirty minutes. That is the difference between a machine that runs for years and one that runs for a fortnight.

What this actually gets you

Not virality. Something duller and much more useful: in six months you have a hundred pages on your own domain, each one answering a real question a customer asked you, each one findable, each one ending with a way to book. People arrive already sold, because they read you before they called you.

And you got there by talking for ninety seconds a day about work you were doing anyway.

Start here

Record one voice note today — ninety seconds, answering the question you're most tired of being asked. Paste the first prompt. Answer the agent's questions honestly; that is the whole unlock.

Build it once and every idea you have afterwards is already published. Hit a wall? Reply to the email that sent you this. I read every one.