Well ads

Well now connects to Qonto over MCP, live today. Your Qonto accounts, balances and transactions flow straight into Well. Well categorizes each transaction and builds the journal entries underneath. Once you approve a supplier invoice, Well sends the PDF back to Qonto, attached to the matching payment. From there, Well links your Qonto data to the rest of your stack. It matches Qonto transactions to the invoices in your other tools, pairs your Stripe payouts with the incoming transfers that settled them, and puts anything that doesn't match in a review queue. It dedupes as it goes. A supplier that shows up in Qonto, Stripe and your inbox becomes one company in Well, not three. A transfer between your own accounts is recognized, not counted twice. One graph, one version of every entity. Setup is a single approval on Qonto's screen through OAuth, nothing to copy or paste. Qonto's MCP does the rest. Our founder Maxime helped build Qonto before starting Well, and today Well is a certified Qonto partner. Building on Qonto's MCP was a natural next step. Thanks Romain Goueffon and Fanny LavertyFanny Laverty for the partnership 🤝

I fired my accountant and built my own bookkeeper agent. Tens of thousands of dollars a year, and I was still spending a lot of time doing data entry and sharing business context. What actually bothered me wasn't the invoice; it was that I was doing most of the work. Every month I'd retype context my own tools already had into intake forms that were lossy on the way in, and none of it came back as connective tissue. My business context never accumulated. So I spent a few evenings in July rebuilding it with Well 𝗧𝗵𝗲 𝘀𝗲𝘁𝘂𝗽 >> Well holds everything now: Mercury, Chase, QuickBooks, and Gmail for the receipts. Transactions categorized, counterparties resolved to real people. >> QuickBooks stays the system of record, and agents do the execution on top: reconcile cash against AR, build the P&L and runway view, compute the quarterly estimated tax. >> It runs in shadow mode, diffed against the old numbers every morning, so I see where it disagrees. All that context was already sitting in those systems. Nobody had connected them. And to be clear about what I fired: not the CPA. Categorization, reconciliation, data entry, prepping a form, none of that needs a license and all of it standardizes. The judgment on a filing position, the signature, and knowing your situation well enough to tell you no, that doesn't. I'll pay for that all day, just not for the part a model does in a morning. Which is why accounting is the most obvious roll-up in professional services right now, and the private equity opportunity is in plain sight. Buy the firms, put one agentic back office underneath all of them, take 90% of the execution out of the CPA's week, and keep them for the two things people were paying for anyway. So the CPA doesn't go away. The work underneath them does. If you write code, connect your own sources to Well and point an agent at the output. Maxime Champoux and his team have been in it with me the whole way.

We ship more in a week than we did in a month 3 months ago. Not because we hired more people. Because the job changed. Paul Graham's "Founder Mode" said stay in the details. Don't delegate to managers who lose the plot. Chesky was right. But the details moved. They used to be lines of code, architecture decisions, pull request reviews. Now they're agent instructions, trust calibration, memory systems, and the org design that holds a hybrid workforce together. Karpathy runs 10 to 20 concurrent AI agents. Steinberger runs 5 to 10 on main with no safeguards. I run 28 named agents with soul documents, graduated trust, and a feedback loop that compounds corrections across sessions. Same discipline founders always needed. Applied to machines instead of humans. I'd call it managentic mode. Management plus agentic. Harder than coding, not easier. And the founders who figure it out first will compound an advantage that looks like magic from the outside and looks like management from the inside. I wrote about what this shift looks like in practice, what gets lost in the transition, and why the real question isn't whether to stay in the details. #foundermode #managentic #aiagents #buildinpublic

Your API's next customer isn't a developer. It's an AI agent. Cloudflare compressed 2,500 endpoints into 2 MCP tools. The $15B integration market is restructuring around AI-native orchestration. I wrote about why the connector economy is the next platform war. #MCP #AI #SaaS #Automation #Startups

Well is now officially available in Claude. Open Claude's connectors, pick Well, sign in once. That's it. From there, Claude has your business, not just your books. Your banks, invoices, emails and CRM feed the same graph, so you can ask for your runway, your cash position, or which customer went quiet after their last invoice, and the answer comes from live data rather than last month's export. It acts too, with your approval on every step. Draft an invoice, log a supplier. And since Well already speaks to your accounting stack, you can set up an agent in Claude that pushes an approved invoice through to Pennylane. Every call is scoped to your workspace and checked against a deny-by-default policy. Claude sees what you granted and nothing more. We built Well MCP-native from day one. Today the assistant side caught up.