long-form-interview· Shaunt Voskanian

Inside Figma's $1BN ARR Revenue Machine

In a PLG-native company at scale, the CRO's job is not to net-new acquire — it is to outbound INTO the existing customer base with prescriptive insights, deliberately routing around CS and SDRs by giving AEs the full stack, easier strategic quotas, and a performance framework that demotes quota attainment from the primary judgment metric.

figma20vcshaunt-voskaniancrosalesplgquotaramp92% confidence

Why this is in the corpus

Concrete operator counterpoint to the ElevenLabs/Carles episode: same role (CRO at a hot AI-era B2B), opposite quota philosophy (3-4× OTE vs 20×), opposite SDR/CS structure (none at Figma vs none at ElevenLabs but for different reasons), and a different motion (expansion-as-hunting vs net-new acquisition). Captures Figma's three-business model, results+behaviors+competencies performance framework, and the take-home discovery+demo as the AE filter.

Summary for skimmers

Shaunt Voskanian, CRO of Figma (~$1B ARR), on the revenue machine. Figma has no traditional SDRs and no traditional CS team — both deliberate. Three businesses: self-serve (web + credit card), PLG-SMB (≤500 employees, AEs upgrading via product signals), and sales-led (mid-market / enterprise / Strat — majority of the team). The sales-led motion is outbound BUT into existing customers — proactive prescription based on patterns of how best customers use Figma vs how the typical customer uses it. NRR jumped 131%→136% in last earnings; seat-based pricing isn't dead at Figma but credits-for-AI launches in days. Quota philosophy: aggressive 3-4× OTE quotas (relatively easy by industry standard) for strategic SLG reps because the work is hard and the right population is small. Hot take: "I don't care if you hit your quota" — quota attainment is a lagging indicator that breeds lazy leadership; judge on results + behaviors + competencies. Hire profile: deal experience > industry experience if forced to pick; visceral red flag on resume-jumpers (12 mo / 12 mo / 12 mo); back-channel rather than over-weight the offer-stage negotiation. Take-home assignment is discovery + demo, optimised for perseverance and curiosity. Ramp: throw new enterprise rep into 1-2 strategic accounts week one, classroom-style in-person enablement, recurring market-update standups. Don't ask one rep to do 14 things; specialise via segmentation, then verticalisation, then overlay. Move fast on bad-apple high earners — culture damage outweighs revenue.

Briefing

What survives the editorial filter

This page should feel like a smart colleague already listened for you and left only the operating logic worth keeping. Not everything said in the episode makes it through.

Trust signal

direct_practitioner_account

Guest type: practitioner.

Best used for

Shaunt Voskanian (CRO Figma, ~$1B ARR) on the Figma sales machine — outbound INTO existing customers, no SDRs, no CS, 3-4× OTE quotas for strategic work, "I don't care if you hit quota" judged on results+behaviors+competencies, take-home discovery+demo case study for AE hiring.

Hold lightly

No explicit downgrade reason stored yet for this episode.

Principles

Durable claims that survive beyond the speaker's biography — each with explicit limits, transferability judgment, and evidence.

Principle

The art of enterprise sales: mix curiosity AND prescriptiveness — neither alone wins

Modern enterprise buyers reward sellers who arrive with a teachable insight tailored to their situation; arriving with only one half (curiosity OR prescriptiveness) underperforms.

Shaunt names the failure mode of pure-curiosity (I do not want to be qualified, you should already know my situation) and pure-prescriptiveness (generic insights that do not fit). Figma reps are taught to bring patterns from comparable best-in-class customers AND probe what is specific to this account.

Use when: Enterprise B2B sales orgs training discovery + insight skills.
Skip when: Pure transactional/PLG motions where the buyer wants speed, not insight.

Train AEs explicitly to bring an external pattern AND a per-account probe to every meeting.

It is not just about being curious, it is about being prescriptive... what they really want is insights.Shaunt Voskanian
You have to be able to do both at the same time or else you are not gonna be successful.Shaunt Voskanian

Durability: Durable; the buyer-attention dynamic is structural.

Principle

Quota attainment is a lagging indicator that breeds lazy leadership

Quota attainment as the primary judgment metric punishes good reps when the quota was set wrong AND lets weak leaders skip the harder work of observing rep execution.

