Recent posts that drew 100 reactions or more and say something a peer would learn from, most reactions first. Click any post to open it on LinkedIn.
Notes From the HubSpot Refounding, Day 1:
Yesterday (November 12th, 2026), Brian Halligan came back as CEO of HubSpot and we declared that it was the refounding of HubSpot. You can get to the original post by visiting refounding .com.
Here are some thoughts/notes for those following along at home, that are curious:
1) Yesterday, we had an all-hands meeting (I've stopped calling it the "all-minds" meeting because that term never stuck). We did it live from Brian's place. I opened and then passed it to Brian who did the main presentation. I've seen Brian give a *lot* of presentations. He's very good at it. This was one of his better ones. I live-Slacked his presentation in the company Slack channel while he was giving his presentation a few feet away. It was fun -- and funny (I hope). There were hundreds of people posting to Slack live. It wasn't just me.
People loved the presentation. Really positive response. The energy was palpable.
HubSpot is ready for a refounding. I'm excited!
2) A common question we've gotten from folks in the community: "What does refounding mean? What will actually change?"
We are reimagining, rethinking *everything*. The core question we're asking ourselves is: "Selves, if we were starting HubSpot today, knowing what we know, what would we do?"
To start with, we're sharpening the product vision. We are leaning strongly into a headless version of HubSpot. This means that an increasing amount of HubSpot's capabilities will be consumable by AI agents and AI harnesses (like Claude and ChatGPT) via MCP. We're shifting significant resources towards that vision. It's how people increasingly want to use/access HubSpot and we hear that loud and clear.
3) After the presentation, Brian and I had a celebratory founders' dinner. Talked about a lot of things. But there's one overarching thing. We both agreed that we should BE BOLD. Take risks and don't hold back from necessary change and short-term sacrifice as long as we think it Solves For The Customer long-term.
So, we are now on Day 2. Stay tuned for more updates.
If you have questions, comments or feedback, just drop them in the comments.
Cheers.
#HubSpotRefounding

I talked with Joe Schmidt IV on the Andreessen Horowitz podcast to talk about the opportunities in software and why I'm so excited.
Some points I make in the episode:
1. The interface is a means to an end. For business software, the value is in the work that gets done. AI assistants are becoming one more great way to reach that work, the way browsers were for the web. AI harnesses are the new browser.
I didn't say this in the episode, but wish I had: MCP (Model Context Protocol) is the new HTTP. If you aren't making your software product composable and callable by AI harnesses, you're going to miss this wave.
2. Don't use inference to solve something a query can solve. Structured data still matters. If you want to know who your top customers last quarter were, that should be a structured query with a deterministic response, not inference over a bunch of unstructured data presented as context to the LLM.
3. Don't use a frontier LLM to to do something a decision model (like JEV) can do.
4. AI is software. Really smart software, but software. It opens up a whole new class of problems to solve at every layer in the stack, so the opportunity is bigger than it's ever been.
What a time to be a building software!
---
Link to the full episode in the comments.
Hope you find it useful.
If you have any questions, happy to answer them here. Just leave a comment.
Notes From the HubSpot Refounding, Day 3 (Saturday):
Things are cranking along and the emails between me, Brian Halligan and Duncan Lennox have been flying.
Our vision is getting sharper, clearer and simpler.
You know how sometimes you read words on a page and it JUST CLICKS? Have had that feeling multiple times this weekend.
On a related note, we also revisited the HubSpot mission. That's something that we've decided to keep the same. But we're going to simplify the language a bit.
From: Help millions of organizations grow better.
To: Help millions grow better.
Shorter (by 17 characters, 2 tokens), simpler and actually fits better too. A lot of the people we're seeking to help are not necessarily full-on organizations.
Every word now carries its weight (or as the cool kids like to say, "is load-bearing").
Help: At the heart of HubSpots' ethos -- to be helpful.
Millions: We're not here to serve the Fortune 500, but the HubSpot 5 Million.
Grow: What we're here to do is help drive growth.
Better: In v1, better meant "with inbound marketing". Now, it means "with AI".
I know some might be thinking: As HubSpot (re)founders, don't you have better things to worry about than dropping 2 words from your mission statement?
Possibly, but I don't think so.
One thing I've learned in my 30+ years as an entrepreneur:
Words matter.
(also, subtraction of words matters too.)
#HubSpotRefounding

