Topics Pioneers Insight Method Author
Back

How AI Is Turning Figma’s Finance Team Into Builders

·The a16z Show

Rendering the long image…

Topics How AI Reshapes Enterprise Workflows AI Workforce Displacement and Labor Disruption Autonomous Agents Reshaping Enterprise SaaS
Pioneers Praveer Melwani Ivan Makarov Seema Amble

Summary

  • Figma’s finance team is using AI to automate collections and help test products during diligence, extending finance into building. A collections specialist rebuilt invoice tracking, cash collection and NetSuite reconciliation. Corporate development recreates products as a diligence check on technical difficulty and moat depth, while continuing to partner with the product team.
  • Finance headcount could fall if business complexity stopped growing, but that is a conditional forecast. CFO Praveer Melwani says that under unchanged complexity, “I think we probably wouldn’t need the same number of people a year from now.” Figma’s new products and acquisitions keep increasing the workload, even as efficiency improves period over period.
  • The build-versus-buy boundary favors purchased systems of record and internally built workflow automation. Melwani buys systems “we just can’t mess up,” while specialists prototype around repetitive tasks. The organizational challenge is turning successful local tools into shared infrastructure that can “live on beyond the creator.”
  • Data preparation remains the bottleneck, while acceptable precision depends on the decision. Reviewing travel and expenses for 2027 planning required matching Navan, Zip and Ramp records; Melwani says “ninety-five percent of the challenge” was getting the data together. Directionally correct analysis was sufficient for policy decisions, and revised visualizations followed his feedback within 30 minutes.
  • AI makes judgment, accountability and consistent definitions more valuable. Melwani’s hiring process tests whether candidates understand their model’s sensitive assumptions, while Ivan Makarov raises concern that companies could forget what world-class work looks like. “You don’t wanna outsource your thinking”: authors remain responsible for understanding and simplifying what others must read.
  • Finance software is moving toward completed results with an auditable explanation. Seema Amble sees products shifting from workflow tracking to delivered reconciliations plus an audit trail, and dates a substantial adoption change to roughly nine months before the conversation. Melwani hopes for more complete automation, starting with deterministic work, but audit-ready outputs still face an “extremely high” bar.
  • Access to tools and a visible building culture are becoming recruiting and retention assets. Team members tell Melwani they are having “a ton of fun,” while automated reporting frees capacity for experiments, spending decisions and investigation. His recruiting argument combines technology access with colleagues who actively build and teach one another through example.

Deep dive

1. Finance’s operating advantage starts with trusted data

  • Before AI, Melwani connected Figma’s product usage with Stripe data through queries running 400 or 500 lines of SQL. Data scientists later put his “golden tables” into recurring ETL jobs feeding Salesforce and Marketo. Consistent definitions stopped arguments over what was true and let finance become “a business enabler” rather than a “traffic cop.”
  • He once reviewed about 30 new paid-plan signups line by line, distinguishing personal from business addresses to inform Figma’s product for organizations. Today, he checks daily metrics and hourly dashboards, expecting colleagues to act rather than wait until next week. Ivan’s comparison: pandemic usage spikes once took weeks to validate; today, he thinks similar questions could be resolved in an hour.
  • On metric definitions, Melwani is categorical: “my team owns the outputs there.” Public-company controls favor consistency across board materials, earnings disclosures and historical reporting. Different ways of understanding the business are welcome, but reported measures should have longevity: “the historicals never change.”
  • Ivan’s advice to a first finance hire: establish data integrity and tracking before rushing to close books or send board updates, then build reporting rigor, metrics and the story. He has seen hires discover within several weeks that revenue was calculated incorrectly. Seema flags more “creative” early-stage ARR; Ivan says numerical storytelling once associated with IPO preparation is now expected in Series A and Series B fundraising.

