Concord Group: Brand Cohesion Post-Merger in 2026

Listen to this article · 19 min listen

Keeping a brand’s identity straight across a bunch of different products is tough, and it gets ten times harder after a big marketing merger. Look at the Concord Group, which just crammed its streaming and smart home divisions into one app. It’s the perfect example of the chaos that follows. The big question becomes how you make sure every single user interaction, from a button press to an error message, feels like it’s coming from one, unified brand.

Key Takeaways

  • Standardizing your design tokens across all app interfaces will cut development time by a solid 30% and keeps the visuals from drifting apart.
  • Use a centralized content management system (CMS) with version control for every marketing asset to stop brand drift before it starts.
  • Run brand audits every quarter with AI-powered sentiment analysis tools, which can spot inconsistencies in your messaging with about 90% accuracy.
  • Training all your customer-facing teams on one set of brand guidelines can bump customer satisfaction scores by an average of 15% after a merger.

Setting Up Your Centralized Brand Asset Management System

The only way to achieve any real brand cohesion, especially after jamming two marketing departments together, is to build a centralized asset management system. If you don’t have a single source of truth for your logos, colors, and fonts, you’ll get inconsistencies creeping into your app and marketing. We watched this happen in real-time during the first phase of Concord’s integration, with one team using an old logo while another used a slightly-off brand color from a forgotten Sketch file. It’s a completely preventable mess, but it demands discipline.

Step 1: Selecting and Configuring Your Digital Asset Management (DAM) Platform

In 2026, your best bets are platforms like Bynder or Adobe Experience Manager Assets. For this walkthrough, we’ll use Bynder since it’s known for being user-friendly and having great integrations. First, get into your Bynder instance. From the main dashboard, hit Settings in the top right corner, then find Asset Types & Metaproperties in the left navigation menu.

  1. Define Asset Types: Don’t just dump everything into one folder. Create specific asset types like “Primary Logo,” “App Icon,” “Brand Color Palettes,” “Approved Fonts,” “Product Photography,” and “Lifestyle Imagery.” This kind of granular structure means people can actually find what they’re looking for fast.
  2. Establish Metaproperties: For every asset type, you need to define its rules. A logo needs metaproperties for “Usage Guidelines,” “Minimum Size,” and “Clearance Zone.” A color needs “Hex Code,” “RGB Value,” and “Pantone Match.” This data is what stops a designer in another country from stretching your logo or using the wrong shade of blue on a print ad.
  3. Implement Version Control: Make sure version control is on for your key assets. In Bynder, you’ll find this under Settings > General Settings > Asset Versioning. This feature is your safety net, letting you track changes, roll back to an old version when someone messes up, and stop the team from using that one outdated logo that just won’t die. A 2025 Nielsen report actually found that brands with tight version control had a 22% higher brand recall rate.

Pro Tip: Integrate your DAM directly with Figma or Sketch. The single biggest reason for brand drift is the friction of a designer having to download an asset, save it, and re-upload it to their project. Making them pull the latest approved assets directly from the source cuts out that entire error-prone step.

Common Mistake: Just uploading a logo file and calling it a day. That’s not enough. You have to be explicit about how to use it, where to use it, and, most importantly, all the ways you’re forbidden from using it. If you don’t spell out the rules, your teams will just make them up as they go.

Expected Outcome: You’ll have one searchable place for all approved brand assets, complete with all the metadata and rules, that every team can access. This alone can cut down the time people waste hunting for the “right” logo by hours each week and guarantees everyone is using the current stuff.

Developing a Unified Design System for App Interfaces

A merger means you’re not just combining marketing teams. You’re often smashing together two completely different apps with their own look and feel. Concord had exactly this problem, with two UI/UX teams who had their own design libraries and ways of working. A unified design system is the blueprint that forces everyone to build things the same way, creating a consistent experience and putting your app brand strategy into practice.

Step 1: Auditing Existing Design Components and Identifying Overlaps

