SaaS releases new features every month: how to maintain consistency

SaaS startups have a characteristic that most other industries do not: the product changes while customers are using it. A new feature every month, a new interface every quarter, and potentially a different market direction every year. This is both a competitive advantage and the reason many startups find that after three years, their brand looks like four different companies.

The issue isn’t about changing a lot or a little. The problem lies in the fact that most product teams cannot distinguish which parts of the brand are allowed to change and which are not.

Why SaaS easily loses its foundation

In most industries, the brand and product are two separate entities. A beverage company can change flavors without touching the packaging. A fashion house can launch a new collection without changing the logo. But with SaaS, the product is where the brand appears every day, directly on the user's screen.

When the design team updates the button color to increase the conversion rate (the rate at which users take the desired action), when the marketing team uses a new tone for the feature launch campaign, when the sales team creates slides with a different font because the old design "looks unprofessional," all these actions happen simultaneously and no one sees the big picture. After a year, the brand identity has diverged significantly without any specific decision causing it.

What this number indicates is that the problem isn’t a lack of guidelines. The problem is that the guidelines do not operate at the actual working pace of the SaaS team.

Two layers of brand need to be separated

Sinh Vũ's approach to digital products is to divide the brand system into two clear layers, with different rules for each layer.

The first layer is the fixed part, consisting of elements that customers use to recognize the brand even without looking at the logo: primary color, font family, product and feature naming conventions, tone in announcements and documents, and how the brand appears at the most important touchpoints (places where customers encounter the brand) such as the login page, transactional emails, and error messages.

The second layer is the flexible part, consisting of elements that need to change with each feature, each launch, and each customer segment: secondary colors for new modules, layout for feature introduction pages, update announcement templates, specific tones in user manuals.

When these two layers are clearly distinguished from the start, the product team knows where they can operate freely and where they need to ask for guidance. There’s no need to hold meetings for every small design decision, but it also prevents someone from accidentally changing the primary color because it seems "more suitable for the new feature."

Design token: one place to change, everywhere to

For digital products, there is a technical tool that helps the fixed layer truly remain fixed: design token. This is a way to store values like colors, font sizes, and spacing in one place, so when changes are needed, the entire product updates simultaneously without having to fix each screen individually.

Salesforce and Google Material Design have used this approach at a scale of millions of users. But the principle is entirely applicable for startups with five or more people. The one-time setup cost and maintenance costs are much lower than the cumulative cost of fixing inconsistencies month by month.

Brand equity can only accumulate when identity signals are consistently repeated. Consistency is not about aesthetics; it’s about memory mechanisms.

Jenni Romaniuk, Building Distinctive Brand Assets, 2018

Old customers: an asset easily forgotten

SaaS startups often focus their feature launch messaging on potential customers. But current users also read those announcements, and they read them with a different mindset: they are checking whether the product they are paying for is heading in the right direction.

When an update announcement is written in a technical style ("version 3.2.1: fixed bug in API endpoint, added new dashboard module"), users do not see the brand; they see a patch. When that announcement is written in the true brand language, following the established tone, users see the team behind the product working with intention.

The difference is not just in the wording. It’s a signal to users that the company knows where it is headed.

When to update the system

Not every change needs to touch the fixed layer. However, there are times when the brand system needs to be intentionally reviewed, rather than patching up each spot.

• When the product expands into a new customer segment that is significantly different from the original.
• When the design and content team is so large that no one has a grasp of the entire system.
• When you notice design assets across different channels starting to look like they come from multiple different companies.
• When preparing to raise funds and realizing that the current brand does not accurately reflect the scale and direction ahead.

During those times, the task is not to redesign from scratch. Often, it’s just necessary to revisit the two layers of branding, confirm what still holds true and what needs upgrading, and then clarify the documentation.

A SaaS brand doesn’t need to be static, but it requires a system to change proactively. Without a system, every small decision accumulates into a significant gap between the brand you are building and the brand your customers actually perceive.