figma.com - Vishal Kapoor’s 10 Rules for Building Honest Products with AI Figma Blog
Vishal Kapoor’s 10 Rules for Building Honest Products with AI
Section titled “Vishal Kapoor’s 10 Rules for Building Honest Products with AI”Vishal KapoorSVP of Product, Affirm

Building with AI isn’t just a technical challenge—it’s a trust challenge. This is especially relevant at Affirm, which empowers customers with transparent, flexible payment plans to take better control of their financial lives. Given the deeply emotional nature of personal finances and the often-convoluted terms of credit card companies, earning user trust is key to Affirm’s mission and enduring success.
Having spent his career at the intersection of engineering, product, and design, Vishal Kapoor, SVP of Product at Affirm, is tackling this emerging challenge from multiple angles. As AI becomes embedded in everyday workflows, we asked Vishal to share how he helps teams accelerate development, explore more ideas, and still deliver experiences that are honest and human at their core. Distilled from that conversation, here are 10 rules for navigating what Vishal calls “the fun and messy middle” of AI adoption to build truly trustworthy products.
1. Put a High Premium on First-principles Thinking
Section titled “1. Put a High Premium on First-principles Thinking”I’m an engineer by training, and at heart, so I approach systems problems from first principles. When tackling a complex challenge, I deconstruct it into its fundamental components to understand the larger puzzle. The end-to-end process of uncovering customer needs, finding a differentiated way to address them, and navigating the S-curves of iteration—that is the joy of building. While AI can accelerate and augment this process, it cannot replace it; having a unique perspective and intuition remain inherently human.
For example, we offer most approved customers three payment plan options after a real-time eligibility check. I recently challenged the team: “Why three plans? Why not five? Why not one? Why not let customers create a custom plan?” The power of asking these fundamental questions is that it forces diverse and often original viewpoints. AI can help us explore alternatives faster, but critical insight comes from thoughtful human disagreement.
AI can help us explore alternatives faster, but critical insight comes from thoughtful human disagreement.
2. Stay Grounded in Deep Human Emotions
Section titled “2. Stay Grounded in Deep Human Emotions”There is immense value in being close to customers and remaining humble about their problems. There is no substitute for rolling up your sleeves, visiting a UX research lab, and observing how real customers use the product by asking direct questions. I actively track social media and app store reviews, and speak with customers whenever possible, especially with strangers who recognize the Affirm logo on my shirt. We even have an internal AI-powered tool called Pluto that I can query directly: “How have our customers been disappointed with us in the last 30 days?”
Dashboards and metrics matter, but data only points the way. To truly understand customer needs, you must experience how human emotions underpin finance. Anxiety, trust, frustration, and relief all surface during checkout. It’s not about the bike you are buying; it’s about the unadulterated joy it’ll bring.
3. Treat AI like Another Teammate
Section titled “3. Treat AI like Another Teammate”In the early stages of any new technology, we tend to swing to extremes—believing AI will either make us 10x faster, or replace us entirely. The reality is far more practical.
When we first piloted AI tools, there was understandable hesitation across the board. What we quickly realized is that since building products is inherently a team sport, AI is simply one more member of that team: one that helps us turn customer insights into tangible prototypes and real products much faster.
For instance, we run different flights of experiments because checkout flows vary across web, mobile, and desktop. We use various AI tools, including Fi gma Make, to help ensure there are no broken windows in the system—say, if we want to update an interaction pattern across all screens. Auditing every single screen for every modality and use case could take months. Make helps us identify early on how to replace outdated design patterns across all these different surfaces. Crucially, by taking cycles away from engineers and putting them back into the hands of designers and PMs, we accelerate velocity and unlock more creativity across the organization.
4. Spike on the Edge Cases
Section titled “4. Spike on the Edge Cases”Building a delightful and authentic product means looking beyond the high-level happy path. The deepest, most valuable work lies in the variations, the rabbit holes, and especially the edge cases. Navigating that terrain demands intense focus, precision, and a lot of love.
One challenge we faced was helping customers decide between 6-week, 6-month, and 12-month payment terms at checkout. Previously, we didn’t fully explain why those options existed. Through research, we knew customers fall into three clear buckets: those seeking 0% APRs (or minimal interest), those who want the shortest possible plan, and those managing cash flow with the smallest monthly payment. Our solution was to show clear badging for each goal, but without overwhelming the customer. The question was: Which badge to show, to which person, on which checkout, on which device?
Affirm prototyped some early explorations of badging for their checkout flow in Figma Make, clarifying directions for the final screens.
This is a complicated problem to solve at scale, so we rapidly prototyped different options. Instead of taking six weeks to validate an idea and take it to production, we can do so in a matter of days. This capability dramatically expands the number of ideas we can explore at any given time.
5. Embrace the counter Metrics
Section titled “5. Embrace the counter Metrics”When prototyping and evaluating ideas, we don’t just look at the success metrics; we pay a lot of attention to the counter metrics. In the badging example, we focused on people who may have unintentionally completed their purchase out of confusion. If I were to just look at conversions, I would say it’s a win. But if I look at complaints and refunds, I would say it’s a loss. We actively track customer dissatisfaction (DSAT) metrics during product reviews to truly understand how features perform in customers’ hands and across different modalities.
The ability to validate and test quickly allows us to preempt customer dissatisfaction with more realistic prototyping. This ensures we gather higher-quality qualitative data before a single line of production code is written.
6. Rapidly Experiment, and Fail Fast
Section titled “6. Rapidly Experiment, and Fail Fast”We are always asking ourselves: How can we experiment and build 10X better products? With tools like Figma Make, Claude, and Cursor, our prototypes are production-ready faster, significantly reducing front-end development time. Because we’ve connected our design artifacts through the Figma MCP server, we can vibe code to continuously iterate on prototypes.
Taking the Affirm app as an example, designers aren’t just creating mockups—they’re building real proofs of concept with Cursor and our app. Since the design system maps directly to our codebase, we maintain design intent from concept to launch. We are also able to move 10x faster with testing variants because the cost of prototyping has reduced by several degrees.
7. Use Creativity as a Competitive Advantage
Section titled “7. Use Creativity as a Competitive Advantage”Previously, PMs at Affirm used Figma to review designs, not author them. But because our amazing designers showed the power of Figma Make, our product team has been inspired to create prototypes directly in the tool, which then form the foundation for product requirements documents (PRDs).
As an example, we were working with Shopify to move a disclosure and change which term would be preselected in the Shop Pay Installments flow. The next day, a prototype landed in my inbox from a PM—I was genuinely surprised. This visual representation became the robust foundation for the PRD, which we still perform due diligence on. AI tools accelerate that process by gleaning insights, helping with formatting, and providing immediate critique. It also helps us see around corners for things like errors and missed states before we go into production.
8. Blur Functional Silos and Treat Everyone like a Builder
Section titled “8. Blur Functional Silos and Treat Everyone like a Builder”Traditionally, a feature used to flow in a waterfall: written in a PRD by a PM, translated into a Figma file by a designer, coded by an engineer, and finally QA’ed and deployed. All of that is up for grabs because AI is democratizing the skills required across all these stages. Engineers can now modify design artifacts; product managers can push code into pre-production to understand the look and feel; and designers can create PRDs—or even production-ready code.
Our roles will continue to blur, opening up a new world of possibilities and collaboration. We all have powerful ideas, but bringing them to life was the constraining factor. AI is injecting the joy and energy of building into functions that previously lacked access. We are living in the golden age for builders. The future belongs to the curious.
We are living in the golden age for builders. The future belongs to the curious.
9. Make it Fun (and safe) to Tinker
Section titled “9. Make it Fun (and safe) to Tinker”As a leader, one of my most important jobs is to inspire curiosity about what AI tools can do. Increased usage drives proficiency in identifying where these tools help and where they fall short. The name of the game is continuously testing systems, monitoring the state of the art, and trying to stay two steps ahead.
To that end, we founded an AI enablement steering committee that keeps teams abreast of the latest developments and triages inbound requests for new tools. Our security and procurement teams set up a pilot for that team or individual, inviting them to kick the tires. The most advanced users help us identify the tools ready for larger adoption and create robust on-ramps. Once a tool is widely available, we track active usage, publish reports on which teams are using which products at what frequency, and run qualitative surveys to understand how they’re helping teams do their jobs better. We are still in this messy middle, but we have turned the tide and converted many AI skeptics into AI advocates.
10. Be Very Careful about “AI slop”
Section titled “10. Be Very Careful about “AI slop””Trust is everything to our mission, and how we build that is through simplicity and transparency. In this golden age of AI, it is dangerously easy to create too much complexity and unintentional “slop.” It’s easy to experiment, throw things at the wall, and see what sticks. The true art and challenge lies in using AI to distill and deliver a product that is profoundly simple and transparent—one that is rooted in authentic customer problems and original perspectives.
How do you harness all that energy and excitement to create something truly compelling? Simplicity is the critical competitive advantage, and it’s achieved by an endless pursuit of excellence.