Co-founder/CTO, HubSpot ($HUBS). Mission: Help millions grow better. Publish https://xitter.cf/t.co/sgeuiJi7wU newsletter (2M+ subscribers). Building: https://xitter.cf/t.co/L5T2SOqHJZ (Solo CRM)
Boston, MA
Joined March 2008
- Tweets24K
- Following785
- Followers602K
- Likes3.3K
Pinned Tweet
I soft-launched YouSpot yesterday (via a tweet).
YouSpot is an AI-native Solo CRM.
Fortune favors the focused.
So, here's who YouSpot is NOT for:
1) If you have a GTM team (marketing/sales) and looking to grow, YouSpot is not for you. Buy HubSpot.
2) If are an e-commerce store, YouSpot is not for you. Product is focused more on B2B and "high consideration" purchases.
3) If you have raised venture money, you should look into HubSpot for Startups. That's the right product.
4) If you're hoping for an open source project that you can run locally, and connect your own local models and use the Karpathy wiki style knowledgebase -- you are *awesome*, but YouSpot is not for you.
5) If you're trying to manage your personal stuff and family life -- I honor you, but YouSpot is not a B2C product. It's meant for 1-person companies (businesses being operated by a single human).
6) If you're worried about connecting your Gmail and other systems to a third-party app you didn't build yourself -- I respect your worry. The world is a scary place. But YouSpot is probably not for you (you're not going to get value without connecting third-party systems that can be used to build your second brain).
Other than that, would love to have you as a beta user! :). Just go to YouSpot.com. Waitlist for the free private beta, or skip the line by coming a $1/month subscriber (first 1,000 users and we're already 547 in).
Building this in public, so if you have questions around what's in my head (and what's in my second brain), just reply to this tweet and ask.
Cheers.
I thought this was funny.
Though for the record, I don't think I've ever hung out at a bar. I'm not that cool. :)
dharmesh retweeted
"We asked 10K what CRM should we use?
It said to stick with Salesforce. But it said if we were starting over, it would look at HubSpot and Attio, and Affinity for @saastrfund.
But most importantly, it said not to leave or migrate. "Keep Salesforce".
👉 If you want to steal a customer from a competitor, you gotta convince the agents. Not just the humans."
dharmesh retweeted
You can now build software that looks ready for a million users before you've learned what one person actually needs.
That's a dangerous amount of room to fool yourself.
Find people already doing the work. Give them early access. Watch what happens when they try to use your product in ways you never anticipated.
The faster you can build, the sooner you need contact with reality.
dharmesh retweeted
99.3% of the people telling you that “distribution is the only moat remaining” have never distributed anything except that opinion.
dharmesh retweeted
The biggest misread of anyone predicting the end of software engineering was imagining that the world only needed a certain amount of software, and bringing automation to the field would reduce the need for labor.
Exactly the opposite is happening where essentially most things are actually turning into software. Because agents can use tools, work with computers, write software on the fly, and process data like humans (but far faster), we can now throw “software” at problems that never could reasonably be digitized before.
What that leads to is the role of engineering taking on greater importance in the economy, because we can now engineer far more systems and processes than were possible before.
If you’re a bank trying to do new forms of trading, engineers are often your first bet. If you are in life sciences, you expect more and more research and lab work to be engineering centric. If you’re in manufacturing, you’re trying to automate more of the supply chain, all that is engineering. More and more work is shaped like software problems.
Yes we’re not going to be coding manually in the future. But almost everything will be code, which means those that understand it are in a fantastic position.
Some observations about the "total" automation of software engineering:
1. There are more software engineers now than in 2025, and demand is growing.
2. Software engineers have never worked harder than they do now.
3. They largely don't write code anymore, agents write ~100% of the code.
4. The bottom line of the companies that employs these engineers and agents (i.e. the terminal purpose of all this code) is typically not budging as a result of AI adoption.
This is why you have to think in terms of systems. Automating one aspect of a system creates its own friction and moves the bottlenecks elsewhere.
dharmesh retweeted
I don't give many interviews these days. This was surprisingly fun.
My friend @RezaSatchu interviewed me for @HarvardHBS and seeing some of these clips just makes me laugh. He really knows how to pull it out of me.
This is so me. Allergic to conventional wisdom.
dharmesh retweeted
The importance of TAM expansion
Late night chat with @nakul led to a discussion about TAM expansion.
tldr Every great company needs to constantly and continuously expand their TAM and launch products / services that go after new customer behaviors and new addressable markets. In fact, you cannot be a generational company with just the same product / addressable market that you started with.
if Google had stayed search + ads + youtube only, we wouldn't have Chrome, GCP, Waymo, and many others.
if Facebook had only stayed Facebook and not done Insta or WhatsApp (or Muse!), the company would worth a fraction of what it is today.
Same for every other generational company
Seems obvious in retrospect but worth stating.
