Figma will report third-quarter results after U.S. markets close Nov. 4, 2026, giving design leaders a fresh checkpoint on the business behind their creative software spending. The company has scheduled its earnings call for 5 p.m. Eastern, with a webcast, subsequent replay and transcript available through its investor relations website.
This Preview focuses on questions for that report, not predictions about results. The practical issue is how to distinguish use of AI tools from additional purchasing and, separately, from better design work.
Read the adoption denominator
In its Aug. 5 second-quarter release, Figma said more than 80% of paid customers with over $10,000 in annual recurring revenue were consuming AI credits weekly. Its definition uses the quarter’s week with the highest number of those users. That is not an average across every week or a statistic covering all customers.
For the coming report, a useful question is whether any new adoption figure retains that cohort and measurement method. A larger percentage measured differently would not provide a clean comparison. Nor would credit consumption alone establish that a team purchased incremental credits, reduced revisions or shipped a stronger product.
Creative leaders evaluating their own accounts can apply the same discipline: specify which teams use the tools, the period measured and what constitutes useful output. An experiment and a repeatable production workflow should not be treated as interchangeable evidence.
Separate expansion from outcomes
Figma’s second-quarter revenue was $370.1 million, up 48% from a year earlier. Management attributed customer expansion to seats and AI credit add-ons. The company reported a GAAP operating loss of $117.3 million and adjusted operating income of $36.1 million; the adjusted measure excludes specified expenses.
Those are historical supplier financial measures, not evidence that an individual design department obtained a return on its spending. The coming discussion could help clarify the relationship between subscription expansion and consumption, but readers should distinguish any disclosed figures from management’s interpretation of demand.
For budget owners, the corresponding question is what additional spending buys. More access, more generated alternatives and fewer approval bottlenecks are different propositions. An internal review should identify which proposition justified the purchase before deciding whether higher use supports renewal.
Keep the evaluation tied to design work
The operational test extends beyond an earnings headline. Design teams can compare review time, consistency with approved components and the amount of rework required before handoff. Those are suggested evaluation criteria, not outcomes Figma has demonstrated in this preview.
After the release, the most useful follow-up will pair clearly defined company metrics with the team’s own evidence. Neither a strong supplier quarter nor a high adoption rate can substitute for checking whether the resulting work meets the organization’s standards.