Dharmesh Shah on Culture Debt, SMB Strategy and Building HubSpot

Dharmesh Shah recalls meeting future HubSpot co-founder Brian Halligan at MIT. His wife initially thought the two had little in common, but they connected in class. Shah had planned to leave startups for an academic path; instead, their desire to work together and shared interest in small businesses led to HubSpot.

On marriage, Shah emphasizes enjoying each other’s company, mutual admiration and respect. He describes his wife’s environmental interests and their complementary strengths. This is his personal account of their relationship.

He calls his operating style transparent and humble: share what he thinks, invite debate and accept that experience does not make him automatically right. He values a low ratio of ego to accomplishment. In hiring, he looks for people who accept responsibility when things go wrong and share credit when they succeed.

Shah identifies HubSpot’s early lack of diversity as a major mistake. He says the first six hires were men from the same MIT program and that the founders did not initially think deliberately about culture. He believes the effects can persist long after the initial hiring decisions.

He calls this culture debt: a poor hire or homogeneous early team can shape what later employees see as acceptable. Unlike a financial debt paid by a check, he says, its effects are difficult to measure or fully remove. This is his management framework, not a measured interest rate.

Shah treats culture as a product: ask employees what helps or prevents them from doing their work, collect feedback and revise it. HubSpot’s Culture Code was his attempt to describe an operating system for company decisions, rather than merely a list of slogans.

He recalls that his first employee survey about culture met unexpected resistance. Colleagues feared corporate mission statements and consultants would replace the practical company they had joined. He says he had to explain that the aim was to understand and improve the existing culture, not simply add polished language.

The first Culture Code asked what kinds of people were likely to succeed at HubSpot. Shah says the team identified attributes such as transparency, humility, empathy and adaptability, then used them in hiring and promotion. He advises founders to discuss desired culture from the beginning, or start now if they have not.

For difficult co-founder decisions, he and Halligan first ask whether they agree. If not, and one feels much more strongly, that person’s choice generally prevails. If both strongly disagree, they debate; Halligan as CEO ultimately decides if necessary. Shah says the final escalation was rare.

Shah describes lifelong impostor feelings tied to modest circumstances and relatively late exposure to computers. He says he sometimes wonders about competing with people who had earlier access to resources. He does not generally compare scores with others, preferring to learn from qualities he admires.

He says patience is one of his strengths: a small amount of valuable insight can make a long conversation worthwhile. On raising a child with greater resources than he had, he is uncertain whether drive is innate or learned, and tries to connect work and learning to his son’s existing interests.

To illustrate software creation, Shah built a word game over a weekend and involved his son in launching, observing traffic and testing features. He says WordPlay had reached six million players at the time. That is his product-side claim in 2022, not a verified count of active or paying users.

Shah agrees that distribution matters alongside product. He distinguishes three startup risks: failure to build the product, absence of a market and inability to obtain the capital needed to build the business. In his view, founders often focus too quickly on building before testing whether customers will pay.

His preferred market test is an exchange of value for money. He says HubSpot’s founders chose an initial $250 monthly price quickly, launched an early product and charged from the start. The point was to gather evidence of demand, not prove that the first price maximized revenue.

Early HubSpot customers could cancel month to month. Shah says that created repeated observations of whether customers chose to stay, whereas a fixed annual contract might conceal dissatisfaction for months. He presents this as a learning choice the company made, not a universal pricing rule.

He disagrees with a blanket instruction to raise prices. Shah says HubSpot retained existing customers at their original price when new-customer pricing rose from $250 to $500. In a hypothetical later reduction, he argues, subscription customers paying more would reasonably expect the lower price, reducing recurring revenue.

He advocates leaving customers some surplus rather than extracting every dollar of perceived value. In his view this can build goodwill and preserve flexibility to raise prices later. The argument comes from HubSpot’s co-founder and CTO, who has an interest in the company’s pricing strategy.

Shah and Halligan chose small and midsize businesses partly because of their experiences with enterprise software. He says large customers can concentrate revenue and influence the roadmap, while longer sales cycles slow learning. He contrasts that with consumer businesses, where he sees potentially huge outcomes but also a risk of zero.

