.webp)
We sell SaaSFrame licenses on Gumroad, a secured online selling platform for creators.
SaaSFrame gets updated all the time! Every new update and version will immediately be made available to all SaaSFrame users.
The licence key required to create your SaaSFrame account is send by Gumroad once you made your purchase. If this email is blocked by your email client, send me an email at antoine[at]unmake[dot]io so I can resend the licence key.
You can generate an invoice on Gumroad once you purchased SaaSFrame. You will find the link in the order confirmation email.
If you're not satisfied, you can ask for a refund within 7 days. Just send me an email at antoine[at]unmake[dot]io
A SaaS integrations library helps visitors find a supported connection and understand what that connection enables. Its design should make a growing ecosystem searchable without turning the page into an undifferentiated wall of logos.
The SaaSFrame references show different ways to organize discovery. Their integration counts and availability belong to the captured pages and should not be treated as current inventories.
A visitor may arrive with a specific application in mind. Give that person a recognizable search route and make result names match the terminology they are likely to use.
Keep the active query and filters visible. A no-results state should explain the current scope and offer a way to clear it before suggesting that the product lacks a connection.
Search and browsing support different intentions. Preserve both when visitors may know either the tool name or only the workflow they want to improve.
The Hotjar capture separates popular integrations, installation-related connections, and integrations through Zapier. Cards include short descriptions and provider context.
This prevents a logo from implying that every connection has the same implementation. A native connection, installation plugin, and third-party automation route can require different setup and support.
Use badges or grouping that describe meaningful differences. Do not imply equivalent capabilities simply because two tools appear in the same grid.
A name and icon identify a service, but a short description should explain what the integration does. Connecting survey responses to a contact record differs from installing a tracking script.
Keep descriptions concrete and comparable. Each card should give enough information to decide whether opening the detail page is worthwhile.
Avoid repeating the same generic automation sentence for every tool. The library becomes more useful when visitors can distinguish data movement, triggers, and installation purpose.
The Livestorm reference combines a category sidebar, search, a featured area, and a long card collection. The sidebar provides a stable browsing route through a large catalog.
Categories should describe recognizable tool families or workflow purposes. Overly broad groups leave too many results; overly narrow groups make browsing fragmented.
Featured connections can help orient newcomers, but they should not hide the full inventory or imply availability that the detailed route cannot support.
The Glide integrations capture shows tool categories and search above a grid, then explains a conversational connection experience through a sequence beneath the catalog.
This connects finding a tool to understanding the setup model. The page's displayed claims are marketing content, not independent proof that every listed connection follows identical steps.
For your library, explain required accounts, permissions, plan access, or installation routes on the relevant detail page. A successful search is only the beginning of evaluation.
A requested tool may not be supported, may require another connector, or may be planned. Those states need distinct labels and destinations.
If visitors can request an integration, describe the request as feedback rather than a promise of delivery. Avoid placing planned connections among available ones without a clear distinction.
Maintain the relationship between cards and detail pages. A polished directory becomes frustrating when its links lead to obsolete setup instructions or unrelated sales pages.
Use consistent card structure and readable labels. Logos should support recognition while text preserves meaning when an image fails or a brand changes.
Review long names, small screens, loading, keyboard navigation, and filter resets. A dense catalog should remain usable without requiring precise pointer interaction.
If pagination or progressive loading is used, preserve the visitor's position and filter state when they return from a detail page.
Explore SaaSFrame's integrations-library references to study search, grouping, and card descriptions. Choose the discovery structure around how users evaluate connections, not the number of logos the page can display.
No. Include the connection's purpose and relevant type so visitors can judge whether it supports their task.
They can, when their differences are clear. Explain setup and support implications in the relevant detail route.
Show the current query and filters, offer a reset, and distinguish unsupported tools from other availability states.
