Marc Lou Calls Stripe Pay "the End of UI for SaaS". Is It?
Marc Lou quote-posted a terminal command for sending money and called it the end of UI for SaaS.
Stripe had shipped the command the day before. The docs under the launch still stop an agent and ask a person to approve. The dashboard in that path is small. It is still there.
A command, and a caption
On 27 October 2026, at 16:43 UTC (03:43 in Sydney on 28 October, AEDT), Stripe posted “Introducing ‘stripe pay’, for instant business-to-business transfers.” The same post said it was “Available in the Dashboard and CLI.” The command is stripe pay @handle 10.00 usd.
At about 07:40 UTC on 29 October 2026, which is 18:40 in Sydney (AEDT), that post had 726,816 views, 3,212 likes, 289 quotes, 165 replies, and 2,203 bookmarks. Every X count in this piece is from that read. The counts move.
On 28 October, at 12:47 UTC (23:47 AEDT), Marc Lou quote-posted the launch. The whole post is one sentence. “And that, ladies and gentlemen, is the end of UI for SaaS”. At the snapshot it had 345,094 views, 4,013 likes, 286 replies, 27 quotes, and 2,544 bookmarks. He had about 418,000 followers.
Read it as a caption. Marc Lou ships a portfolio, including ShipFast, DataFast, TrustMRR, and MailCheap. The same week he had asked whether SaaS is dead, using TrustMRR. The portfolio behind the name is a separate story. This post is not that analysis. It is one line on someone else’s launch.
What stripe pay actually is
Stripe’s docs describe a CLI plugin. “The stripe pay plugin is in preview for eligible US and UK businesses, supporting same-currency transfers in USD, GBP, and USDC.”
Senders need “a funded Stripe Treasury financial account”. Recipients need “either a Treasury financial account or a payout-enabled bank account linked to their Stripe profile.” Same page.
The launch post says you can “send funds for free”, and it uses the word instant. Free and instant is Stripe’s marketing. The send-transfer docs say a review includes “fee, delivery timing” before confirmation. Stripe’s agent skill for stripe pay, as mirrored on skills.sh, says the command “reports the fee and delivery timing before confirmation. Don’t assume that a transfer is free or instant.”
PYMNTS covered the launch on 27 October. The Paypers covered it on 28 October and noted that Stripe “has not disclosed transaction volumes.”
jack friks turned the handle into a joke at 00:07 UTC on 28 October (11:07 AEDT). “you can now send my business (me) money simply by typing into your terminal: ‘stripe pay @jackfriks’”. 135 likes at the snapshot.
A short timeline
Sydney is AEDT, UTC+11, for every time below. The 6 September post in a later section is AEST, UTC+10. Before 4 October 2026, Sydney was on AEST.
- 27 Oct, 16:43 UTC (28 Oct, 03:43 AEDT). Stripe announces
stripe pay, in the Dashboard and the CLI. - 27 Oct, 20:45 UTC (28 Oct, 07:45 AEDT). Patrick Collison, Stripe’s CEO: “A2A payments will be more important than P2P payments.”
- 28 Oct, 01:54 UTC (12:54 AEDT). Theo: if he has to go to a dashboard, he is not going to use the product.
- 28 Oct, 02:27 UTC (13:27 AEDT). Corey Quinn agrees, then adds a warning about being sold someone else’s agent. Theo answers at 02:43 UTC.
- 28 Oct, 09:42 UTC (20:42 AEDT). Marie Martens posts Tally’s chart. The 42% figure is the company’s.
- 28 Oct, 12:25 UTC (23:25 AEDT). Arvid Kahl asks for UI, MCP, and API parity. At 12:47 UTC Marc posts the end-of-UI line.
- 28 Oct, 19:08 UTC (29 Oct, 06:08 AEDT). A reply says most people cannot open a terminal.
- 28 Oct, 23:30 UTC (29 Oct, 10:30 AEDT). Pieter Levels submits Nomads.com to MCP directories. He asks for feature parity. He does not say the UI is dead.
- 29 Oct, 05:38 UTC (16:38 AEDT). Theo again, on developers who still prompt agents in a terminal. He sells a GUI for that job.
Theo will not use the dashboard
Theo Browne (@theo) posted at 01:54 UTC on 28 October. His bio calls him “Full time CEO @t3dotcodes & @t3dotchat”. About 416,000 followers at the snapshot.
“If I have to go to a dashboard to use your product, I’m not going to use your product.” The next sentence: “If anything, I’m more likely to tell Claude to rebuild your product.”
233,191 views, 3,040 likes, 342 replies, and 115 quotes.
He sells T3 Code, an agent-coding app. On 27 October he posted T3 Code v0.1.3, including a “Complete redesign of the app to look significantly better”. The dashboard complaint and the GUI are the same week. His position is that his agents should drive the tools. The polished screen is the one he sells for those agents.
At 05:38 UTC on 29 October he posted again. “It is insane to me that there are still devs using terminals to prompt their agents”. 106,582 views, 1,399 likes, 292 replies. The follow-up mocks developers who still prompt agents in a terminal. The product on sale is a GUI. Read together, he wants his agents to drive the tools.
Corey Quinn (@QuinnyPig) replied at 02:27 UTC. He is a Duckbill co-founder, about 109,000 followers, and he calls himself a “Professional skeptic”. “I really wish more folks understood this. It goes double for trying to get me to use your agent.” 29,736 views and 308 likes.
Theo’s reply at 02:43 UTC: “I like my agents, I don’t want yours… Sell me things I can give my agents. Don’t sell me a worse agent.” 91,189 views and 1,488 likes.
The rebuild line meets an argument already on the record. Levels had said software is dead, in a fight over whether software is still worth paying for. He has also been replacing SaaS with his own code. Vibe coding and shipping fast are the pages on that method. Theo’s post is about the dashboard. If that is the only way in, he would rather ask Claude for a private one.
Jon Yongfook, who builds Bannerbear, posted the joke form at 00:31 UTC on 28 October. “This is why docusign has 7 million employees. Moat.” DocuSign does not have 7 million employees. The line is satire. 42,866 views and 1,282 likes. It sits in the rebuild thread.
A company chart, then a parity argument
Marie Martens (@MarieMartens), co-founder of Tally, posted at 09:42 UTC on 28 October. About 17,000 followers. “Today, 42% of all @TallyForms are built with AI. (Tally AI + MCP)”. 12,605 views and 125 likes.
The 42% is company-reported. It comes from a screenshot on that post. It is not independently verified. The chart is titled “Published forms by how they were made”.
For the week of 19–25 October 2026 the chart shows Tally AI at 21.3% of published forms and MCP at 20.7%, against 23.7% and 1.6% twelve weeks earlier. Weekly forms on the chart are roughly 55,000 at the peak. The MCP series shows up from about mid-August.
The two AI slices together move from 25.3% to 42.0%. Almost all of that rise is MCP. In-app Tally AI slipped, from 23.7% to 21.3%. Manual building inside the app still accounts for most forms, about 58%, on the same company-reported chart. The screenshot is the source for every one of those shares.
Arvid Kahl (@arvidkahl) posted at 12:25 UTC. He builds Podscan. About 214,000 followers. “SaaS products of the future MUST present all affordances equally to humans, agents, and machines. UI, MCP, and API have to be fully interchangeable.” He also wrote that customers ask for “feature parity in the API and MCP”. 5,345 views, 76 likes, 100 replies. An earlier post that hour has a typo, “AI” for “API”. The corrected post is the one quoted here.
At 12:28 UTC he quote-posted the Tally chart. “To anyone who believes MCP as a usage vector is dead on arrival, here’s an adoption curve…” 119 likes.
Podscan sells API and MCP access. That is the interest next to the advice. At 13:31 UTC on 28 October (00:31 AEDT on 29 October) he answered a pricing question. The billing metric he named is the “number of API/MCP tool calls”. The question he was answering said “per seat pricing breaks when half the users are agents”. His reply had 74 views. It is a detail from the person who set the price.
A seat is a person. MRR turns those seats into a monthly number when the product is a subscription. The models indie hackers already use are still a monthly fee, a one-time sale, a listing, ads, or a course. Tool calls are another meter. Arvid is charging on that meter, so the recommendation and the invoice point the same way.
Levels wants the same doors, and a directory will take them
Pieter Levels (@levelsio, about 983,000 followers) did not call the UI dead.
At 12:16 UTC on 28 October he described his own setup. “The only interface is Termius SSH and then Claude Code on the server”. What comes back, in that post, is “chat responses… or websites it builds”. 77,951 views and 775 likes. The longer record is a set of products.
At 23:30 UTC (10:30 AEDT on 29 October) he wrote two practical lines and one principle. “Submitted nomads.com/mcp now to most of the MCP directories”. “I had to add OAuth login for users as it doesn’t allow just API keys”. “I agree with the philosophy that all of our apps/sites should be MCP/API accessible at feature parity”. 27,173 views, 182 likes, 139 replies.
The post quotes his 6 September launch, “Agent ready 😊”, from 15:34 UTC that day (01:34 AEST on 7 September). He is promoting Nomads’ MCP in the same thread as the parity line. Feature parity keeps the app. It adds a door an agent can use.
MCP is the Model Context Protocol. It lets an assistant such as Claude or ChatGPT call a product’s tools directly.
Marc had already answered this for MailCheap. On 27 October, at 13:11 UTC (00:11 AEDT on 28 October), he shipped MailCheap features. Someone asked “do you have MCP support?” At 17:30 UTC (04:30 AEDT on 28 October) he replied “full MCP support” and “literally anything you can do on the UI is available with your AI”.
MailCheap is his. How it started is a separate story. On 29 October 2026, mailcheap.ai had an “MCP setup” section. The code is marclou/mailcheap. He is calling UI over while shipping a UI an agent can drive. He gains, mildly, if founders take that caption as advice. The gain sits next to the one-line post.
Matthew Phillips (@matthewcp), who works on Astro at Cloudflare, posted at 14:01 UTC on 28 October. “Next step will be the expectation to register for your product without going to your website. It’s coming.” Eight likes. Stripe is already the payments tool founders name in public. The posts above were adding another door: a way for an agent to call the product.
Patrick Collison (@patrickc, Stripe’s CEO, about 1.8 million followers) had posted at 20:45 UTC on 27 October. “A2A payments will be more important than P2P payments.” He does not define A2A in the post. 202,433 views and 2,621 likes. He runs the company that shipped the command. The line is the CEO’s. The confirmation step below is the company’s docs.
The pushback was replies
The well-known posts above argue that an agent has to be able to use the product. In the posts read for this piece, they do not argue for deleting the screen. Arvid and Levels both said feature parity.
The pushback came as replies, mostly from smaller accounts. This is a sample, not a census. Replies read by this site: about 25 of Marc’s 286 replies, 24 of his 27 quotes, about 25 of Theo’s 342 replies, and 50 of Theo’s 115 quotes. No large account in that sample argued that dashboards will last. The lines below stay replies.
@_christinacodes (about 2,000 followers) quote-posted Marc at 19:08 UTC on 28 October (06:08 AEDT on 29 October). The reply says “99% of the population doesn’t know how to open a terminal” and “Dashboards aren’t going anywhere”, for people who are not technical. 34 likes. It was the top quote-post on Marc’s post at the snapshot.
@OInnocxnt (about 2,900 followers) replied: “does your average brick and mortar store know what a terminal is?”
@buildwithjoe97 (131 followers) replied on Marc’s post, around 07:00 UTC on 29 October (about 18:00 in Sydney). “ui didn’t die, it moved to the approve button”. That sentence matches the docs. It is still a reply from a small account.
@xautomator999 (0 followers) replied: “Approvals, invoices, the audit trail. Nobody puts those in the launch video.”
@JanKutschera (about 7,000 followers) replied: “When the agent does the work, its output becomes the interface, and almost nobody designs that part.”
@maxfabi_u (6 followers) replied: “entire industries are so far away of doing everything via chat”. A field anecdote from a tiny account.
@robindarlington (654 followers) replied: “there is still room for creative / interesting UI work”.
@CryptoMentionss (278 followers) replied: “when an agent is the user, your API docs and error messages are the UI.”
The approve button is in Stripe’s docs
The send-transfer page is the quiet half of the launch.
“Agent and JSON modes return a confirmation_required response before sending money.” An agent may rerun with --yes only “after the user confirms those details.”
If the result is status: approval_required and an approval_url, the agent has to “give the user the approval link and wait for them to approve or reject.” The other branch is an approvals_dashboard_url. “Resumable approval requests expire after 5 minutes.”
There is a dry run. --dry-run validates the flow “without creating or sending the transfer.”
The product in Marc’s caption ships with a Dashboard. Stripe said so in the launch post. Agent payments in the docs go through a person. The link expires in five minutes. The fee and the delivery timing are part of the review. What is left of the interface, on that path, is look, then approve.
Hacker News barely touched it. The submission titled Stripe Pay had 6 points and 0 comments. Two other submissions drew 1 or 2 points. The argument stayed on X.
What a solo SaaS can copy, and what it should keep
The concrete moves are the ones people named.
Ship an API, a CLI, or an MCP server next to the UI. Levels, Arvid, and MailCheap each described that job: the agent can do what the screen can do. Arvid’s word is interchangeable. Levels’ word is feature parity.
Support OAuth when a directory will not take only an API key. Levels said he had to add OAuth login for users, because the directory “doesn’t allow just API keys”.
Price the caller if the caller is an agent. Arvid bills Podscan by the “number of API/MCP tool calls”, and he sells that access. A per-seat MRR count assumes a person. Copy the meter with that interest in view.
Offer a dry run. Stripe’s --dry-run flag validates the flow “without creating or sending the transfer.” The @CryptoMentionss reply, from a small account, says that when the agent is the user, the docs and the error messages are the interface.
The screens a person still needs. Approvals, invoices, an audit trail, billing. The @_christinacodes reply is about people who are not technical. The zero-follower reply is the one about approvals, invoices, and the audit trail. Stripe’s approval link is that step, with a five-minute expiry.
The dashboard shrinks to the button
Marc wrote a caption. Theo wrote a preference for his own agents, from a CEO who sells those agents a GUI. Levels and Arvid asked for the same features on the UI, the API, and MCP. Tally’s chart, company-reported and unverified, says MCP was 20.7% of published forms in the week of 19–25 October, and that most forms were still made by hand in the app.
If an agent can drive the product, it can also set the product beside a rebuild. That is the line from the software-is-dead argument to Theo’s “rebuild your product”. Parity is the minimum these builders treated as obvious. The screen that remains is the moment a person checks the fee, the recipient, and the record, and approves.
What do you think this means for indie hackers building SaaS?
A note on the numbers
X counts here were read at about 07:40 UTC on 29 October 2026 (18:40 AEDT). Follower counts are from that same read, in the rounding they were recorded: Theo about 416,000, Marc about 418,000, Corey Quinn about 109,000, Arvid Kahl about 214,000, Marie Martens about 17,000, Pieter Levels about 983,000, Patrick Collison about 1.8 million. Smaller accounts, as recorded: @_christinacodes about 2,000, @buildwithjoe97 131, @xautomator999 0, @JanKutschera about 7,000, @maxfabi_u 6, @matthewcp about 5,000, @robindarlington 654, @OInnocxnt about 2,900, @CryptoMentionss 278.
Tally’s 42%, the 21.3% and 20.7% split, the twelve-week comparison of 23.7% and 1.6%, the move from 25.3% to 42.0%, roughly 55,000 weekly forms at the peak, and about 58% still built in the app are company-reported, from Marie Martens’ chart for the week of 19–25 October 2026. They are not independently verified.
Theo runs T3 Code. Marc’s MailCheap offers MCP. Arvid prices Podscan by API and MCP tool calls. Patrick Collison is Stripe’s CEO. Levels was submitting Nomads to MCP directories in the same post as the parity line. Those are the interests beside the sentences. The pushback quoted above is replies, not a panel.
FAQ
What is Stripe Pay (`stripe pay`)?
Stripe Pay is a CLI plugin and a Dashboard feature for instant business-to-business transfers to another business's Stripe profile handle. Stripe's docs say the plugin is in preview for eligible US and UK businesses, for same-currency transfers in USD, GBP, and USDC. The 27 October 2026 launch post said it was available in the Dashboard and the CLI.
Did Marc Lou say SaaS UI is dead?
On 28 October 2026 he quote-posted Stripe's launch and wrote: "And that, ladies and gentlemen, is the end of UI for SaaS". It was a one-line opinion. His MailCheap product has a user interface and advertises MCP.
Can AI agents send money with `stripe pay` without a human?
Stripe's docs say agent and JSON modes return a confirmation_required response before sending money. The command may be rerun with --yes only after the user confirms those details. Some transfers also return an approval link, and resumable approval requests expire after 5 minutes.
What is MCP, and why are indie hackers adding it?
MCP, the Model Context Protocol, lets an AI assistant such as Claude or ChatGPT call a product's tools. Tally co-founder Marie Martens said MCP accounted for 20.7% of published Tally forms in the week of 19–25 October 2026, up from 1.6% twelve weeks earlier. That split is company-reported, from her chart. Pieter Levels has added MCP to Nomads.com, and Marc Lou says MailCheap has full MCP support.
Should a solo SaaS drop its dashboard?
The posts in this debate do not say to delete the dashboard. Arvid Kahl and Pieter Levels argued for feature parity across the UI, the API, and MCP. Replies from smaller accounts said most people do not use a terminal, and that approvals and billing still need a screen. Stripe's own stripe pay docs still require a person to confirm an agent payment.