Figma Fails: Why It Breaks for Print Graphics! #shorts
The speaker discusses recurring failures when using Figma for print production graphics at SaaStr events. Despite warnings, sponsors repeatedly attempt to use Figma for booth graphics, and the files consistently break. The speaker argues Adobe Illustrator remains the gold standard for print production work.
Summary
The conversation begins with a brief aside about building an AEO product in Replit before pivoting to the main topic: the persistent problem of using Figma for print production graphics at SaaStr events.
The speaker explains that Figma, while widely considered the standard tool for UX and digital design, consistently fails when used for print production. Every year at SaaStr, sponsors attempt to build their booth graphics in Figma, and every year the files break in various ways. This year was no exception — three sponsors were explicitly warned not to use Figma for their booth designs, but proceeded anyway. When the proofs came back, all three files were broken, with missing layers and incomplete assets.
The speaker argues that Adobe Illustrator, despite being an older tool, remains the undisputed gold standard for print production. This has been agreed upon by the speaker, Freeman, and their production vendors as the source of truth for print-ready files. The core issue, as the speaker sees it, is that Figma was built for the online and UX design world, and attempting to use it for physical print production is fundamentally misaligned with its purpose — a mismatch that manifests as real, repeated production failures.
About this episode
Don't use classic Figma for print graphics! While great for UX, it breaks every year for production. Sponsors learned the hard way: missing layers, broken files. Stick to Illustrator for print. #Figma #Illustrator #GraphicDesign #UXDesign #PrintProduction
Key Insights
- The speaker warned three sponsors explicitly not to use Figma for their booth graphics, but all three proceeded anyway — and all three returned broken proofs with missing layers and incomplete files.
- The speaker argues that Figma's fundamental design purpose — built for UX and the online world — makes it inherently unsuitable for print production, regardless of any claims Figma may make about supporting print use cases.
- The speaker states that Adobe Illustrator has been agreed upon as the 'gold truth' for print production among themselves, Freeman, and their production vendors, positioning it as the uncontested standard despite its age.
Topics
Transcript
[0:00] Built that AEO thing that's better than HubSpot in a single crappy prompt yesterday in Replit. A single Build me a better AEO product, attach three screenshots, and boom in 5 minutes. It was pretty good, man. How How's May going to compete? Yeah, my my first version of Figma is a little different. So, it was classic Figma, right? Here's the thing about classic Figma that's always bothered me at this point in time, where we we hit these production deadlines for SaaStr. And so many folks want to build their booth graphics for print [0:31] in Figma. Yep. Every year it breaks. And so, the >> the standard, right? It is the standard. Or it has been.…
Full transcript available for MurmurCast members
Sign Up to AccessMore from SaaStr AI
Salesforce Headless: Cut Costs, Boost Data Access! #shorts
The speakers discuss their experience running Salesforce in a headless configuration within an AI-driven marketing platform, which has increased daily usage despite fewer human seats. Paradoxically, their Salesforce bill has grown compared to a year ago, even with fewer human users, due to heavy data and API consumption by AI agents.
Our Agents Drove Our Salesforce Bill Up 80%, Marketo Hates Agents, and We Stealth-Churned Off Notion
Jason and Amelia discuss running a 20-agent AI organization at SaaStr, covering their AI VP of Marketing (10K) autonomously generating campaigns, unexpected Salesforce cost increases despite fewer human seats, Marketo's broken unsubscribe flow that they fixed themselves in 20 minutes, and findings from a Redpoint survey showing 54% of CIOs are consolidating vendors.
Resend vs Marketo: Email API Battle! #shorts
The speaker compares Resend and Marketo as email platforms in an AI-driven marketing context. Resend is praised for its elegant API integration with agentic workflows, while Marketo is criticized harshly for its inaccessible API. Some friction with email domain verification is noted even for Resend.
Build vs. Buy Apps: Avoid Salesforce & Workday Nightmares #shorts
The speaker and Amelia discuss the practical challenges of building vs. buying software applications, arguing that even if you could replicate tools like Salesforce or Workday, the ongoing maintenance burden makes buying far more cost-effective. They use a real-time database connectivity issue as a concrete example of the hidden costs of self-maintained software.