Notes From the HubSpot Refounding, Day 2:
Another big day as we plan, ship, adjust and adjust again.
One thing I'm learning as we dig into this is the *brand* of HubSpot.
In our early years, we punched above our weight-class when it came to brand.
Back then, one of the internal aspirations we set for ourselves was this...
Make HubSpot:
Easy to buy.
Easy to use.
Easy to love.
This was on a slide I used all the time (and I think I may have shared publicly a few times like a decade ago).
As part of the #HubSpotRefounding, Brian Halligan and I are working to get back to this.
1) Easy to buy: Simplify pricing considerably and reduce the "jaggedness" as customers need key features. Make the pricing smoother so price goes up as value/usage/consumption goes up.
2) Easy to use: Simplify the core product and double-down on both Breeze and our MCP connectors for Claude/ChatGPT. More and more people are happier using HubSpot in that way. Sometimes the interface that we so fastidiously worked on for years just needs to fade into the background.
3) Easy to love: Lean in to the human side of HubSpot. It's the thing that we were defined by in our early years. We cared deeply about truly democratizing technology and made the investment to *teach* millions and help them grow better. We're going to bring that back -- but now, instead of inbound marketing, it's AI.
The tricky part about the refounding is that we want to balance the idea of bringing back some of the fundamental things that made us different that are still relevant today while resisting the temptation to just do the same things over again.
For example, in the prior generation of HubSpot we got really good at designing a classic web interface that was approachable for SMBs. Now, we need to recognize that the interface is not the value -- it's the gateway to the value that HubSpot provides. And, a hybrid conversational/chat interface is a better gateway to that value. It's going to be uncomfortable for some -- but necessary.
Keep the comments and feedback coming (just leave a comment). We're all learning a lot in this process of refounding in public.
Confession: Let's keep this between us friends, but thinking out loud in public is actually a great way to spread the message *internally* too.

This week, there was a major issue with PHP, a core technology used in hundreds of millions of websites and web applications.
HubSpot was not one of them (we don't use PHP in our website/CMS product or our core CRM applications).
That's not what this post is about. That's just us getting lucky.
Every major software company on the planet uses some of the core primitives -- often open source -- to power their applications. Many have been around for decades. Examples include MySQL or Postgres for the database. PHP, Python, TypeScript and Java for languages.
So, if you were not impacted this week, that's great. But the lesson here is not choice of technology, it's choice of technology strategy.
I'm talking about the "buy vs. build" decision that has become increasingly elevated in the age of AI.
Yes, you can build a lot of software now and much more inexpensively with modern agentic coding tools.
But the main question to be asked here is not:
"Who should build the software that implements a given set of features?"
The question is: "Who owns the problem when there's a failure?"
Who gets the call at 2am on a Tuesday if something goes wrong? It doesn't even have to be a major security issue like we had this week. It could just be a simple "the system had an owie (a technical term) and is not working like it should".
The issue is not that you or your team can't whip up a software product over a weekend that replaces the parts of a commercial product that you actually use.
The issue is you also need a team that will can be woken up on a weekend if something goes wrong.
When you pay for software, you're not paying just for lines of code (which are easy to produce these days), you're paying for sleep not lost for your team. If they are going to lose sleep, it should be for something that creates direct value for your customers, not for saving the relatively little you are likely paying or would pay (on a relative basis) for a commercial product.
If you can buy software from a company you trust, you should buy it.
Only consider building if nothing close to what you need is buyable or you're spending 100X more money than you think it would cost you to have a micro team (at least two people) to build/maintain/babysit the product.
Agentic code is free like a kitten is free -- and considerably less cute and cuddly.
Being co-founder/CTO of HubSpot, I'm remarkably biased on this. But I'm also right.
p.s. If you're looking to for a CRM from a company you can trust, check out GoHubSpot .ai and sign-up for the free edition (that's my personal landing page - #FounderLedGrowth ftw).
What I dislike more than AI Slop is what I call "AI Foam".
AI Foam: Communication that lacks the shape and substance of the person behind it.
It's when generally smart, insightful people send you something that is AI generated and lacks their usual sharp insight or point of view.
AI slop is easy to ignore because it's often just random people posting random stuff online -- often as content or comments.
AI foam is more insidious because these are people you know and respect and you know they're capable of critical thinking and clear communication.
I call it AI Foam because it lacks shape and substance.
p.s. For convenience, if you need to get to this post, you can go to aifoam .org (it redirects to this page).