Shaunt: when a manager says this rep is not performing because they did not hit quota, the response should be why? show me what they are doing wrong. If the rep is grinding, doing PG, executing discovery, building pipeline — they need time. If lone-wolfing or not learning — move fast regardless of quota status.

Use when: Sales orgs with strategic-account motions and long sales cycles.
Skip when: Pure transactional sales where lag is small.

Replace did-they-hit-quota with show-me-their-PG/discovery/pipeline. Manager strength comes from real-time observation.

I kind of don't care if you as a rep hit your quota or not... I just think it is too much of a lagging indicator. And what my fear is, it creates lazy leadership.Shaunt Voskanian

Durability: Durable; lagging indicators corrupt management.

Principle

Missionary sellers outearn mercenary sellers — career growth signals predict who will earn the most

The best earners over a 10-year window are not the ones obsessing over the next pay-period; they are the ones obsessing over getting better, which compounds into bigger deals and accelerated promotions.

Shaunt hire-screen: career growth, learning, development, collaboration are the signals worth filtering for. He has seen sellers who chase W2 hardest go the other direction.

Use when: B2B sales hiring panels.
Skip when: Pure-commission transactional roles where money-first is the design.

Filter at first interview for growth-mindset signals. Treat money-first as a yellow flag.

Some of my best people over the years where money wasn't the first thing that they were thinking about... I think the best people actually kind of know that if you are prioritizing those things, the money comes.Shaunt Voskanian

Durability: Durable; the compounding-craft argument is structural.

Frameworks

Reusable systems and operating models — including when they help and when they break.

Framework

Performance framework: Results + Behaviors + Competencies (not just quota)

Reducing rep evaluation to one bucket (results) is the failure mode that breeds lazy management; explicit framework with three buckets forces leaders to manage in real time.

When the three-bucket frame is in place, did-they-hit-quota is no longer an acceptable performance-management answer — it is a starting question.

  1. Results: quota + PG + success metrics
  2. Behaviors: collaboration, growth mindset, attitude
  3. Competencies: PG, discovery, pipeline mgmt, methodology adherence
Use when: Sales orgs above ~50 reps where evaluation needs to be standardised.
Skip when: Founder-led orgs with <10 reps.

Document each bucket with sub-criteria. Make did-they-hit-quota a starting question, not a verdict.

There is a results bucket... and then behaviors and we documented what does that mean? And then competencies, we documented all of the competencies that we actually care about.Shaunt Voskanian

Durability: Durable; widely applicable.

Framework

Aggressive (3-4× OTE) quotas for hard strategic work — the reward signals it is worth your time

Hard strategic sales work has a small qualified-population; setting easier quotas signals the work is worth your career time.

Shaunt view: average enterprise rep at Figma carries 3-4× OTE quota — relatively low by industry standard. Compare to ElevenLabs at 20×. Figma philosophy reflects that work is hard, the right population is small, the company has a strong base of customers, so reward the people who can do it.

  1. Hard strategic work + small talent pool → aggressive quota (3-4× OTE) + bigger payouts
  2. Transactional + large pool → high quota (10-20× OTE) + accelerator structure
  3. Match quota multiplier to motion, not to industry-standard
Use when: B2B companies setting quotas for strategic enterprise reps.
Skip when: Transactional / SDR / SMB motions.

Match quota multiplier to work difficulty and talent rarity.

An average enterprise rep here might have three to four x their OTE for a quota and we are happy with that.Shaunt Voskanian
We want to have really aggressive as in like relatively easy quotas compared to what is out there in industry standard because the work is hard and it is strategic.Shaunt Voskanian

Durability: Durable framework; multipliers may shift with conditions.

Framework

The Figma three-business operating model: self-serve / PLG-SMB / sales-led

A multi-product PLG company at scale needs to explicitly split self-serve, AE-led upgrade, and full sales-led motions — running them as one motion produces neither efficiency nor strategic depth.

Self-serve = no rep involvement. PLG-SMB = AEs in zero-to-500-employee accounts upgrading via product-signal triggers. Sales-led = mid-market + enterprise + Strat, smaller per-rep books, full discovery + champions + medic + value-selling.

  1. Self-serve: no rep involvement; web + credit card; lower-tier plans only
  2. PLG-SMB: AEs in ≤500-employee accounts; upgrade via product-signal triggers
  3. Sales-led: mid-market + enterprise + Strat; full discovery + champions + medic motion
