.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 about page helps visitors understand what the company does, why it exists, and who is responsible for its direction. Its design should turn a company story into useful context rather than repeating the homepage's feature pitch.
A visitor should be able to describe the product and the problem it addresses after the introduction. A mission statement can support that explanation but should not replace it.
The Abstract reference combines a mission-led introduction with an origin explanation, a careers route, brand assets, and several lengths of company description.
This serves both general understanding and practical reuse of company information. Keep those responsibilities distinct so a visitor reading the story can also find a concise approved description.
Explain the problem or observation that led to the company and connect it to what the product now supports. A timeline should advance that story rather than list milestones without meaning.
Avoid inflated claims about being the only company to recognize a problem. Concrete context is more persuasive and easier to assess.
Historical details should remain accurate even when the company changes its offering. Distinguish past milestones from current capabilities.
The Reveal reference includes a product-oriented introduction, a company-history sequence, team imagery, reported figures, values, founder profiles, and a recruiting action.
This shows several ways to make an organization tangible. Values become more useful when connected to practices or decisions rather than appearing only as single-word cards.
The captured figures are historical page content, not current results verified here. Any quantitative company statement needs an appropriate period and maintained source.
Founder or leadership profiles can explain responsibility and perspective. Use relevant role context and approved information rather than including personal detail without a reason.
A full team gallery is optional. Its value depends on whether it helps visitors understand the organization and whether the company can maintain it accurately.
Photography should support the story without implying a working arrangement the company does not actually offer.
Customers may want product detail, candidates may want roles, and journalists may want approved descriptions or assets. Provide relevant routes after the corresponding context.
Avoid a generic sales CTA after every paragraph. The about page can serve several evaluation tasks without forcing them into one funnel.
If brand assets are included, label formats and usage guidance clearly. Asset retrieval is a practical task distinct from reading the origin story.
Check descriptions, leadership context, milestones, metrics, and destinations. An about page can become stale even when the product homepage is updated frequently.
Test whether a new visitor can explain the company and find the appropriate next route. Keep the page readable on mobile and through assistive technology.
Explore SaaSFrame's about-page references to compare narrative and practical company context. Choose a structure that makes the organization understandable.
No. Explain origin, purpose, responsibility, and company context while linking to product detail where useful.
No. Use one when milestones help explain the company's development rather than merely decorating the page.
Use them only with meaningful scope and date context, and keep them maintained by responsible owners.
.webp)
.avif){kind=small}