2. AI strengthens the hiring case for independent judgment

  • Intellectual curiosity, data fluency, structured questions and clear communication still define Melwani’s ideal hire. His VP-finance case study supplies little information beyond available public disclosures and expects candidates to use AI. The examination is whether they understand their model, its most sensitive assumptions and the business underneath it: “you don’t wanna outsource your thinking.”
  • Ivan’s pushback — worth keeping: instant document generation can produce an unsearchable pile of work, while the shift in hiring toward tool fluency raises his concern that people could forget “what world-class looked like.” Melwani concedes he sometimes encounters half-baked output. Figma has policies for branding AI-written work, but authors still owe readers review, simplification and understanding: consuming anything takes “time, effort, and energy.”
  • Melwani’s own correction concerns influence: he initially thought he could “be the smartest person in the room and figure it all out,” then learned finance is a team sport. He had underplayed communication, relationships and persuasion. The hiring signal he now prizes is the ability to build trust and “really solid followership,” because analysis changes a business through other people.

3. Collections and acquisition diligence already have finance builders

  • In credit and collections, Kajal rebuilt invoice tracking, cash collection and NetSuite reconciliation around Figma’s existing systems. That frees time to reduce days receivable and tackle further bottlenecks, including redesigned credit checks and connected datasets. Melwani says some collections automation uses ChatGPT agents and skills; the resulting tools can also be used by colleagues.
  • Corporate development recreates products during diligence: “can you vibe code a product” helps test technical difficulty and moat depth. Melwani thinks the corporate development team is using Codex for this work. Ivan underscores that these are finance-background corp-dev staff. Melwani adds the limit: replication provides “a solid intuition,” with nuances still requiring judgment. Product remains a partner, but finance arrives with something it has already built.
  • The team also creates skills reflecting recurring leadership perspectives: “what Praveer would say,” alongside Dylan and CRO Sean. Seema calls it an LLM investment committee; Melwani agrees. Running investment memos through those personalities highlights weak sections, missing diligence and predictable questions before leadership reads them, reducing the time spent cycling through feedback together.
  • Figma Make offers another route: natural-language prompts can produce an application or website with hosting and a backend. Melwani is seeing internal use cases emerge there, which also turns finance into a source of product feedback. Building becomes a way to automate work and learn.

4. Useful analysis does not always require perfect reconciliation

  • During 2027 planning, a travel-and-expense review combined Navan, Zip and Ramp data. Matching records required judgment: was someone traveling for an offsite, and how should someone living in San Francisco who was just visiting be classified? Melwani’s diagnosis: “ninety-five percent of the challenge there is just, like, getting your data in the right spot.” For this decision, directional accuracy was sufficient.
  • The team produced suggested policy changes, then had revised visualizations ready 30 minutes after his morning feedback. Melwani doubts they could have done the work by hand. His counterweight to the slop critique is purpose-specific precision: understand “what is good enough and what needs to be, like, really, really picture perfect.”
  • Seema describes another growth-stage finance team creating 40 or 50 agents in a month or two. She guesses “maybe ninety percent” are no longer used, but values the habit the exercise developed: when work is manual and tedious, “let me build.” Melwani agrees, particularly when teams share what others might reuse.

5. Local prototypes need shared ownership to survive

  • A speaker offers the failure case: a customer-success leader found every rep had vibe-coded a different dashboard, with different numbers. Melwani sees a systems opportunity in repeated audit-evidence requests, GRC work across ISO and SOC 2, and accounts-payable approvals. These share a pattern of chasing information, triaging and reconciling; a systems team can turn scattered tools into a shared platform.
  • Specialists should invent and iterate because they know the process and “what good looks like.” Maintaining upstream dependencies, arranging durable hosting and ensuring tools survive their creators’ departure need different ownership. Newly arrived CIO Kasper Sørensen, from Coinbase, is exploring centralized product-management-style functions that identify useful local tools and build foundations others can extend.
  • This remains unfinished: “we’re in the messy middle right now.” Some teams have centralized better than others; Melwani has prioritized letting people build and is catching up with infrastructure. Seema finds similarly unsettled finance-engineer roles elsewhere, filled variously by engineers inside finance or product engineers borrowed from another team.
  • Domain context matters. Figma’s finance-supporting data scientists include people with accounting backgrounds who understand refunds, uncollectibles and the requirement for correctness. Builders move faster when they understand dataset architecture, distinguish deterministic decisions from inference and know which tasks can tolerate each. FigNation demonstrations, hackathons and conversations with outside finance leaders help spread that understanding.