Use when: PLG-native B2B at scale ($50M+ ARR) with multi-segment customer bases.
Skip when: Single-motion businesses where bundling cost is lower than splitting cost.

Audit which AE handles self-serve upgrade AND sales-led strategic AND PG simultaneously. Split them.

We kind of have three distinct businesses at Figma. One is self-serve... PLG... concentrated in our SMB segment... And then we have our sales led, which I would consider mid-market enterprise and Strat.Shaunt Voskanian

Durability: Durable PLG-at-scale operating model.

Signals

What appears to be shifting, for whom it matters, and what happens if you ignore it.

Signal

Seat-based pricing is alive and well — Figma added 5 points of NRR (131%→136%) on it

The death-of-seat-pricing prediction is wrong, or at least premature, in categories where the buyer is a builder/designer (not labour replacement).

Driver of Figma seat expansion: the world is creating more builders, not fewer. Adding credits is not the same as moving off seats.

Use when: B2B SaaS pricing teams considering scrapping seat-based for usage/credits.
Skip when: Customer-support / labour-replacement categories where seat-pricing genuinely inverts.

Do not reflexively kill seat pricing. If your buyer is a builder, seats may still scale. Add credits on top, do not replace.

We added five points on our net retention. Pretty significant I think went from 131% to 136%. Obviously today we are in a pretty much an exclusively seat based model.Shaunt Voskanian
There is just more and more builders I think coming into software.Shaunt Voskanian

Durability: Time-sensitive (the threshold may shift); structural insight is durable.

Opportunities

Only included where there is a buyer, a real wedge, and a plausible revenue path — not vague idea theater.

Opportunity

Opportunity: AI-design tooling beyond Figma

$10B+ over 5-7 years.

Figma is drawing. AI-design is prompting.Voskanian context

Durability: Time-sensitive.

Forward thesis.

Lessons still worth keeping

Useful takeaways that did not fully clear the bar for durable principle status.

Lesson

Hire slow, even at the cost of missing the hiring plan — a B-player costs more than the empty seat

Sales hiring is the primary lever on revenue 12 months out; compromising on the bar to make a quarter's plan is a negative-NPV trade.

Shaunt: if someone says they have a B-player candidate, I am never gonna say hire that person. A founder he met yesterday plans to add 200 reps in 12 months; Shaunt's estimate: probably 20 will be good.

Use when: Sales leaders under hiring-plan pressure.
Skip when: Roles where ramp-cost is near-zero and a B-player is genuinely productive day-1.

Reject good-enough-to-grow hires. Empty seat > B-player seat.

I am never gonna say hire that person, I am just not going to do it. Even if it risks the hiring plan.Shaunt Voskanian

Durability: Durable; the math holds in any reasonably-priced sales org.

Lesson

In a PLG company at scale, expansion is a hunting motion — not a CS or AM job

Treating PLG-driven customers as happy customers needing only support leaves the majority of the expansion opportunity on the table.

Figma structural choice: no traditional CS team. Sales-led reps go into existing customers with the same hunting toolkit they would use for net-new — except now the prospect already trusts the product.

Use when: PLG companies at $50M+ ARR with broad customer bases and shallow per-account adoption.
Skip when: Companies where customers already use 80%+ of product capability at first land.

Do not hire CSMs to expand PLG accounts. Hire AEs trained in hunting, point them at existing customers.

You compare what an average customer is doing with Figma compared to what we think they should be doing with Figma, there is a pretty big gap... how do we go and proactively educate the customer on the more that they can be doing.Shaunt Voskanian
For the most part, that is a hunting motion.Shaunt Voskanian

Durability: Durable for the PLG-at-scale generation.

The Plays

Try these this week

Verb-first executable actions — each one tied to a stated outcome in the episode.

Strategic enterprise rep ramp — accounts day one, classroom enablement after