You can’t build something new until you know exactly what junk you have lying around. This part is a grind, but it’s not optional. Open up both of the old apps on your screen. Go through and list out every single UI component you can find: buttons, input fields, nav bars, icons, modals, text styles, and colors. You have to document every state, too (what does a primary button look like by default, on hover, when pressed, and when disabled?). This visual inventory is where you’ll see just how bad the redundancies and inconsistencies really are.

  1. Component Cataloging: Start a new file in a tool like Figma or Sketch. Pull in or just recreate every unique component from both apps. Be super clear about labeling where each one came from.
  2. Style Guide Comparison: Pull out the typography scales (all the font families, weights, and sizes for headings, body copy, etc.) and color palettes from both apps. Find where they use different colors for the same purpose. Is the “success” green the same hex code in both places? Probably not.
  3. Interaction Pattern Mapping: Write down how common things work. Does a confirmation dialog have the same buttons and behavior in both apps? Do the form validation messages pop up in the same way?

Pro Tip: Make sure you have people from both of the original design teams in the room for this audit. They’ll have the institutional memory to explain *why* a certain button looks the way it does, which might stop you from throwing out a component that actually solves a very specific user problem.

Common Mistake: Getting excited and immediately starting to build new components before you’ve done a full audit. You’ll just end up with a “Frankenstein” system that stitches together the ugliest parts of both old apps instead of creating something clean and cohesive.

Expected Outcome: You’ll have a brutally honest map of all your existing UI components and styles, which clearly shows where things are broken, inconsistent, or ripe for unification.

Step 2: Defining Core Design Principles and Guidelines

Once you’ve surveyed the mess, you can start defining the principles for the new, unified experience. These aren’t just fluffy aesthetic goals. They’re the hard rules that will guide your entire app brand strategy. For Concord, their guiding principle became “Effortless Control,” a simple phrase reminding every designer and developer that every interaction should feel direct and intuitive, reducing how much a user has to think.

  1. Brand Voice and Tone: Turn your brand values into actual rules for writing copy. Is your app’s tone friendly and a little casual, or is it straight-to-the-point and authoritative? Write out good and bad examples for things like error messages and onboarding screens.
  2. Accessibility Standards: Set a hard target for accessibility, like full WCAG 2.2 compliance. This means defining minimum color contrast ratios, font sizes, and tap target sizes. It opens up your app to more users and has the side effect of forcing designers to be more disciplined.
  3. Motion and Animation Guidelines: Decide how things on the screen should move. Are your animations quick and functional, or are they more expressive and fun? Being consistent with motion, even for tiny micro-interactions, gives the app a much more polished and professional feel.

Pro Tip: Come up with a short, memorable mantra for the whole design system. Concord used “Concord Connect: Simple, Smart, Secure.” It’s cheesy, but it helps a developer in a hurry remember the goal behind the component they’re building.

Common Mistake: Writing rules that are so strict they kill all creativity. A good design system gives people guardrails, not a straitjacket. You have to leave some room for designers to solve new problems in the future without breaking the whole system.

Expected Outcome: A documented set of principles that acts as the philosophical and practical rulebook for anyone building a piece of your app’s interface.

Step 3: Building the Unified Component Library

Now you get to build. Using your design tool of choice (again, Figma or Sketch), you’ll construct the new, single component library. This library needs to be shared and have version control, just like your brand assets in the DAM.

  1. Standardize Color Palettes: Choose your final primary, secondary, and accent colors, plus the semantic colors for success, warning, and error states. Document their hex codes and when to use them. Make this an official, linked color palette in your design tool so it can be applied automatically.
  2. Define Typography Scales: Pick one main font family. Define a very limited set of sizes, weights, and line heights for everything from H1s down to captions and button labels. Create these as text styles in your design tool.
  3. Rebuild Components: Go through and systematically rebuild every component, buttons, inputs, cards, using your new standardized colors and typography. For something like a “Button,” you’ll build one component with variants for its primary, secondary, disabled, and loading states, ensuring they all have the same padding and corner radius.
  4. Create Iconography Set: Design a single, unified set of icons for the whole app. They should all have the same line weight and visual style, so a “settings” gear looks like it belongs next to a “profile” icon.

Pro Tip: Build the most common components first, buttons, text fields, navigation. This lets the dev teams start using the new system in their next sprint, which shows immediate progress and helps get everyone on board.

Common Mistake: Trying to save every weird, one-off component from the old systems. You have to be ruthless about cutting things out and simplifying. A cohesive design system is often about what you remove, because fewer, more flexible components are far easier to maintain.

Expected Outcome: You get a complete, well-documented component library that anyone can access which guarantees your app looks and works the same everywhere. This directly builds your brand by giving users a predictable, familiar experience every time they open the app.

