What works today, apart from what is coming
What already ships comes first and in detail. What is planned sits in its own block. The two never share the same grid.
Software and SaaS
Landing pages for software and SaaS
For anyone launching software, SaaS or an app who needs a page that explains the product honestly, converts into trials or demos and is read in full by Google.
Industry
Project type
What usually goes wrong
Marketing software that is still being built is an honesty problem before it is a design problem. The easy route is to write the page as if everything already existed. The bill arrives at the first demo, when the client looks for the screen the landing page promised.
Many SaaS landing pages are built in React without prerendering. Visitors see the page, but Google and AI assistants receive almost empty HTML, and the product simply does not show up in search.
Another common problem is inflated numbers: "trusted by 500+ companies", logos of clients that do not exist. When someone checks, the product's credibility goes with it.
What a software landing page needs
The page has to match the product. Always.
Figures derived from the product
Counts of modules, screens or integrations generated from the product's real scope, not written by hand. That way the page cannot contradict the software.
Prerendering
Every route generated as ready HTML at build time, so Google and AI assistants read the full page without running JavaScript.
A clear conversion path
Free trial, demo or waitlist: one main goal per page, repeated at the right points.
Verified accessibility
State that does not rely on colour alone, keyboard navigation and checked contrast. Automated audits against WCAG 2.2 AA rules.
How ALB Seven builds it
A modern stack without extra weight
React, TypeScript, Vite and Tailwind, with prerendering at build time. The page loads fast on mobile and stays easy to maintain.
Old URLs preserved
Addresses that were already shared answer with a server-side 301 redirect, so Google transfers their history.
Audits in the pipeline
Lint, build and accessibility audit run in the same verification command before every release.
Bilingual when it makes sense
An English version with its own URL and hreflang, for products that want to sell outside Brazil.
Related work
One real project in production and two apps ALB Seven published on Google Play itself.
The landing page of a modular ERP still being built, with figures derived from the real scope and a WCAG 2.2 AA audit.
ALB Seven's app that works out selling price and profit for Shopee sellers.
ALB Seven's app with construction material calculators that work offline.
Frequently asked questions
My product is not ready yet. Is a landing page worth it?
Yes, if it is honest about the product's stage. A well-built waitlist validates interest before launch. What is not worth it is promising features that do not exist yet.
Why doesn't my React site show up on Google?
Most likely because it serves empty HTML and relies on JavaScript to build the content. The fix is to prerender routes at build time. We explain this in detail in our blog article on React sites and SSG.
Do you build the product too, or only the landing page?
Both. ALB Seven develops custom systems and apps as well as the marketing pages.
Can the landing page be in Portuguese and English?
Yes. Each language gets its own URL, with hreflang markup, so Google shows the right version to each audience.
Shall we talk about your project?
Tell us what your business does and for whom. The first conversation is about understanding the goal, not selling a package.