For an enterprise rep, one of the things we want to do is kind of as quickly as possible, even before we teach them all the product stuff and the sales skills... we kind of wanna get them into their account and their territory. First thing, kind of throw them into the fire.
Shaunt Voskanian
5-week ramp; ongoing standups per
  1. 1

    Day one: assign rep 1-2 strategic accounts

    Real accounts, currently in motion. Outgoing rep or manager gives handover. Goal: build relationships and learn the account immediately.

  2. 2

    Weeks 1-2: rep listens on calls + learns the account

    Passive listening + active research on the customer business. They are not driving deals yet, just absorbing context.

  3. 3

    Weeks 3-5: classroom-style in-person enablement

    Cohort-based, in-person if possible. Modules: tech ecosystem landscape, product depth, sales process, methodology (e.g., medic + value-selling), resources + operating rhythm.

  4. 4

    Bring in thought leaders across the org

    Product, eng, marketing, customer-success-equivalent leaders teach modules in their domain. Classroom format > async video.

  5. 5

    Recurring market-update enablement standups

    Weekly or biweekly. New product launches, ecosystem changes, new competitor moves — keep the team uniformly current.

  6. 6

    Track ramp by inputs, not lagging quota

    PG activity, discovery call quality, methodology adherence. Quota-attainment ramp is the lagging metric.

Before you start

  • · Strategic accounts available to assign on day one
  • · Cohort-based hiring cadence (so classroom is feasible)
  • · Internal thought leaders willing to teach modules
  • · Operating rhythm documented (pipeline reviews, forecast calls)
onboardingenablementsales-rampgrowth-stagescalehyper-scale

Take-home discovery + demo case study — AE hiring filter

We always make people do a challenge or an exercise at the end that requires some heavy lifting in terms of like learning a bit about our business but also showing off your basic sales skills around discovery.
Shaunt Voskanian
3-5 days take-home; 60-min live session per
  1. 1

    Build a fictional case study — target customer + relevant facts about their business

    Should be real-feeling enough to require effort to research. Detail the customer industry, size, problem, current state.

  2. 2

    Give the candidate 3-5 days lead time

    Long enough that real effort is required; short enough that the test is energetic, not extended.

  3. 3

    Set the live session: candidate runs a discovery + brief demo

    Candidate enters as if meeting the prospect; runs 20-30 min of discovery, then demos a workflow. You play the prospect.

  4. 4

    Score discovery > demo polish

    Polish is unfair to expect after 3-5 days of product. Discovery quality is the real signal — questions, listening, framing. Demo competence is a tertiary signal.

  5. 5

    Filter on perseverance signal

    Did they go deep on the customer? Did they actually learn the product? Effort signal beats raw skill signal at this stage.

Scripts

prompt

Here is the case study: [customer]. They are looking at solutions in [space]. Prepare a 30-min meeting. We will play the prospect. You should: (1) lead a discovery conversation, (2) follow with a brief demo of one workflow you think would resonate. We will evaluate on discovery quality, product engagement, and how you handle pushback.

Before you start

  • · A representative-but-fictional customer case study
  • · An interviewer skilled at playing prospect
  • · A scoring rubric (discovery over demo)
  • · Hiring panel buy-in to weight take-home quality high
hiring-filterinterview-designsales-recruitingearly-stagegrowth-stagescalehyper-scale

Outbound INTO the existing customer base — expansion-as-hunting motion

Once they get their accounts, the job is you map it out, you map out that org and you basically have a vision of what is a best in class deployment of Figma look like... where are they today? And that gap between those things is your job.
Shaunt Voskanian
Quarterly account-planning cycle; weekly pipeline reviews; multi-quarter expansion arcs per
  1. 1

    Define a best-in-class deployment archetype per company type

    For each company size, industry, and maturity stage in your customer base, document what an ideal full deployment looks like — features adopted, personas using, integrations live, ARR per employee.

  2. 2

    Assign each AE a small book of existing customers

    Smaller book sizes for sales-led, enterprise, and Strat reps. Ruthless prioritisation — which 10-20 accounts will the rep go really deep on?

  3. 3

    Map each assigned account end-to-end

    Org chart, current product usage, current personas, current ARR. Compare to the archetype blueprint.

  4. 4

    Build a written vision of the gap

    What does the bridge from current to best-in-class look like? Which new personas, products, features, integrations? Quantify the gap in seats and ARR.

  5. 5

    Run prescriptive outbound INTO the account

    Approach existing champions AND new EBs/personas with cross-customer insights about what comparable best-in-class accounts are doing differently. Frame each meeting as an insight delivery, not a renewal/upgrade.

  6. 6

    Run weekly pipeline reviews + forecast calls

    Same SaaS sales discipline as net-new, but with the gap as the pipeline definition rather than logo acquisition.