Implementing Unified Content and Messaging Strategies

Visuals are only half the battle. True brand cohesion means you have a unified voice. A merger can be incredibly jarring for users if one part of the app sounds like a stuffy banker and the other sounds like a teenager. Concord’s big challenge was merging two very different groups of customers who were used to different communication styles, and they solved it with a centralized content strategy.

Step 1: Establishing a Centralized Content Management System (CMS)

You absolutely cannot manage this with Google Docs. You need a real CMS to control marketing copy, in-app notifications, and support articles. In 2026, headless CMS options like Contentful or Strapi give you the flexibility to push content to multiple platforms from one place.

  1. Content Model Definition: In your CMS, create models for all the different kinds of text you use, like “Marketing Campaign Copy,” “In-App Notification,” or “FAQ Article.” Each model needs fields for the title, body, call-to-action text, target audience, and an approval status.
  2. Workflow Automation: Set up an approval workflow. A piece of copy might need to be written, then go to an editor, and finally to a brand manager before it can be published. This workflow ensures everything is checked for tone and accuracy.
  3. Multi-Channel Publishing: Connect your CMS so it can push content directly to your app, website, email platform, and social media. This is how you prevent the tiny but damaging errors that happen when someone has to manually copy and paste the same message into five different systems.

Pro Tip: Connect your CMS to an AI-powered writing assistant. You can configure a tool like Grammarly Business with your brand’s specific style guide, letting it catch awkward phrasing or off-brand words before a human editor even sees the draft, saving your brand manager a ton of time.

Common Mistake: Using the CMS as a simple file cabinet for text. The real value is in the workflows and publishing integrations. If you ignore those, you’re still basically managing everything with chaotic, ad-hoc processes.

Expected Outcome: You get a single, controlled place for every piece of brand-related text, which enforces consistency in tone and terminology across every single place a customer might interact with you.

Step 2: Developing a Unified Brand Style Guide for Copy

Just like with design, you need a style guide for words. This is more than just a grammar rulebook. It defines your brand’s written personality. Concord’s guide, for example, had a strict rule to always use active voice, avoid technical jargon, and keep the tone helpful but not overly casual.

  1. Vocabulary and Terminology List: Make a glossary of approved words for your products. For instance, if you sell “smart home automation,” you need to decide if you’re going to call the things in the house “devices,” “gadgets,” or “appliances” and then stick with it. This stops support agents from using a different term than what the user sees in the app.
  2. Tone of Voice Guidelines: Show, don’t just tell. Provide actual examples of good and bad copy for different situations, like what to say during onboarding versus what to say in an error message.
  3. Call-to-Action (CTA) Best Practices: Standardize the phrasing for your buttons and links. Do you use direct commands like “Learn More” and “Shop Now,” or are they more benefit-oriented like “Discover Your Options”?

Pro Tip: Give this style guide to everyone, not just the marketing team. Your customer support agents and even your developers need to know how to talk about the brand, because a support email that contradicts an in-app message creates a disjointed and untrustworthy experience.

Common Mistake: Writing a style guide that’s too academic or vague to be useful. It needs to be a practical document with clear, actionable examples that a busy writer or support agent can apply immediately.

Expected Outcome: A clear, complete guide that makes sure all your written communications sound like they’re from the same brand, which constantly reinforces your app’s identity.

Monitoring and Iterating on Brand Cohesion

Brand cohesion isn’t a one-time setup. It’s something you have to constantly police, especially after a merger when things are always changing. Concord found that even with a great system in place, little inconsistencies started popping up over time because no one was actively looking for them.

Step 1: Conducting Regular Brand Audits

You need to schedule formal audits every quarter to look at everything your customers see. This should be a mix of automated scanning and human review.

  1. Visual Consistency Check: Use a tool like Brandgility or even a custom script to crawl your app, website, and ads to look for problems. These tools can automatically flag things like wrong fonts, off-brand colors, or a logo that’s been squashed.
  2. Content Voice and Tone Audit: Use AI-powered NLP tools to analyze the sentiment of your marketing emails, in-app copy, and support chat logs. You can then compare the results to the tone you defined in your style guide to see where you’re drifting.
  3. User Feedback Analysis: Scour your app store reviews, social media mentions, and support tickets for any hint of brand-related confusion. Are people saying they’re surprised by a change, or are they talking about the experience as if it’s one unified product?

