← Back to Insights

Insight

The Free Agent Has a Boss

Ariel Agor
•
The Free Agent Has a Boss

Listen · Read by Leo · click any word to jump

0:00 / —· loading…

On September 29, 2026, Meta opened its Muse agent to small businesses. TechCrunch reported a free tier with usage limits and paid plans for heavier use. The integration list is long: Shopify, Dropbox, Slack, Asana, Box, Canva, Figma, Granola, HighLevel, Intuit QuickBooks, Klaviyo, Lovable, Notion, Stripe and Zoom. Muse also plugs into Instagram professional analytics, Facebook pages and Meta ad accounts. Meta's line for the launch was well written: "Small businesses have been growing on our apps for nearly two decades. They told us they're short on hours, not ideas."

That line is true, and it is also a sales pitch. The company that makes most of its money selling attention to small businesses now offers to run their operations for free. The agent it hands them can read the QuickBooks file, the Stripe payouts, the Shopify catalogue and the ad account, all in the same session.

Thirteen days earlier, on September 16, OpenAI announced Sponsored Agents, a ChatGPT ad format where a shopper opens a conversation with an AI stand-in for a business. Alongside it came AI tools that build ads from a plain-language prompt and official HubSpot and Shopify integrations, according to OpenAI's help documentation and coverage of the launch. The same week Google announced a Business Agent beta for YouTube ads, as tracked in Lilach Bullock's weekly roundup of small business AI news.

Line those three launches up and you get the most important fact about AI workflow automation for small businesses this fall. The cheapest, best-integrated agents on offer come from the three companies that also sell the owner's advertising. They are free because the owner is the customer of a different product. The agent that closes your books has a second employer, and the second employer sends you an invoice every month for clicks.

My argument is narrow, and I think it holds up. Small business owners should take the free agents. They should also decide, on purpose and in writing, which agent is allowed to see the margin. Most will skip that decision, because the free agent already asked for every permission during setup and the owner clicked yes.

Who pays for the free agent

A free tier is a budget line inside someone else's company. Somebody at Meta signed off on the compute that Muse burns while it reconciles a bakery's Stripe deposits. That spend has to come back from somewhere, and Meta has told you where it expects to find the money. Muse connects to Meta ad accounts. Meta's pitch talks about helping owners "find new customers." Finding customers, at Meta, has always meant buying ads.

I am not accusing Meta of anything sinister. The arrangement is old and familiar. Google gave away Gmail and Maps. Meta gave away Facebook pages to every restaurant in America. The deal was always attention for service, and the owners who took it mostly did well. What changed this month is the depth of the access. A Facebook page knew what you posted. An agent wired into QuickBooks and Stripe knows your gross margin, your best month, your cash cushion, and how much you can afford to spend before payroll.

Picture the negotiation from the seller's side of the table. Every ad platform runs an auction, and the price you pay depends on how badly you want the slot. For twenty years the platform has guessed at your willingness to pay from your bidding behaviour. An agent with read access to your books does not have to guess. The data may be walled off inside Meta, and Meta may promise never to use it in ad pricing. The owner still cannot audit that promise, and nothing stops the next version of the agent from recommending, helpfully and with charts, that this is a great week to raise the ad budget.

The agent's advice and the platform's revenue point the same way. Advice from a counterparty can still be good advice, and owners should simply treat it as coming from a counterparty.

The pitch sounds like an employee

Meta's description says Muse understands what a business sells, its brand voice and the questions customers ask most. That is the language of hiring. Owners will hear it that way, because the agent shows up in the place where an operations hire would sit. It drafts the reply to the angry customer. It reorders stock. It writes the email campaign in Klaviyo and then suggests boosting it on Instagram.

An employee who also took a commission from your largest supplier would have to disclose it. The free agent's commission is built into its business model, and the disclosure lives in a terms of service document nobody reads. I would not call that a scandal. It is simply a structure, and the owner who sees it clearly makes better choices than the owner who thinks they hired a free assistant.

Amazon showed where the agent's reach ends

The second lesson of September came from a fight between giants that most small business owners watched with mild interest. Meta launched the Muse app on September 8. It hit the top of the US and Canadian app charts within days, per TechCrunch. On September 20, Amazon began blocking it. The Rundown reported that Amazon acted after Meta declined its request to pull the bot, and that users who tried to shop with Muse saw a notice saying the agent's access violated Amazon's terms. Amazon's position, as quoted, is that "purchasing apps should respect merchants' decisions about whether to participate."

Amazon also complained that Muse did not identify itself while browsing and raised concerns about customer credentials, according to GeekWire's account of the standoff. Meta says credentials are stored securely and that Muse cannot see passwords or payment methods. Meta has partnered with Walmart, GameStop, Sephora, Expedia, OpenTable and Shopify. Amazon refused.

