ONE Customers
Stage 3 of 14 foundation Written

Customers

The one person you write for: what they want, what stops them, the words they use.

As of 2026-11-12 Last edited 2026-11-11 Read the lesson The playbook

Sources (5)
  • one.ie/web/src/content/saas-playbook/customers.md
  • text/one.md (The offer, The VSL, The treasury, Words we keep true)
  • text/clients/one/sold/sources/x402-market-brief-2026-11.md
  • text/clients/one/strategic-blueprint.md (section 3, verbatims 9 to 16 only)
  • one.ie/web/src/lib/foundation/spine.ts
Learn Customers, then write yours This is ONE's record. Copy what works and make it yours.

Customers: ONE's own run

The decision

We serve one avatar first: a very smart, ambitious young builder of about 21, and equally a smart young AI agent. Same avatar, two readers. Tony's label for him is Brian. We write for him and tell no personal story.

Why him. The market brief says the payment rail for agents exists and everyone backs it, but almost nobody sells on it: about 78 organic sellers, median seller revenue a few cents (x402stats, Sep 2026, secondhand). Supply is the bottleneck, not the protocol. A young builder with an agent and no way to be paid is the person that gap describes. Our position, from Tony: the leading payment infrastructure for agents, compared with Stripe and Coinbase.

The avatar

The lesson splits a B2B buyer into champion, economic buyer and end user. For ONE they collapse. The young builder is champion and economic buyer: he finds ONE, and his fingerprint is the only thing that raises an agent's limit. His agent is the end user, living inside ONE every day. Everything below is a hypothesis. Rows B and C are inferred.

A1, who they are (observable). A builder who already runs an agent, or is about to. Comfortable with a terminal and npx. Owns a key, not an account. The agent reads the same pages and the same npx oneie output the human does.

A2, stated pains. In heard words (from the strategic blueprint, forum and review quotes, not interviews):

  • "agents that need multiple APIs face signup/KYC/key-management overhead that doesn't scale"
  • "Most friction we see isn't the 402 handshake, it's agents managing wallet balance, gas, and chain selection"
  • "Discovery is the real bottleneck."
  • "no standard way to express 'this agent can spend up to $X/day on these API categories'"

A3, stated goals. Be paid. Let the agent sell without being babysat. Sell something inside a minute.

B1, how they see it (inferred). Ambitious and short of credit: a first real sale is proof of who they are. They distrust pitches and trust working code.

B2, underlying fear (inferred). Looking foolish for building on a rail nobody pays through. An agent that spends past its limit. A key someone else can hold.

B3, dominant need (inferred). Control and proof, not promise.

C1, watering holes. Hacker News x402 threads, r/AI_Agents, GitHub MCP repos, Coinbase and Cloudflare developer posts (blueprint, unverified).

C2, cost of inaction. The agent can talk and cannot earn. The builder keeps paying for hosting and tokens.

C3, vision. Send a link, watch it land, nobody else's key in the flow.

Trigger moments. Learning that agents can now be paid. Hitting key and signup overhead wiring a payment API by hand. Wanting a first sale to show for it.

The other buyers

Kevin, an education seller. Sells a course and needs a way to take cards and crypto and to teach with agents beside him. Sold is built for him. Still a named idea, no conversation on file.

The niche operator. One human running an agent team for movers or roofers. The Vespio side (Done With You, Done For You) is not said on one.ie, so we only note that he exists.

The Sold buyer in general. People and agents who learn to sell together: $100, one month of community included, then $100 a month (draft in text/one.md; VERIFY it can be bought today).

Pain index

Ranked by our own judgement of frequency times intensity (scale 1 to 5). Frequency comes from how often the pain shows in the scraped quotes, not from a survey.

  1. Agent has no way to be paid: frequency 4, intensity 5.
  2. Key, signup and wallet overhead per project: frequency 4, intensity 4.
  3. Fear an agent overspends: frequency 3, intensity 5.
  4. Nobody finds a paid endpoint (discovery): frequency 3, intensity 4.
  5. First sale takes too long to set up: frequency 3, intensity 3.

Receipts

Probed read-only on 2026-11-12 with curl -I:

A page that loads is not a buyer. text/one.md names no real buyer. Its VSL table (2026-11-12) says a test sale completes on testnet and that no payment through a link has a mainnet receipt yet. The only market figures we hold are the secondhand ones in the market brief.

Still open

  • No customer interviews. Zero. Every quote above is scraped, not heard by us.
  • The "about 90% agent-like wallets" and "about 3,000 daily paying agents" figures were given to us but do not appear in the market brief with a source. Not used as fact.
  • Whether the young builder and the young agent really are one avatar is a judgement, not a measurement.
  • Kevin and the niche operator are named, not met.
  • Hyperliquid trading, and "swap" in general, waits on a mainnet swap per text/one.md.
  • Sold's enrolment: text/one.md says both "draft, cannot be bought" and "went live 2026-11-09, not re-checked". Unresolved.

Do it yourself

  1. Write your avatar as one person first. If your buyer is also an agent, say so.
  2. Fill the nine cells. Mark which are heard (row A) and which are inferred (rows B and C).
  3. Copy only real quotes. Label your own paraphrase as paraphrase.
  4. Book five conversations with your first avatar. Replace one inferred cell with a heard quote each time.
  5. Probe your own landing pages and note the status code beside each.

Next in ONE's run · all 14 written

Alignment

Everything you say, checked against everything you do. What still contradicts is the work.

Open Alignment