HN user

dshah

2,910 karma

Startup fanatic. Founder and CTO, HubSpot in Cambridge, MA. Blogger at http://OnStartups.com. Twitter: @dharmesh (http://twitter.com/dharmesh)

Posts203
Comments399
View on HN
agent.ai 2y ago

What Google Got Wrong with Its New Gemini AI Model

dshah
10pts3
network.hubspot.com 5y ago

The HubSpot Culture Code [slides]

dshah
99pts104
www.linkedin.com 6y ago

What Will the New Normal Look Like (Slide Deck)

dshah
1pts0
famicol.in 7y ago

Why Your New Programming Language Will Not Work

dshah
4pts0
news.ycombinator.com 10y ago

Ask HN: Building a simple conversational UI – what libraries should I look at?

dshah
3pts3
blog.zillabyte.com 11y ago

5 Most Popular Growth Tools in the YC Portfolio

dshah
1pts0
onstartups.com 12y ago

Did The 900-Pound Gorilla Just Vanquish Your Startup Or Validate It?

dshah
37pts9
nedbatchelder.com 12y ago

Ad-hoc data breakpoints in Python

dshah
1pts0
blog.asmartbear.com 12y ago

Why I don’t like the LTV metric

dshah
4pts0
blog.leanstack.io 12y ago

The cloud stack that helped SendGrid scale to 100 billion emails sent

dshah
2pts0
moz.com 12y ago

Ambition vs. Obligation - Rand's Blog

dshah
2pts0
www.redbord.com 13y ago

On the SaaS Adoption Curve: When to Solve for the Current Customer

dshah
1pts0
blog.asmartbear.com 13y ago

Escorts, Startups, and the questionable promise of being your own boss

dshah
8pts0
moz.com 13y ago

Vision-Based Framework - Rand's Blog

dshah
1pts0
blog.aha.io 13y ago

Hey Product Managers — Stop Pissing Off The Engineers

dshah
2pts0
insideintercom.io 13y ago

The Danger of Dogfooding

dshah
3pts0
blog.asmartbear.com 13y ago

An eBook pricing model that resulted in $100,000 in sales

dshah
156pts97
onstartups.com 13y ago

The Why and How Of Updating Your Angel Investors

dshah
3pts0
onstartups.com 13y ago

The Pitch Deck We Used To Raise $500,000 For Our Startup

dshah
139pts29
www.inc.com 13y ago

Why More Is Not Always Better (Jason Friend in Inc.)

dshah
3pts0
dev.hubspot.com 13y ago

"Hire People Bothered By Suck" And Other Insights From GitHub

dshah
3pts0
blog.asmartbear.com 13y ago

Reframing the problems with “Freemium” by charging the marketing department

dshah
5pts0
onstartups.com 13y ago

Clear Eyes, Full Heart: Beating The Series A Crunch

dshah
3pts0
mattlauzon.tumblr.com 13y ago

Ten Things Young CEOs Seem Likely To Get Wrong

dshah
2pts0
petewarden.typepad.com 13y ago

Things users don't care about

dshah
3pts0
www.startuplessonslearned.com 13y ago

Don't Be The Ice Cream Glove

dshah
1pts0
nabeelhyatt.com 13y ago

Watching Your Competitors Release "Your" Features

dshah
1pts0
joel.is 13y ago

The highs and lows of startup life

dshah
27pts2
www.webdesignerdepot.com 13y ago

4 tricks for designing data-heavy applications

dshah
3pts1
joel.is 13y ago

The Evolution of Culture At A Startup

dshah
20pts2
Swirl 2.5 Released 3 years ago

Thanks for including a search provider for HubSpot and best wishes with the launch.

Disclosure: I'm one of the founders of HubSpot so a bit biased. :)

I'm from HubSpot (I'm one of the founders).

This was our second year doing the "Week of Rest". It was an experiment we ran last year.

It ended up being a good idea and works well.

This is a really useful thread with posts from people actually using LLMs.