The Rundown put a number on the motive. Amazon's advertising business runs at roughly $68.6 billion a year, and a shopping agent that skips sponsored listings skips the toll booth. The legal ground under all this is still moving. In August 2026 the Ninth Circuit vacated Amazon's preliminary injunction against Perplexity's Comet shopping agent and sent the case back for more proceedings.

Small business owners should take one fact from this: an agent's reach is set by the permission of whoever owns the other end of the connection, and those owners decide based on their own ad revenue. When a workflow runs through Muse into Shopify, it runs on a truce between Meta and Shopify. When the workflow touches a supplier on Amazon, it ran on a truce that ended on September 20.

A small business that builds its order flow, its supplier reorders or its price checks on one giant's agent has bet its operations on that giant's diplomatic relations. The giants will fight more, because agents are the new storefront and every storefront has a landlord. The owner can't stop those fights. What the owner controls is how much of the business sits in the blast radius when the next one starts.

The integration list is a foreign policy

I read Meta's list of fifteen integrations the way I would read a treaty. Each name is a company that decided, for now, that letting Meta's agent in serves its interests. Shopify has been open about wanting agents to check out. Intuit and Stripe have every reason to be inside the agent that small businesses use. Any of those deals can be renegotiated, and the owner is not at the table when it happens.

None of that argues against using Muse. It argues for knowing which of your workflows depend on which treaty, so you are not finding out from a pop-up in the middle of a Saturday rush.

Half the work fails, and the agent says it finished

The third lesson came from a benchmark, and it matters more than either launch. Zapier runs AutomationBench, a public test of whether agents can complete real business workflows. It covers more than 600 held-out tasks across 47 simulated applications and about 500 API endpoints, in six business areas: sales, marketing, operations, support, finance and HR. It scores the final state of the systems, so the grade depends on whether the CRM record, the invoice or the ticket actually ended up right. No language model is asked to grade the work.

When I checked the leaderboard this week, the top entry was Google's Gemini 4 Argon on high effort at 51.29 percent, at $1.70 per task. Claude Sonnet 5.5 scored 44.75 percent at $1.14 per task, and it led the finance category at 50.0 percent. The best agent available to anyone, at any price, completes about half of realistic business workflows correctly.

The detail that should change how an owner sets up automation is buried lower on the page. Zapier found that 72 percent of Opus's failures, 91 percent of Gemini's and 84 percent of GPT-5.4's involved false confidence: the agent reported the task as done while the final state was wrong.

Read that from the owner's chair. A company with an operations team has someone who notices that the invoice went to the wrong address. A five-person shop doesn't. The owner is the operations team, and the owner turned on the agent precisely so they could stop checking. An agent that fails loudly costs you an afternoon. One that fails quietly and reports success costs you a customer, a tax filing, or a month of revenue booked to the wrong account before anyone looks.

This is where the free agent and the ad model meet again. The free agent's maker has strong reasons to make the agent feel competent and pleasant, since a delighted owner stays on the platform and buys more ads. It has weaker reasons to build the tedious checks that would show the owner how often the agent got the reconciliation wrong. Nothing about this requires bad intent. It is the ordinary pull of incentives, and the Zapier numbers show the cost of following it.

AI workflow automation for small businesses needs a loyalty map

Here is the practical part. AI workflow automation for small businesses works now, it is cheap, and owners who ignore it will lose to rivals who don't. The free agents from Meta, OpenAI and Google are good tools. The job is to put each one where its loyalties match the work.

I sort a small company's workflows by one question: if the agent's maker profits when this workflow goes a certain way, does that hurt me? Customer reply drafts, social posts, campaign copy and ad creative mostly pass the test. The ad platform wants good ads too, because good ads keep you buying. Let the ad company's agent do ad company work.

Bookkeeping, pricing, cash forecasting, supplier selection and payroll fail the test. Each of those workflows contains a number that a seller of ads would like to know: how much you can spend, how desperate you are for growth, how thin your margin runs. Those workflows belong on an agent you pay for directly, from a vendor whose revenue comes from your subscription and not from your ad budget.

Pay for the agent that reads the ledger

The prices are now low enough that this is an easy call. OpenAI's API pricing for GPT-6 Luna sits at $0.10 per million input tokens and $0.50 per million output, and GPT-6 Sol at $2 and $10, per the Bullock roundup. Anthropic shipped Claude Opus 5.5 on September 22 with what it described as 40 percent lower cost on typical workloads. A small business can run its month-end close through a paid model for less than the cost of one bookkeeping hour. The paid relationship buys you something the free tier can't: a vendor whose only customer in the transaction is you.

The paid route has its own risks. Paid vendors change prices too. The same roundup notes that Microsoft made usage-based billing the default for new Microsoft 365 Copilot Business licenses, effective November 2, and that OpenAI set December 11, 2026 as the retirement date for Custom GPTs. Every vendor reprices, and every vendor retires products. The difference is that a paid vendor reprices in the open, on an invoice you can read and refuse.

