Opinion

My team page lists fifteen people who do not exist

20 August 2026, 5 minute read

The team page lists fifteen names (Audrey, Cecily, Delia, Greta, Henry, Ivor, Margot, Owen, Porter, Quentin, Rhett, Sable, Silas, Tobias and Wren), and all fifteen are AI agents.

The first sentence on that page says they are software, so when a client calls and asks who Margot is, I can tell the truth.

Why the agents have names

The alternative is describing them as a system, which tells a client little. "Automated proposal generation" says nothing about what happens on a Tuesday. "Quentin drafts the proposal, Cecily checks it for anything internal, and it does not leave the building until both have passed it" tells you exactly what happens, and the names make the order easy to follow.

Naming them also makes the boundaries obvious. If Quentin drafts and Audrey audits and Audrey cannot change anything, that separation is easy to say and easy to check. Both are harder when everything is called "the system."

Why the first sentence has to say what they are

First, clients find out. If the page showed invented colleagues with stock photographs, a client would eventually ask to speak to Margot, and I would have to admit she does not exist.

Second, a one-person company with fifteen agents is unusual, and presenting them as staff would hide the most unusual fact about how the company works.

The three disclosure rules

All three are enforced in code.

Each agent signs with its own name. Every client-facing message goes out under the agent's own name with a line saying it is an automated agent and that a person will read a reply. The check runs at the single point where anything is recorded as sent, so there is no path around it.

DISCLOSURE = "An automated agent of Purcell Ventures LLC. " \
             "Reply and a person will read it."

Internal notes never go to clients. The proposal agent once drafted twenty documents that all carried internal notes meant for me. None went out, because a separate agent whose only job is compliance reads everything at the choke point.

The auditors cannot fix anything. The agents that inspect the live properties are read-only. Keeping the agents that find problems apart from the ones that fix them took one design decision, and it also let findings pile up unfixed.

What this costs

It costs me some credibility. "One person and fifteen scripts" sounds smaller than "our team," and some prospects would have been more impressed by the second phrase.

I would rather work with the prospects who are fine with the first one, because a client who learns the truth later will wonder what else I overstated.

If you are building something similar

Say what it is on the page where you say what it does. Put the disclosure inside the function that sends. If you would be uncomfortable having a client read a sentence about your company back to you, rewrite it.

I wrote up the agents' failures in what the agents get wrong.

Part of the guide AI for small business.