What you need to know
- Figma’s revenue quarter and reported AI-user growth cover different periods.
- The add-on credit increase left seat allowances unchanged.
- Compare consumed credits with the applicable rules and accepted work.
Revenue and usage have different measurement windows
Figma reported $391.4 million in revenue for the quarter ended September 30, up 43% year over year. The company released those results on November 4.
Our reading is that the result supplies a business backdrop for its AI expansion, rather than a measure of AI’s individual contribution. Company revenue, people using a feature and credits consumed describe different activities. A useful assessment keeps each measure attached to its own period and definition.
The allowance is a commercial rule
Figma says its August 25 update doubled add-on credits on Professional and increased them 1.6 times on Organization and Enterprise at unchanged prices for subscriptions and pay-as-you-go billing. Monthly seat credits stayed unchanged.
This changes how much room a team has within a purchase. It does not tell the team how much of that room it used, what it produced or how much review the output required. Our editorial view is that an allowance belongs alongside usage in the operating record, so a commercial change remains visible when managers compare months.
A changing meter needs a dated comparison
The Figma agent in Design and Weave tools began consuming shared credits at general availability on October 6. Agent consumption varies with prompts, actions and context.
Separately, Figma reported almost 50% growth from July 1 through October 31 in weekly active users consuming credits among customer accounts in its $10,000-plus ARR category. That window extends beyond the financial quarter.
The distinction matters when interpreting a trend. More people consuming credits is different from a larger quantity consumed by the same people. Adding previously unmetered features also changes the activity represented by the meter. Our interpretation is that a comparison should preserve the feature mix and the applicable billing rules, rather than assume every credit total describes the same kind of work.
Put finished work beside the meter
Consider two hypothetical design teams with an unchanged budget. One uses its expanded allowance to explore more alternatives, but approves the same number of components. The other finishes more components with the same credit use. Both could find the product more useful, for different reasons. A usage count alone would not explain the difference.
This is an illustrative comparison, not a Figma customer result or a test of its software. Our proposed record would connect the task, applicable credit rules, consumption, human review and accepted deliverable. Exploration could be recorded as exploration, rather than forced into a claim about production output. A manager could review a small sample of accepted tasks to understand what the aggregate count leaves unexplained.
That approach makes the business question more concrete: what useful work did the purchased capacity support? The answer can inform a team’s next allocation while leaving company revenue, individual adoption and completed work as distinct measures. A team changing both its allowance and the features it uses would need to explain both changes before interpreting a higher total.