Build the check the agent cannot grade

Given Zapier's false confidence numbers, every workflow that touches money needs a check the agent did not write and cannot mark as passed. For a small business this can be crude and still work. The agent posts the reconciliation, and a separate rule compares the bank balance to the books every morning and texts the owner when they disagree by more than fifty dollars. The agent sends invoices, and a weekly report lists every invoice that has gone unopened for ten days.

None of this needs a developer. It needs the owner to accept that "done" from an agent is a claim to verify, and to spend one afternoon wiring the verification. The owners who skip that afternoon will be the ones explaining a bad quarter to their accountant in April.

Keep the map of the work in your own hands

The most valuable thing a small business builds during automation is its description of how the work runs. The agent itself is replaceable. Which steps happen in what order, which exceptions matter, which customer gets the discount and why: that map is the business, written down for the first time. If it lives only inside Muse's memory, or inside a Custom GPT that retires on December 11, the owner has handed the company's operating manual to a vendor and kept no copy.

Write the workflows down in plain documents you own. Store them in your own Notion or Google Drive. When the agent changes, or the truce between platforms breaks, or the free tier shrinks, you point a new agent at the same map and keep going. That single habit turns a vendor dependency into a vendor choice.

The subsidy will reprice

Free tiers are a customer acquisition cost, and acquisition costs end when the customers are acquired. Meta announced its Meta Enterprise Platform on September 28, the day before the Muse small business launch, with former MongoDB CEO CJ Desai leading it, per TechCrunch. A company building an enterprise division intends to sell software, and companies that sell software eventually charge for it.

I expect the Muse free tier to stay generous for a while, because Meta wants the integrations to become habits. Once the habits form, the usage limits will tighten, and the paid plans will look reasonable next to the cost of rebuilding everything elsewhere. Gmail did not get worse when Google got serious about Workspace. It got more expensive for the people who needed it most.

The owner who sorted workflows by loyalty, kept the map in their own files and built independent checks will treat that repricing as one more vendor decision. The owner who let one free agent absorb the whole back office will find out that switching costs grew quietly while the agent was being helpful.

Draw the map before you click yes

The setup screen for every one of these agents asks for permissions in a friendly sequence, one integration at a time, and each yes feels small. By the end the agent can see everything, and the owner has made a structural decision about the company without noticing it was a decision.

That is why buying a tool won't solve this. Turning on Muse takes ten minutes, and anyone can do it. The hard part, and the part that decides whether the automation makes the business stronger or just more dependent, is the design underneath: which agent serves which workflow, which data crosses which line, which checks catch the quiet failures, and where the map of the work lives when the platforms fight. Those choices compound, and once they are made they are expensive to unwind.

Agor AI Advisory does that design work with owners and operators before the permissions are granted. We map your workflows by loyalty and cost, split the ad-side work from the ledger-side work, choose the paid models that should see your margins, and build the independent checks that the Zapier numbers say you need. You keep the map. You keep the leverage. The free agents still do the work they are good at, inside limits you set.

The agents arriving this fall are capable and cheap, and each one reports to someone. Decide who that someone is before they decide for you.

Sources

Which Workflows Can the Ad Company's Free Agent Touch?

This table checks the post's central claim that small-business workflows split cleanly by whether the agent's maker profits from how the work goes. After 15 seconds the reader should see that ad-side work passes the loyalty test and ledger-side work fails it.

  • Ask one question of every workflow: if the agent's maker profits when this goes a certain way, does that hurt me?
  • Let the ad company's agent do ad company work. Keep the ledger with someone who only bills you.
  • Advice from a counterparty can still be good advice. Just treat it as coming from a counterparty.
What the maker could gainPasses the loyalty test?Where it should run
Customer reply draftsLow risk, and the free tier saves real hours.Little. Good replies keep the owner on the platform.YesFree ad-platform agent
Social posts and campaign copyLet the ad company's agent do ad company work.Little. The platform wants good content too.YesFree ad-platform agent
Ad creativeThe maker's incentive and the owner's goal point the same way.Little. Good ads keep you buying.YesFree ad-platform agent
Bookkeeping and cash forecastingA small monthly fee buys a vendor whose only customer in the transaction is you.A view of how much you can spend and how thin your margin runs.NoPaid agent from a vendor funded by your subscription
Pricing, supplier selection and payrollCosts more than free, but the advice comes from someone with no ad budget to win.A view of how desperate you are for growth.NoPaid agent from a vendor funded by your subscription

Source: The loyalty test and workflow sorting described in the post 'The Free Agent Has a Boss' (Ariel Agor, October 1, 2026), section 'AI workflow automation for small businesses needs a loyalty map'. No outside data added. · verified · as of 2026-10-01

Want this kind of automation working for your business?

Agor AI designs and ships the systems these posts describe, scoped in weeks, not quarters.

Book a Free Strategy Call