Brilliance CRM follows a structured update strategy designed to deliver new features, security enhancements, and performance improvements on a predictable schedule—while giving every business the flexibility they need. Regular releases occur every even-numbered month, and a dedicated preview environment lets customers explore upcoming changes in advance. Organizations can stay on the standard cadence, slow their updates to suit internal processes, or request immediate or weekly deployments for must-have features. Critical security patches are issued outside the regular cycle to protect data without delay. This balanced approach combines the reliability of a fixed schedule with the agility to respond quickly to evolving business and security needs, ensuring your CRM stays both cutting-edge and dependable.
Regular Release Cadence
Brilliance CRM follows a predictable, even-month release rhythm so you always know when to expect the next update. By deploying during the first full week of February, April, June, August, October, and December, our team can plan, test, and communicate changes well in advance. This consistency minimizes surprises and helps your staff schedule training or testing around a known timeline.
- Frequency: Updates are released every even-numbered month (February, April, June, August, October, December).
- Deployment Window: Rollouts begin the first full week of the scheduled month unless otherwise communicated.
Test Site (Preview Environment)
The preview environment acts as a “sandbox” for your team. It always runs the latest release candidate so you can explore new features, confirm integrations, and train staff before updates reach your live system. This proactive testing reduces downtime and ensures a smooth transition to each new version.
- Always-On Preview: A dedicated test site running the latest release candidate is available to all customers.
- Access: Simply contact our support team for credentials. You can explore upcoming features, interface changes, and workflow updates before they reach production.
Flexible Options for Businesses
Every organization operates differently, so Brilliance CRM gives you full control over your update pace. If your team prefers a slower rollout—such as quarterly or semi-annual updates—you can set a custom cadence. Conversely, if a new feature is essential, you can request a manual or weekly update to adopt it immediately.
- Custom Cadence: If you prefer fewer updates (quarterly, semi-annual, etc.), you can request a schedule that fits your operations.
- Manual or Weekly Updates: If a new feature is critical to your workflow, you can request a manual deployment or weekly update outside the standard cycle.
Critical & Security Patches
Protecting your data is our top priority. In the event of a zero-day vulnerability or critical defect, we bypass the regular schedule and deploy an immediate fix. This rapid response helps safeguard sensitive information and keeps your system compliant with the latest security standards.
- Zero-Day Response: Any urgent security vulnerability or critical defect will be patched and deployed immediately, regardless of the regular schedule, to keep your data safe.
Why Stay Current
Keeping your system updated ensures you benefit from ongoing security hardening, performance enhancements, and the latest features. Regular updates reduce the need for large, disruptive upgrades and maintain compatibility with browsers, APIs, and third-party integrations, protecting your investment in the platform.
- Ongoing security hardening and performance tuning.
- Early access to new capabilities and integrations.
- Continued compatibility with browsers, APIs, and third-party services.
- Reduced risk of large, disruptive upgrades.
Additional Best Practices
To maximize reliability, we recommend staging and acceptance testing in the preview environment before each even-month deployment. Release notes are distributed at least a week in advance so your team can plan, verify, and train as needed. These practices help you take advantage of new features while maintaining stable operations.
- Staging Approval: For mission-critical setups, we recommend running automated or manual acceptance tests in the preview environment before each even-month deployment.
- Change Notifications: Detailed release notes will be provided at least one week prior to each scheduled update.
Knowledge Base Article Categories
Choose from the Knowledge Base category to view the available articles.