Scripts

insight-frame

Hi [name] — wanted to share what we are seeing comparable [industry/size] companies doing with Figma that you may not be tapping into yet. Specifically: [insight from cross-customer pattern]. Worth a 30-min discussion?

Before you start

  • · Documented best-in-class deployment archetypes per customer type
  • · Account-mapping discipline (org chart + persona inventory)
  • · Cross-customer pattern visibility — usage analytics that show what your peers are doing
  • · AE skill in discovery + champion-building + insight delivery
expansion-motionenterprise-salesaccount-managementgrowth-stagescalehyper-scale

Decision Moments

Actual decisions, real outcomes

Specific decisions narrated in the episode with their outcomes and transferable lessons.

Shaunt joined Figma four-and-a-half years ago. Standard new-leader instinct: come in with strong opinions and start changing things. Counter-instinct: come in too soft, defer to existing culture.

Did: Optimised too far toward the soft side — too much time observing, understanding the culture before implementing changes. Some changes did happen quickly, but in retrospect he would have moved faster on more.Outcome: A regret in hindsight: too-cautious entry slowed transformation that ended up being right.

New CRO/CXO playbook: ramp observation faster, push changes earlier. The risk of going too cautiously is symmetric to going too aggressively — and easier to under-correct than to over-correct.

Part of an emerging decision pattern across multiple episodes

Figma had grown to ~$50-100M ARR via PLG. Most customers self-onboarded and used a fraction of the product. Standard playbook: hire CSMs to drive adoption and expansion.

Did: Refused the standard playbook. Concluded that expansion was a hunting motion, not a satisfaction motion, and structurally chose to NOT build a traditional CS team. Built sales-led mid-market/enterprise/Strat orgs instead, with AEs trained to go INTO existing customers with prescriptive insights.Outcome: NRR 131%→136% in latest earnings. Sales-led motion is now the majority of the team. Validates the structural choice years later.

When acquisition is PLG, do not import the legacy CS function. Restructure expansion as a hunting motion with AEs going into existing customers — most of your customers under-use the product, so the upside is in winning new internal champions, not satisfying existing ones.

Part of an emerging decision pattern across multiple episodes

Figma was choosing how to set quotas for strategic enterprise reps. Industry default: 5-7× OTE quota. ElevenLabs choice: 20× OTE quota.

Did: Set strategic enterprise quotas at 3-4× OTE — relatively easy by industry standard. Reasoning: the work is hard, the population that can do it is small, and reward should signal that this is worth your career time.Outcome: Figma can attract and retain reps who can do complex insight-driven multi-stakeholder enterprise sales. The 3-4× philosophy is the explicit foil to ElevenLabs 20× and the common 5-7× default.

Match quota multiplier to work difficulty and talent rarity, not to industry standard. Hard strategic work + small talent pool = easier quota + bigger payouts. Transactional fast-pull motion = higher quota + accelerator structure.

Part of an emerging decision pattern across multiple episodes

Figma's enterprise sales org was using a traditional pre-deployment classroom-then-territory ramp. The remote/COVID era had also pushed enablement to async video.

Did: Inverted the ramp sequence: throw new enterprise rep into 1-2 strategic accounts day one, listen on calls for 2 weeks, THEN run classroom-style in-person enablement. Going back to in-person classroom from async-video.Outcome: Soft launch of the new ramp this week (per the conversation). Ongoing market-update enablement standups added on top.

Account immersion BEFORE formal training grounds the rep in real work; classroom enablement AFTER immersion sticks because every concept maps to an account already familiar. Async video underperforms cohort-based in-person classroom for sales enablement.

Part of an emerging decision pattern across multiple episodes

Tensions surfaced

Contradictions and trade-offs the episode raises — judgment calls a thoughtful operator has to navigate.

Tension

Tension: PLG growth vs traditional enterprise sales

Different team designs, metrics, cultures.

PLG and enterprise sales clash. Different orgs.Voskanian

Durability: Durable.

Productive tension.

Corpus connection

Where this episode fits for retrieval

What kinds of decisions this briefing is best pulled into.

Primary decisions

  • hiring-when-to-hire
  • go-to-market-channel
  • pricing-packaging

Temporal flag

partially dated