SaaS template
The working application foundation: data, behavior, pages, modules, navigation, and permissions.
Choose the colors, surfaces, spacing, and mode that define your product. BuildWithHQ applies those decisions across the application—without turning your brand layer into a second codebase.
A SaaS template can include pages, records, workflows, modules, menus, permissions, and a starting theme. The theme is the visual layer you can adapt to your own brand or to each product you launch.
The working application foundation: data, behavior, pages, modules, navigation, and permissions.
The shared design system: primary actions, backgrounds, surfaces, text, borders, spacing, corner radius, and light or dark mode.
Set the primary color family, surface hierarchy, text contrast, spacing rhythm, and corner style that fit the product.
Review forms, tables, cards, charts, dialogs, empty states, errors, focus states, and narrow screens—not only a hero mockup.
Release through the builder’s supported theme workflow so applications resolve a stable, reviewable set of visual decisions.
Dark mode is not a color inversion. Each mode needs its own readable surface ladder, emphasis levels, interaction states, and contrast checks.
Clean white working surfaces, a quiet page background, navy text, and a decisive blue action color.
Layered deep surfaces, brighter interactive blue, and carefully tuned text colors for sustained product use.
Theme tokens give registered components a common source for color, spacing, and radius. That keeps the application coherent as you add pages, reuse modules, or launch another product.
The supported contract includes primary action states, page and surface colors, primary and muted text, borders, spacing, and corner radius. Advanced visual treatments belong in reviewed components, where they can be tested and versioned.
--runtime-primary--runtime-primary-strong--runtime-primary-tint--runtime-page--runtime-surface--runtime-inkBuildWithHQ keeps branding separate from authority. Tenant isolation, User Types, DataRoles, locations, server-side data scope, and registered actions remain in control.
Before release, review the states customers will actually encounter.
Build and preview without a charge while your SaaS is still in development. When it goes live, choose the commercial model that fits how you use and sell it.