360° customer view
Product Qualified Lead (PQL)
Account Health Score Model
Redshift to Salesforce
Redshift to Google Sheets
Figma is a SaaS collaborative design tool that enables the entire design team’s process to happen in the cloud.
Figma is built around a freemium model - designers from all over the world get started using Figma for free and bring in coworkers to collaborate on the platform. They start paying as they use more of it.
This Product Led Growth has been at the core of Figma’s success and revenue growth since it launched in 2016. To capitalize on that rapid growth, in 2018 Figma launched their Organizations product and decided to build an Enterprise Sales team to drive its adoption.
That’s when Figma’s Sales Ops team turned to Census for help.
The problem the Sales Ops team faced was finding the right sales leads amongst their millions of users, many of whom weren't ready to buy. How could the company turn their rapid product led growth into a sales strategy?
Not knowing which features the customers were using made it complicated for Account Managers to know which accounts to educate and engage in order to prevent churn and/or create opportunities.
With millions of freemium users, it was difficult for Account Executives to know which customers to prioritize.
A lack of consistency in their user, team, and organization models made it impossible for Account Executives to understand which prospects were using Figma inside the organization, and for what purposes.
Figma set out to organize their users into a hierarchical account structure. Their goal was to group all Figma teams and organizations together into a single account so that it could be worked by an individual rep.
With Census, Figma automatically created child accounts for new teams and organizations, and associated them with a single parent account representing the company. When an individual from a new company signs up for Figma, Census triggers Salesforce automation to create a new parent account to represent the company, and a child account to represent the org or team. Opportunities and contacts are associated with a child account, but a single rep owns the whole hierarchy of accounts, opportunities, and contacts.
Figma went even further. Even though a rep was actively engaging with a particular account, the customer could choose to pay for the product at any time with their credit card, skipping the rep entirely. Figma used Census to incorporate payment data from Stripe into the account hierarchy, adding automation to create new Opportunities or mark existing ones as Closed Won when a credit card transaction occurs
Building a unified list of accounts was the first step, but now the team had to figure out which leads and customers to prioritize. Figma, like most companies, chose to solve this by enriching their leads with third-party data from Clearbit to find users working in the Fortune 500. However, using third-party data isn’t enough to build a great sales operation.
With Census, Figma added internal product usage data and created a 360 view of their users directly in Salesforce. The Account Executives and Account Managers could now understand the level of engagement for each account at a glance and identify their ICP by looking for those users with highest levels of engagement.
With potential accounts unified and enriched, the final step was to turn the data into action. Figma leveraged their new first & third-party enrichment data to build their own Product Qualified Lead (PQL) scoring model and a Customer Health Score model.
By using Census, Figma could now tweak both scoring models and immediately deploy the new formulas to every account so that reps stay prioritized on the right accounts at the right time, even as strategy shifts.
The investment in a data-driven sales process has paid dividends by increasing the productivity of the Sales team. This increase in both efficiency and productivity led Figma to achieve their sales target & raise their series C financing just a year later.
Since the initial deployment, Figma has continued to improve their go-to-market machine. First, they leveraged Census to enable real time sales forecasting in Google Sheets instead of daily manual updates. Second, using their now-structured usage data and existing data sync, other teams such as the Marketing Ops were also able to deploy Marketo with a full list of customers and their activities in a matter of a few days instead of weeks.
And the best part, no engineers or custom code needed.