We announced today that we acquired Boston-based social graph company, Rekindle. We’re beyond excited to welcome their team, talent, and innovation to HubSpot. Here’s why.
Keep Reading >
Earlier this week, our co-founder and CTO Dharmesh Shah gave a talk at our company meeting about culture as a competitive advantage. He said every small interaction that happens at a company adds up to its unique culture, making it impossible to replicate; every decision, laugh, beer, handshake, everything. It’s easy to see the tie between those details and the parts of a business that deal with people, like recruiting. But when it comes to building software, the competitive advantage of culture isn’t so clear.
We've designed our team structure, development processes, and technical archicture to promote strong team ownership and iteration velocity. HubSpot makes a marketing and sales platform trusted by more than 13,600 customers to power their online presence. Those businesses rely on our SaaS platform to host their website, blog, landing pages and forms, collect web analytics, manage their contacts, deliver marketing emails, support their social media efforts and much more. The capability is relatively broad -- each functional area has many companies that focus on just one vertical -- and is growing as we continue to introduce new products.
Our stack is not only a function of building B2B SaaS offerings, the company's stage and size, but also the cultural values that we want reflected in our products and organization.
Yesterday, Google announced they would officially be pulling the plug on open source project hosting service, Google Code. What launched ten years ago as an alternative to SourceForge never really grew up to be the social coding platform Google envisioned. In other words, it wasn’t GitHub.
Here at HubSpot, we ship new code quite often. Development at such a rapid pace only works if you can ensure as little disruption as possible (if any) for your customers by using strategic patterns and techniques. We have a system in place that allows us to toggle features on a per-customer basis and we recently applied it to successfully rewriting an existing, high-trafficked API.
We implemented this with our own homegrown gating system, and our nginx loadbalancing tier, but the general pattern could be applied to other architectures, too. Here’s a rundown of how we did this and the steps you can take to address issues with a new system before they impact your overall customer base.
Last year, our customers used HubSpot’s social software to share over 6 million posts on social media. Creating and publishing social content was a breeze but their feedback made it clear that gauging the impact of that content was more of a challenge. Customers didn’t just need data, they needed a tool to help them be better marketers, so we set out to build a social reporting solution. We launched Social Reports a few months ago and I wanted to share some insights from that process since data visualization can be a particularly tricky design challenge.