Plot.ly

Jack Palmer started working on Plot.ly in 2012 and incorporated the company at the end of 2013. The company was born from a genuine need in the data science and developer community: a best-in-class charting library that could serve as a communication platform for technical teams. Palmer saw that data scientists at companies like Tesla needed a way to create visualizations in Python or MATLAB and share them seamlessly with their teams—not just for external presentations, but for internal collaboration across departments.

Plot.ly launched with an interesting dual model from the start. Palmer and his co-founders (four total, including co-founder Alex Johnson) bootstrapped the first year with just two people. They decided early that the product needed to work both as a cloud SaaS offering and as an on-premise solution. Why the hybrid approach? Most of their target customers—aerospace, finance, and tech companies like Tesla—wouldn't trust their data science workflows to the cloud. They needed on-prem solutions completely behind their firewall. Palmer's team used Docker containers to package their cloud server into an on-prem product, keeping the software identical while varying the deployment model.

In their first year of sales (2014), Plot.ly did "basically nothing less than $300,000." The acquisition strategy was radically different from typical SaaS playbooks. Rather than spending heavily on ads, Palmer and team invested in making their product exceptional and their documentation phenomenal. They wrote thousands of documentation pages—work they had to do anyway for a developer-focused product. This content became a growth engine: it ranked incredibly well in SEO, drawing developers who were already searching for charting solutions. The inbound effect was powerful: "every day people come to us from companies who have already been using this software for several years." Palmer explicitly noted they spent only about $20,000 total on paid ads since 2013, trying different approaches that simply didn't work at scale.

The winning channel was ruthlessly clear: content marketing and SEO. Palmer explained the philosophy: "if you just write, if you just make a really great product and you have at least one strategy like you know for us, it's been SEO with you know the thousands of documentation pages. We had to write anyway." They killed two birds with one stone—shipping a better product and capturing organic search traffic.

Paid acquisition didn't work because their audience was too niche and technical. Banner ads on niche blogging sites showed some promise but didn't scale. Instead, Palmer invested the $4.5M seed (plus $1M in venture debt from Silicon Valley Bank) almost entirely into product and documentation. The company stayed cash flow positive, which gave them discipline: customer acquisition costs had to come back within 60 days net. This wasn't theoretical—they tracked it religiously.

By year two, they had 3,000-6,000 cloud customers at $400/year minimum, generating roughly 50% of revenue. Their on-prem segment was smaller in customer count (~300 accounts) but commanded $10,000-year minimums, making up the other 50% of revenue. Cloud churn was about 10% annually; on-prem was stickier due to switching costs.

By the time of this interview, Plot.ly had grown to approximately $2M in ARR, nearly doubling revenue every year from their $300k start. The team had grown to 20 full-time employees (plus ~10 contractors on open source), mostly based in Canada with a VP of sales in Boston and a technical sales lead in New York. They'd achieved something rare in enterprise software: nearly 90% retention, inbound-driven growth with minimal paid spend, and sub-60-day payback periods on acquisition. Palmer attributed this to a simple insight: build an excellent product, invest in one channel deeply (in this case, SEO-friendly documentation), and let word-of-mouth and organic discovery do the heavy lifting.