The problem
SuiteCRM ships with one look. Teams that wanted their own colors and logo on it needed a developer, a build step and theme files that often broke at the next upgrade. In our own SuiteCRM work, the same request came up again and again: make the CRM look like our company, and do not make it fragile.
What we built
- A browser studio that reads the colors in a logo and builds a complete theme: top bar, menus, buttons, list views, record pages and the login screen.
- A live preview on real SuiteCRM screens (list, detail, edit, subpanels, dashboard and login) where any part can be clicked and recolored.
- A contrast check on every text-and-background pair against WCAG AA before download, so a brand color never makes the CRM hard to read.
- A package that installs through Admin, then Module Loader, records the previous settings, and restores the old theme, user preferences and logo on uninstall.
- Version locking, so a package built for one SuiteCRM version refuses to install on another, and an upgrade-safe install on both versions: the custom folder on SuiteCRM 8 and a SuiteP sub-theme through Module Loader on SuiteCRM 7.
- Optional AI refinement that suggests a polished color scheme from the logo for signed-in users.
The result
What used to be a small development project for each client is now a few minutes in a browser. Brandtint supports SuiteCRM 7.10 to 7.15 and SuiteCRM 8.0 to 8.10, covering both the classic views and the new interface, and it is available to any SuiteCRM team at brandtint.app.
What we learned
The hard part was not choosing colors. It was making the result safe: readable for every user, removable without leaving traces, and unbreakable by the wrong version. Those same rules now shape the SuiteCRM customization work we do for clients.