Pro Tip: Name one person or a small committee as the official “Brand Guardian.” This person’s job is to run these audits and be the final judge when there’s a disagreement between teams about a design or copy choice.

Common Mistake: Thinking automated tools can do it all. They’re great for catching obvious errors, but you still need a human with good judgment to evaluate the nuance of brand voice and the overall feel of the user experience.

Expected Outcome: You’ll be able to spot brand inconsistencies early, letting you fix them before they grow into bigger problems that erode user trust or make your brand look sloppy.

Step 2: Establishing a Feedback Loop and Iteration Process

You need a clear process for how anyone in the company can report a brand problem and know that it will be addressed. This feedback loop is what keeps your brand guide from becoming outdated.

  1. Dedicated Reporting Channel: Make it easy for people to flag problems. Set up a dedicated Slack channel or a specific JIRA ticket type called “Brand Inconsistency” so that everyone feels empowered to be a brand advocate.
  2. Regular Review Meetings: Once a month, get the key people from design, marketing, product, and support in a room to review the audit findings and any issues that have been reported. This is where you decide what to fix.
  3. Design System Updates: Your design system and style guide are living documents. When you decide to make a change based on feedback, update the official documentation and make sure you announce that change to the entire company.

Pro Tip: When you update a guideline, always explain *why* you’re making the change. This helps people understand the thinking behind it and reduces the number of arguments you’ll have in the future because everyone is aligned on the goal.

Common Mistake: Building a great system but providing no way for it to be updated. In a fast-moving market where new features are constantly being added, a brand guide that can’t evolve will be ignored and become useless within a year.

Expected Outcome: You’ll have a process that lets your brand evolve in a controlled way, adapting to new challenges while keeping its core identity intact and ensuring your brand cohesion holds up for the long term.

Putting a real framework in place for brand cohesion, like the one Concord Group used for its integration, takes serious planning, centralized tools, and constant oversight. If you focus on standardizing your assets, unifying your design system, and controlling your content strategy, you can make sure your app brand feels solid and reliable to your users. For more on how AI can help with this, check out AI Marketing: 2026 Hyper-Relevance via 15% CTR Jump. It’s also worth understanding how Adobe Agentic CX: Redefining In-App AI by 2026 will change the game for future-proofing your brand’s digital interactions.

What is a design system and why is it important for app brand strategy?

A design system is the single source of truth for a digital product’s look and feel, containing all the standards, reusable components, and guidelines. It’s critical for an app’s brand strategy because it enforces visual and functional consistency, which speeds up development, makes the user experience better, and reinforces the brand’s identity by making every part of the app feel predictable and familiar.

How often should a brand conduct a brand audit?

You should run a full brand audit at least quarterly, but you need to be continuously monitoring high-stakes things like new ad campaigns or major app updates. This cadence lets you catch inconsistencies like off-brand colors in an ad or confusing copy in a new feature before they do real damage, and it keeps your guidelines from becoming irrelevant as the market changes.

What are “design tokens” and how do they contribute to brand cohesion?

Design tokens are the atomic-level pieces of a design system. They’re not the components themselves, but the raw values for things like a specific color hex code, a font size, a spacing unit, or an animation speed. They are essential for cohesion because they create a single source of truth that code can reference, meaning if you update a token for your primary brand color, that change automatically populates across every button, link, and background where it’s used.

Can a small team effectively manage brand cohesion after a merger?

Yes, but only if they are disciplined about centralization and process. A small team can’t afford to have assets and rules scattered everywhere, so a solid Digital Asset Management (DAM) system, a headless CMS, and a well-documented design system become even more important. They have to rely on automation for auditing and a very clear feedback loop to scale their impact without just hiring more people.

What is the role of AI in maintaining brand cohesion in 2026?

By 2026, AI’s main job in brand cohesion is automating the tedious monitoring work. AI tools can scan thousands of images and lines of code to find visual problems (like a logo being used incorrectly), analyze customer support chats to see if the tone matches the brand guide, and even flag potential brand perception problems by analyzing social media sentiment. This frees up the human team to focus on strategy instead of spending all their time doing manual checks.

Editorial Team

The Editorial Team at App Growth Studio is a group of writers and editors who cover marketing, brand, and growth. They research each story and publish under a shared desk byline — experts in their fields, working as one team.