I wonder if Claude-100k could be used to ingest this entire thread and then answer questions based on it, or summarize or identify the pros/cons of certain aspects of Claude, large context windows, vector embeddings, etc.

I'm Co-founder/CTO of HubSpot.

There are many things I admire about Salesforce.

But, we decidedly don't want to become like Salesforce when we grow up. We have been committed to SMBs for 16+ years now, and not planning to change that anytime soon.

They have grown through a lot of M&A, we built our platform from the ground-up for SMBs.

There is room in the market for both Salesforce and HubSpot to succeed. Salesforce for large enterprises (the Fortune 1000) and HubSpot for SMBs.

Can confirm. :) I've been glued to this discussion thread all morning.

Resisting the temptation to respond to many of the messages, because I don't want to come off as defensive.

Thanks for chiming in. Have many good memories of your time at HubSpot.

First and foremost, it's for the ~4,000 people that work at HubSpot and who actually create the culture and live it day-to-day.

Second, it's for those that want to better understand HubSpot and how we work. It may be because they're considering joining the company. Or becoming a customer. Or becoming a partner.

Third, it's for the community of entrepreneurs that are building businesses. My hope is that it can be a useful example of how one company (that has done reasonably well) thought about culture -- and articulated it.

Candidly, this year, because of the pandemic, we've come closer together as a group. Not quite a family -- but closer. Also, I needed to make room in the deck to articulate our position on diversity and inclusion.

I agree with you on that front.

In earlier versions of the deck, we actually explicitly called out that we are NOT a family. We are a team with a common goal. You don't get to choose your family, but you do get to choose your team.

h/t to Netflix for that original "team not a family".

Thanks for the warning. I hear you.

My direct experience is that there will be some that will be cynical -- that's OK.

A big lesson for me personally is that working on culture as a "product" is very useful. Collect customer feedback. Identify bugs. Categorize some things as "works as designed". Be transparent with your customers. And, of course, iterate, iterate, iterate.

The product I'm most proud of having worked on. Hundreds of hours invested for over a decade.

Yes, it's a slide deck -- but think of it as a template.

Shared with the community with love.

Disclosure: I am one of the HubSpot founders.

Sorry for the poor experience you've had with the HubSpot CRM. We are working hard to make things better -- especially the APIs and how we present information in the Contact view.

Thanks for the candid feedback.

Congrats to the api.ai team.

I love when great companies do well.

I'm a happy customer (and wish I were also an investor, but I'm not).

I'm using wit.ai as well, and overall it's working well for me.

But, the new story-based functionality is something I still haven't been able to get comfortable with -- and it still feels very early. So, that part I'm still implementing myself.

And yes, I too wish they they would allow you to download your logs/model. Bugs me that they don't do that (and one of the reasons I'm also looking at api.ai).

Interestingly, my usage dates back to around the same time (Sep, 2010) and the list of features that I use/need is identical. Just a daily email reminder with a previous post from the past year/month.

If the founder(s) of OhLife are reading this thread, I'd like to make an offer: I'll pay to host the infrastructure/servers (up to $1,000/month) as a contribution to the community. My guess is, a lot of people are using this app and would like to keep it around.

Ping me @dharmesh on twitter if you're interested.

I agree that company culture's are organic (changing) and highly dependent on the people that make it.

Having said that, the people that are there are determined by the culture. If the culture of a company is well known, articulated and understood, there's a self-selection process that happens. A given culture attracts certain kinds of people -- so it becomes self-reenforcing.

I also disagree with the notion that a culture cannot permeate across groups. There is certainly a sub-culture that can (and does) exist within groups (this exists everywhere people of like mind or activity aggregate), but that doesn't mean there can't be an overarching culture that is shared organization wide.

I've given a lot of thought and calories to this topic. My company (HubSpot) has grown from 2 people to 800 people and like Brian (OP from AirBnB), we think about this culture thing a lot.

Just because you hit the "awkward teen" size doesn't mean you are predetermined to fail at trying to have a functional , shared culture.