6. Buying core systems leaves room to build better working days

  • Ivan presses the alternative: a hypergrowth company told him it had to buy everything off the shelf because it was moving too quickly. Melwani agrees for core systems of record and things “we just can’t mess up.” His team builds around repetitive workflow steps, finding tasks where someone is “almost, like, not thinking” and redesigning how that time gets spent.
  • The payoff appears in retention conversations. Team members tell Melwani they are having “a ton of fun” and want to stay because they can explore and learn. He has begun selling technology access in recruiting, particularly to candidates outside technology who see it as an entrance into a new professional world.
  • Ivan suggests treating models and tools like perks and benefits. Melwani adds that candidates should see colleagues actually building, including during interviews: learning happens through “osmosis of what others have built too.” He thinks developing one’s craft among similarly motivated peers can help Figma attract and build “the world’s best finance organization.”

7. Freed capacity is moving toward experiments and business decisions

  • Seema recalls her 2020 framework: finance spent most of its time reconciling data and the smallest share on strategy. Melwani’s self-serve finance team can now focus more on experiments, trends and additional spending. Automating recurring materials shifts effort toward “the annotation, the discovery, the understanding.” He recalls a team discussion of Figma plug-ins to accelerate ideation, although growing complexity still competes for the saved time.
  • Seema sees CFO software moving from workflow tracking to a result plus the audit trail explaining it. Melwani’s accounting example is flux analysis: tools can offer an initial explanation of period-over-period general-ledger changes, giving accountants threads to pursue. He does not claim the first explanation is always right; it provides a better starting point for investigation.
  • The CFO Melwani wants shares the CEO’s business ownership and desire to win, using P&L knowledge to drive change and simplify the business model for others. Accounting fundamentals and planning remain prerequisites. Creativity means finding another business angle, not inventing “a fun, funky set of metrics.” He tries to generate those ideas but does not know whether he does it as much as he could.
  • Seema dates a marked adoption shift to roughly nine months earlier: CFO dinner conversations moved from AI-generated tax memos and onboarding documents to core reconciliation and automated workflows. At board level, she sees deeper analysis and faster iteration. Leaders increasingly feel they must adopt the tools or be perceived as behind; finance now participates in automation hackathons.

8. Efficiency can reduce staffing needs while Excel retains its role

  • Asked about the next 12–18 months, Melwani gives a conditional staffing call: “if our business complexity was, like, staying the same, I think we probably wouldn’t need the same number of people a year from now.” Figma keeps adding products and acquiring teams and businesses, so complexity still outpaces complete efficiency. Nevertheless, he sees improvement period over period.
  • He hopes more processes become fully automated, beginning with deterministic work supplied with enough information to make outputs completely trustworthy. Business-critical, audit-ready results face an extremely high bar, including what auditors will accept. His expectation remains: “I do think we’ll get there over time.”
  • Is Excel under threat? Melwani’s answer is categorical: “No, it’s like my love language, dude.” His analogy is Figma’s color wheel: prompting a change from red to green is useful, but moving directly through shades builds understanding differently. Spreadsheets similarly let him refine intuition by hand. Something better may emerge, but he would find Excel hard to surrender.
  • Seema adds a limit: models are not “quite good enough” to create a forecast or model yet, while Excel’s spatial organization helps her think. Melwani uses AI to review a team’s 20-tab model, finding sensitive assumptions and important variables before investigating himself. His durable criterion is adaptability: “a great finance person” has longevity “if they continue to adapt.”