He sees SMB software as combining a broad customer base with the ability to charge businesses, while acknowledging that distribution economics can be difficult. He calls the tendency for SaaS companies to drift toward larger customers “reverse gravity”: many short-term metrics improve, but competition also intensifies.

Doing unscalable things can be useful for learning, he says, if a company has a credible path to the market it intends to serve. Stebbings warns against applying enterprise sales costs to small contracts while assuming a later move upmarket will solve the problem. Shah agrees that lessons from one market may mislead in another.

Before launching a second product, Shah asks why it is needed. Reasons can include slowing growth in the existing market, a shrinking category, or an adjacent market that matters for growth or defense. He cites HubSpot’s move from marketing software into CRM as an example of the third case.

He says HubSpot saw marketing leads flowing into CRM systems and worried that CRM providers could later expand into marketing. Shah reports that the marketing product had grown beyond $1 billion in annual recurring revenue by the interview. That is his company-side statement about recurring revenue at the time, not profit.

Shah advises delaying a second product as long as practical, though not forever. Beyond projected revenue, a second product adds a new dimension of complexity to hiring, R&D, marketing and performance analysis. Every resource decision must now be considered across both products.

He says HubSpot has generally done better by committing significant people and resources once it chooses a second product, rather than running many small experiments. He acknowledges that other companies may be better at experimentation and that his approach can be wrong. The opportunity must be large enough to justify the bet.

To encourage internal disruption, Shah keeps boldness among his three priorities alongside platform and brand. He asks teams to allocate some resources to calculated outlier bets even when existing work looks predictably profitable. His percentages are illustrative, not a disclosed HubSpot budget.

He recommends discussing failed experiments openly so employees see that responsible risk-taking is accepted. In a fast-growing company, leaders must repeat cultural messages because many people hear them for the first time. The goal is to learn from failure, not treat all outcomes as equally good.

Shah identifies the second product, international expansion and going public as important scaling transitions. Building CRM was difficult because HubSpot was known for inbound marketing and had to earn permission from the market to enter a different category. The company had to learn a new domain while approaching its IPO.

For product marketing, he emphasizes a story that resonates with a community rather than a neutral message everyone accepts. He says HubSpot gathered people around inbound marketing through content and events before it had a mature product. His account is from a founder with a commercial interest in that positioning.

A community, in his view, is not merely a list of people who can be marketed to. Members should get value from one another, while the company acts as host and may benefit indirectly. He describes the connections people make outside a keynote as more revealing than attendance alone.

His 2022 prediction concerns the way buyers and sellers connect and the share of value people receive from data they provide to intermediaries. Stebbings challenges him, noting that users also receive distribution and can monetize it. Shah accepts that indirect value exists but questions its share and says he does not know exactly how the model will change.

Shah began angel investing to stay connected with startups and continued after starting HubSpot, setting rules to minimize time rather than maximize returns. He says he exchanges emails rather than taking founder meetings, does not negotiate terms, and generally does not make follow-on investments.

He describes judging some founders through email and says he personally does not conduct extensive diligence. He claims his portfolio performed well, but supplies no return data here. These are his own time-saving practices and assessment, not a recommendation that others skip meetings or independent due diligence.

He says mistakes included investing in physical-product businesses outside his expertise and overlooking warning signs about a founder after falling for an idea. He recalls missing an early Dropbox round partly because friendship made both sides reluctant to raise the subject, though he later acquired pre-IPO shares. No investment return is provided.

In the quick-fire round, he recommends Les Misérables, Getting to Yes and The Innovator’s Dilemma. He distinguishes learnable skills from talent, and says his own reluctance to confront people makes management difficult. He also finds it hard to follow his own advice to care for his health.

He wishes he had known the SMB bet would work, wants founders to focus on customer problems rather than become attached to solutions too early, and credits HubSpot’s partners. Looking to 2027, he hopes to continue helping the company solve customer problems; that is his 2022 aspiration.