<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Pricing on Liam Ding</title>
    <link>https://www.liamding.com/en/tags/pricing/</link>
    <description>Recent content in Pricing on Liam Ding</description>
    <image>
      <title>Liam Ding</title>
      <url>https://www.liamding.com/img/og-cover.png</url>
      <link>https://www.liamding.com/img/og-cover.png</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0800</lastBuildDate>
    <atom:link href="https://www.liamding.com/en/tags/pricing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Personal agents split into two markets: productivity sells ROI, secretary sells time</title>
      <link>https://www.liamding.com/en/posts/2026-10-12-personal-agents-productivity-vs-secretary/</link>
      <pubDate>Mon, 12 Oct 2026 00:00:00 +0800</pubDate>
      <guid>https://www.liamding.com/en/posts/2026-10-12-personal-agents-productivity-vs-secretary/</guid>
      <description>Grok Bot and Muse get filed as one category. They are two businesses: one priced against the user&amp;#39;s hourly value and sold on proven ROI, the other against the subjective value of free time, settled in transactions.</description>
      <content:encoded><![CDATA[<h2 id="the-problem">The problem</h2>
<p>&ldquo;Personal agent&rdquo; is one word covering two products, and the demos are the reason nobody notices. A chat box, a browser session, a phone call, a finished task — Cue and Grok Bot look like Instinct and Muse, so they get filed as one category racing to one finish line.</p>
<p>Filed together, they generate contradictory conclusions: consumer AI subscriptions are hitting a ceiling, and agents are the next platform shift. Both can be true at once, because one is a per-seat productivity sale and the other is a mass-market chore-removal sale. Different buyers, different pricing anchors, different moats, different failure modes — and the biggest product decisions (what to charge for, what to build first, which constraint to attack) come out differently depending on which one you are actually building.</p>
<h2 id="what-i-concluded">What I concluded</h2>
<p><strong>Two value propositions, two anchors.</strong> The productivity type creates more value for the user: the agent is worth what the user&rsquo;s time is worth economically. The buyer is a pro consumer raising their own throughput, the test is ROI, and a subscription is the natural shape of the business. The secretary type hands the user&rsquo;s time back: the agent is worth what free time is subjectively worth to that person. The hour it buys back may be spent on short videos and the payment still holds. The buyer is the ordinary consumer, and what is being purchased is the removal of a chore.</p>
<p>That makes the pricing question different in kind. Productivity asks &ldquo;what is your hour worth?&rdquo; — the anchor is a wage or a budget line, so the ceiling is high and the population able to answer is small. Secretary asks &ldquo;what would you pay to never do this again?&rdquo; — the anchor is a chore and cheap human supply, so the ceiling is low and the population is everyone.</p>
<p><strong>The asymmetry is the whole argument.</strong> Productivity agents monetise better per user; secretary agents have far more users. The A16Z figures reported on 7 October show how thin the paid base still is: about half of Americans have used AI, 25% daily, but as of August 2026 only 4.5% hold a personal paid subscription to ChatGPT, Gemini or Claude, and the top 1% of payers spend around $903 a month and account for 19.5% of all spend. That is the shape of a narrow, high-willingness-to-pay market. The secretary type aims at the other 95%, who will not pay $20 a month for it.</p>
<p><strong>Which is why the secretary type&rsquo;s natural revenue is the transaction, not the subscription.</strong> Brian Armstrong&rsquo;s account of Coinbase&rsquo;s agentic-finance push is the reality check in both directions. Card fees start around 30 cents before any percentage, so payments below a dollar are structurally unprofitable, and 76% of the agent commerce transactions Coinbase observes are under 30 cents. His conclusion is that agents need their own accounts and stablecoin rails. Mine is narrower: a take-rate business in agent commerce has to be machine-frequency volume, not consumer checkout, and a $288 phone-call saving is a service nobody can take a share of. So the secretary type&rsquo;s real revenue shape is probably a subscription for trust and permission plus a take on the transactions that do clear at meaningful size — a harder business to model than either camp usually admits.</p>
<p><strong>The entry point is the prize, and nobody has won it yet.</strong> If the last internet had apps that let people fetch services themselves, the next one has agents that complete tasks for them, and increasingly agents that coordinate with other agents to do it. That is why the winner of this market is unlikely to be the smartest agent, and more likely to be the platform that becomes the default daily entry point for hundreds of millions of people, with a large agent network behind it. Today&rsquo;s evidence does not show that entry point existing yet. Peter Yang runs Muse for personal, Grok Bot for work, Claude for specific jobs and ChatGPT for the rest; Nikunj Kothari keeps Codex as his daily driver, calls Instinct and Muse the best zero-config consumer agents he has used, and still finds Codex with Computer Use on a Mac unmatched. When the heaviest users run four agents, that is a stack, not an entry point. Collapsing the stack is the prize, and only the secretary type genuinely needs it.</p>
<p><strong>The receipt is real on the productivity side.</strong> xAI gave Grok Bot access to supplier spend, contracts and usage data and built Haggle Bot, which found more than $100,000 of direct savings: 43 paid seats on one SaaS product inactive for 90 days ($14,220), $85,662 a year of unused SKUs elsewhere, and an office-supplies order negotiated from $14,629 to $6,143. Set that against the secretary type&rsquo;s best consumer number — Peter Yang reporting that Muse saved him more than $800 a year on cable and phone bills, including a Muse-versus-Comcast transcript worth $288 — and you have the same technology selling two different things. One prints an auditable receipt. The other performs a small favour.</p>
<h2 id="constraints">Constraints</h2>
<ul>
<li><strong>Who can pay.</strong> The 4.5% paid base, and the top 1% accounting for 19.5% of spend, define the productivity type&rsquo;s reachable market. The secretary type&rsquo;s base is everyone else, at a much lower price.</li>
<li><strong>Authority and blast radius.</strong> Before an agent can spend your money, use your accounts and carry the consequences, permissioning has to be a product. Anthropic&rsquo;s containment post frames risk as probability multiplied by blast radius: probability keeps falling with safeguards and training, while blast radius only grows with capability and permissions, and access a lab would have refused a year ago is now routine. Simon Willison&rsquo;s 3 October argument is the consumer-side version — metered, agent-driven services should default to a hard budget cap that cuts off with an error, with an explicit opt-out rather than a warning email.</li>
<li><strong>Liability is no longer hypothetical.</strong> California&rsquo;s Attorney General issued an investigative subpoena to OpenAI over AI cybersecurity risk after its agent breached Hugging Face infrastructure, and warned developers about their exposure. Whoever holds the wallet holds the case file.</li>
<li><strong>The capability is not generally available.</strong> Nan Yu could not place calls with either Muse or Instinct, because both said they could not do it. That is the distance between a demo and a secretary.</li>
<li><strong>Integrations are the work, not the model.</strong> Kothari&rsquo;s home-network prompt sits on top of an agent already handling Gmail, a thermostat, DoorDash and Amazon. Nobody in that stack is waiting for a better model.</li>
<li><strong>Cheap human supply sets the ceiling.</strong> A cleaner or an errand runner prices the secretary type&rsquo;s chores long before a model does.</li>
<li><strong>Sub-dollar transactions limit the take.</strong> With 76% of observed agent commerce under 30 cents, the take-rate story needs machine-scale volume to work at all.</li>
</ul>
<h2 id="the-options-and-what-i-traded-away">The options, and what I traded away</h2>
<table>
  <thead>
      <tr>
          <th>Option</th>
          <th>What it buys</th>
          <th>What it costs</th>
          <th>Why I picked it, or did not</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Productivity type billed against measured savings</td>
          <td>A buyer who already owns budget, ROI a champion can defend internally, revenue this quarter</td>
          <td>Value concentrates in the top 1%; sales-heavy; renewal dies the moment the number stops</td>
          <td>Picked for near-term revenue. Haggle Bot&rsquo;s shape is right, but n=1, so the measurement has to live in the product, not in a case study</td>
      </tr>
      <tr>
          <td>Secretary type sold as time handed back</td>
          <td>The largest under-served base, 95% of which does not pay for AI today, and the only route to a daily habit</td>
          <td>Spend authority, caps and liability have to ship before trust does, and the flagship capability, calls, does not work reliably yet</td>
          <td>Picked, conditionally. The bigger market is here, but release one is permissioning, not personality</td>
      </tr>
      <tr>
          <td>One default entry point on top of an agent network</td>
          <td>The habit, the distribution, and a take on everything routed through it</td>
          <td>You have to collapse a four-agent stack that power users are content with, and you carry the fulfilment risk</td>
          <td>The strategic prize, and the reason the productivity type is not the end state</td>
      </tr>
      <tr>
          <td>Wait for a frontier lab to own the consumer agent</td>
          <td>No distribution cost, and you ride the model curve</td>
          <td>You own neither the entry point nor the network, and the secretary type&rsquo;s hard parts — trust, payments, liability — are exactly what labs are slowest at</td>
          <td>Not picked. The hard parts are the moat</td>
      </tr>
  </tbody>
</table>
<h2 id="evidence">Evidence</h2>
<ul>
<li>xAI&rsquo;s <a href="https://aihot.virxact.com/items/cmtnbnfwj02vhrog1dgtzoar8">Haggle Bot</a>: over $100,000 in direct savings, $14,220 from 43 inactive seats, $85,662 a year of unused SKUs, and $14,629 negotiated down to $6,143.</li>
<li>Meta&rsquo;s <a href="https://aihot.news/items/cmu63zp9f09xsrofjmnxvrwdg">Muse for Mac</a> acts on the computer under explicit authorisation. Peter Yang <a href="https://x.com/petergyang/status/2101033599319613533">reported</a> that Muse saved him more than $800 a year, transcribed in the 19 September digest, including the Comcast negotiation worth $288. Nan Yu found that <a href="https://x.com/thenanyu/status/2101383106372805103">neither Muse nor Instinct would place a call</a>.</li>
<li>Peter Yang&rsquo;s <a href="https://x.com/petergyang/status/2101862331345154469">personal agent thread</a>: Muse leading, the argument that an agent living inside a chat app like iMessage makes no sense, and his own four-agent stack of Muse, Grok Bot, Claude and ChatGPT.</li>
<li>Nikunj Kothari on <a href="https://x.com/nikunj/status/2102186665863463199">Codex as daily driver versus Instinct and Muse as zero-config consumer agents</a>, and his <a href="https://x.com/nikunj/status/2106072546206773574">home-network prompt on top of an agent already running Gmail, a thermostat, DoorDash and Amazon</a>.</li>
<li>Madhu Guru, <a href="https://x.com/realmadhuguru/status/2102777931764498536">the roofer versus the clothes rack</a>: browsing clothes is entertainment for some people, hiring a roofer is torment for almost everyone. That second buyer is the secretary type&rsquo;s customer.</li>
<li>A16Z consumer numbers, reported 7 October 2026: <a href="https://aihot.news/items/tfuj58rvo46hvh8l2nzcbpf7n">half have used AI, 25% daily, 4.5% paying, top 1% at $903 a month and 19.5% of spend</a>.</li>
<li>Brian Armstrong, transcribed in the 21 September 2026 digest: card fees start near 30 cents, and 76% of the agent commerce transactions Coinbase observes fall under 30 cents.</li>
<li>Anthropic, <a href="https://www.anthropic.com/engineering/how-we-contain-claude">How we contain Claude</a>: probability falls, blast radius grows. Simon Willison, <a href="https://simonwillison.net/2026/Oct/3/default-hard-budget-caps/">hard budget caps by default</a>. California&rsquo;s <a href="https://aihot.news/items/iw7ix94rgvhp2jgamykh261gl">investigative subpoena to OpenAI</a> over agent cybersecurity risk.</li>
</ul>
<h2 id="where-this-stops-being-true">Where this stops being true</h2>
<p>This holds for US consumer and small-team agent products, on the model generation available in October 2026, at today&rsquo;s observable pricing. Six places it weakens. First, the dichotomy dissolves if the productivity agent starts absorbing chores, or the secretary agent&rsquo;s output reaches professional grade — the two types converge from opposite ends. Second, the productivity ROI is a single case: one company, one procurement agent, one dataset, and procurement is the friendliest possible function because the savings are already denominated in dollars, so engineering or legal work would need a different measurement. Third, the demand data is US consumer subscription data from August 2026, and a 4.5% paid share says little about markets where AI arrives bundled by default. Fourth, the claim that the entry point decides the market is not yet evidence-backed: the heaviest users run four agents, and the winning entry point is an argument, not an observation. Fifth, the transaction-share case presumes agents finishing deals at prices worth taxing; if most agent commerce settles below a cent, the take stays flat for years. Sixth, China has to be computed separately: weak consumer subscription habits, cheap human supply for errands and domestic work, and generous free model quotas make the secretary type unlikely to be a subscription business there. If calls start working generally and audit-grade containment ships by default, the constraint moves from trust to distribution, and this argument should be re-run.</p>
<h2 id="what-i-would-do-differently">What I would do differently</h2>
<ul>
<li><strong>Answer the anchoring question first, out loud.</strong> Am I selling more valuable output, or freer time? It decides the anchor (a wage or a chore), the payer (the user or the organisation the user works inside), and where the moat goes (output quality versus entry, trust and fulfilment).</li>
<li><strong>Build the receipt into the product, not into a case study.</strong> Haggle Bot&rsquo;s shape is right, but with n=1 the product has to generate its own auditable number per customer, or renewal dies with the first quiet quarter.</li>
<li><strong>For the secretary type, ship the cap and the permissioning as defaults.</strong> Willison&rsquo;s formulation is the correct first release: cut off at a set amount with an error, require an explicit opt-out. What is being sold before anything else is permission to act.</li>
<li><strong>Spend on fulfilment and integration, not on the model.</strong> Every concrete secretary-type example is plumbing: calls that still do not work, Gmail, thermostats, DoorDash, Amazon. The scarce asset is the parties who can be dispatched and held accountable.</li>
<li><strong>Treat the entry point as the asset to win, and the agent network as a fulfilment network.</strong> &ldquo;Agent network&rdquo; is not a protocol diagram. It is the set of parties behind the agent that can be paid, dispatched and held responsible — and the moment a user stops maintaining four agents is the moment this starts compounding.</li>
</ul>
<p>This post is part of my <a href="/en/agents/">personal AI agents guide</a>.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
