Relationships
CRM Foundation
Maintain customers, prospects, organizations, contacts, vendors, partners, communication points, classifications, activity, and broader relationship context.
Brilliance One Core
One foundation. Build the business on top of it.
Start with the shared CRM, communications, automation, users, security, permissions, administration, and business data foundation behind the Brilliance One Business Operating System.
Core gives customer-facing and operational modules a common place to manage relationships, communication, access, workflow, configuration, security, and shared business context before specialized CRM, ERP, CMS, or industry capabilities are added.
CRM • Communications • Automations • Security • No Per-User Pricing
The Operating Foundation
More than CRM. The shared layer beneath the business.
Brilliance One Core provides the capabilities that should not need to be recreated every time your organization adds another business function.
Workflows
Communication & Automation
Connect email, SMS, messaging, templates, communication history, and repeatable automation with the business records responsible for the activity.
Platform
Users, Security & Administration
Manage users, permissions, security groups, organization settings, authentication, administrative tools, and shared services from one platform foundation.
Why Core Exists
Every new capability should not require another foundation.
Businesses often accumulate applications that each recreate users, customer records, permissions, settings, communication history, authentication, and integrations. Core centralizes those common responsibilities so additional Brilliance One modules can build on them.
- Shared customer and account context
- Shared users and access controls
- Shared communications
- Shared automation
- Shared security foundation
- Shared administration
- Shared configuration
- Shared API architecture
- Shared operational context
- Modular expansion
One Foundation
Add capability without rebuilding the system underneath it.
Adding Accounting should not require another customer database. Adding Scheduling should not require another user directory. Adding Projects should not require another permission model.
Specialized modules can extend the Brilliance One platform while continuing to use shared Core services wherever their workflows intersect.
Brilliance One Core
One shared foundation. Used throughout the platform.
Core provides the relationship, communication, automation, identity, security, configuration, and administrative capabilities that support the broader Brilliance One Business Operating System.
CRM & Relationships
Accounts
Manage customers, prospects, leads, organizations, contacts, vendors, suppliers, partners, and relationship history through one connected business record.
Explore AccountsLocations
Addresses
Maintain billing, shipping, service, customer, employee, vendor, job-site, and operational locations as reusable records connected to the business activity that depends on them.
Explore AddressesEmail, SMS & Messaging
Communications
Connect email, SMS, MMS, campaigns, templates, lists, replies, delivery activity, and communication history with the customers and business records behind every conversation.
Explore CommunicationsWorkflow Automation
Automations
Automate supported email, SMS, tagging, notifications, delays, follow-up, and repeatable processes so people can focus on decisions while software handles routine work.
Explore AutomationsIdentity & Access
Users
Manage identities, roles, permissions, security groups, profiles, account relationships, module access, authentication, and operational responsibilities across Brilliance One.
Explore UsersPlatform Protection
Security
Protect business information with authentication, authorization, roles, permissions, security groups, encryption, session controls, logging, monitoring, and administrative safeguards.
Explore SecurityPlatform Configuration
Settings
Configure organization defaults, branding, permissions, communication providers, payment services, AI preferences, integrations, module behavior, and shared platform settings.
Explore SettingsData Operations
Tools
Import, export, map, validate, review, migrate, clean, and maintain supported business information with administrative workflows designed for controlled data operations.
Explore ToolsShared Business Data
Enter the relationship once. Add context as the business grows.
Core provides relationship and administrative context that specialized modules can reuse instead of forcing every department to maintain isolated copies of the same underlying information.
- Accounts and organizations
- Contacts and people
- Addresses and communication points
- Users and access
- Tags and classifications
- Communication history
- Automation context
- Shared settings
- Security and permission context
- Connected operational references
Connected Architecture
The record becomes more useful as the platform expands.
A customer may begin with only contact information and communication history.
As the organization adds Accounting, Projects, Scheduling, CMS, Marketing, POS, HR, or other modules, that same relationship can gain financial, operational, digital, and workflow context without starting over.
CRM & Relationships
Every business process starts with knowing who it belongs to.
Core provides a shared relationship layer for customers, leads, organizations, contacts, vendors, partners, and the business activity connected with them.
Customers
Maintain customer records and the communication, financial, project, scheduling, document, and operational context that can accumulate around the relationship.
Leads
Track prospective relationships and connect follow-up with communication and automation workflows.
Organizations
Represent companies, agencies, nonprofits, vendors, partners, suppliers, and other organizational relationships independently from their people.
Contacts
Associate people, roles, phone numbers, email addresses, and other information with the organizations and relationships they represent.
Activity
Keep supported communication and operational activity connected with the relationship responsible for it.
Shared Context
Allow connected modules to build on the same relationship information rather than recreating another independent customer record.
Communications
Send the message. Keep the relationship context.
Core communication capabilities connect supported email and messaging activity with the customers, contacts, users, campaigns, and workflows behind the conversation.
- SMS
- MMS where supported
- Templates
- Lists and audiences
- Communication history
- Automated messaging
- Opt-out and suppression context
- Provider-supported delivery activity
- Replies where supported
Shared Communication Layer
Messaging should not become another disconnected customer database.
Email and text activity are more useful when they remain connected to the customer, account, campaign, appointment, invoice, project, or workflow responsible for the conversation.
Automations
Automate the repetition. Keep the process understandable.
Core automation capabilities support repeatable communication and operational workflows using clear triggers, ordered actions, delays, notifications, tagging, and defined stopping points.
Trigger
Begin a supported workflow from configured business activity, a record event, a form, a module event, or manual enrollment.
Execute
Run supported email, SMS, delay, tagging, notification, and other configured workflow actions in sequence.
Track
Maintain available execution history so teams can understand what ran and investigate the workflow when necessary.
Users & Access
Give people the access their responsibilities require.
Manage users, roles, permissions, security groups, module access, and administrative responsibility from the same shared platform foundation.
- User accounts
- Roles
- Permissions
- Security groups
- Module access
- Administrative responsibilities
- Authentication controls
- User-specific settings
No Per-User Pricing
Access decisions should be based on responsibility. Not another seat charge.
Brilliance One is priced around the platform and business capabilities rather than charging another recurring platform subscription every time another authorized employee needs a user account.
Security and permissions still determine which information and functionality each person should be allowed to use.
Security Foundation
Security belongs below every module.
Core provides shared identity, authentication, authorization, permissions, data-separation architecture, logging, and security controls so individual modules do not need to invent an independent security foundation.
Authentication
Identity Protection
Centralize supported login, authentication, account protection, session, multi-factor, lockout, and related security workflows.
Authorization
Role & Permission Controls
Use roles, permissions, security groups, and module access to help determine which capabilities and information authorized users can access.
Data Separation
Customer-Isolated Data Architecture
Brilliance One can use customer-specific database environments to provide database-level separation while application security and access controls govern how authorized users interact with the data.
Transport
Secure Communication
Use modern secure transport and application-security practices to protect data moving between users, applications, APIs, and platform services.
Visibility
Logging & History
Maintain supported security, application, automation, and operational activity that helps authorized teams understand important system actions.
Governance
Security-Conscious Architecture
Use centralized platform controls as part of an organization's broader security, privacy, compliance, access, and operational governance practices.
Data Architecture
Your business data does not have to share one giant customer database.
Brilliance One can use a customer-specific database architecture so tenant information is separated at the database layer rather than relying exclusively on a shared database with tenant identifiers separating customer records.
- Customer-specific data environment
- Database-level tenant separation
- Application-level authentication
- Authorization controls
- Permission-aware access
- Central platform administration
- Connected module architecture
- Security-focused deployment
Customer Isolation
Shared software does not require shared customer tables.
Brilliance One's architecture can provide a dedicated database for an individual customer while still using the shared application platform and common product capabilities.
Database separation is one part of the overall security architecture and works alongside authentication, authorization, permissions, transport protection, application controls, and operational governance.
Administration
Configure one platform. Not another administration console for every function.
Core provides shared administrative capabilities that support the broader Brilliance One environment and the modules operating within it.
Settings
Organization Configuration
Manage organization-wide preferences, supported branding, defaults, platform behavior, and connected configuration from the shared administrative layer.
Users
Access Administration
Manage users, permissions, security groups, responsibilities, module access, and related user configuration.
Tools
Administrative Utilities
Use supported imports, exports, validation, maintenance, and other administrative utilities as part of normal platform operations.
Security
Platform Controls
Manage appropriate authentication, permissions, access settings, security configuration, and administrative visibility from the shared system layer.
Services
Shared Platform Configuration
Configure supported platform-level services that can be reused by multiple modules instead of independently configuring the same service for every business function.
Integrations
Connected Systems
Manage supported integrations and external-service connections that extend Brilliance One without fragmenting the core business context.
API-First Platform
Business capability should not be trapped behind one screen.
Brilliance One's API-first direction allows supported business functionality to be used by the primary application, websites, portals, integrations, partner systems, and custom experiences.
- Application APIs
- Website integration
- Portal experiences
- External-system integration
- Partner workflows
- Industry-specific extensions
- Secure authentication and authorization
- Custom business experiences
Extensible by Design
Integrate when replacement does not make sense.
A business operating system does not need to replace every specialized application in existence.
API-first architecture gives Brilliance One room to connect with external systems when integration provides a better operational result than replacement.
Business Operating System
CRM is the beginning. Operations continue the relationship.
Core establishes the customer and platform foundation. Additional modules extend that context into the work required to sell, schedule, deliver, bill, support, manage, and grow the relationship.
Know the Relationship
Core manages the customer, prospect, organization, contact, communication, access, and shared platform context.
Add the Capability
Activate Accounting, Marketing, CMS, Projects, Scheduling, HR, POS, Insights, Firearms, Technology, or other business modules when required.
Connect the Operation
Let supported modules use the common relationships, users, permissions, communications, automation, APIs, and configuration beneath them.
Modular Expansion
Start with the foundation. Add capability when the business needs it.
Core is designed to remain useful whether an organization begins primarily with CRM and communications or eventually expands Brilliance One across multiple operational functions.
Accounting
Financial Operations
Add quotes, invoices, payments, expenses, banking, vendors, ledger activity, and connected financial workflows.
CMS
Websites & Digital Experiences
Add pages, forms, blogs, media, SEO controls, portals, and digital experiences connected to the business platform.
Marketing
Customer Acquisition
Extend relationship and communication data into broader marketing, campaign, audience, and engagement workflows.
Projects
Work Management
Add project, task, assignment, customer-work, deadline, and operational delivery context.
Scheduling
Appointments & Resources
Add appointments, events, customer scheduling, people, resources, capacity, and related workflows as supported.
Specialized Modules
Industry & Operational Expansion
Extend Core into HR, POS, Insights, Technology, Firearms, Courses, Drug Testing, and other specialized business requirements.
Platform Strategy
Customer platforms connect the customer journey. Brilliance connects it to operations.
Modern customer platforms increasingly centralize CRM data, communications, automation, marketing, sales, service, scheduling, and related customer-facing capabilities. Brilliance One builds on the same connected-platform idea while extending the shared foundation into broader ERP, CMS, industry, and internal operating workflows.
Customer
CRM & Relationships
Maintain customers, leads, organizations, contacts, communication, activities, and relationship context.
Engagement
Communication & Automation
Coordinate supported email, SMS, templates, campaigns, follow-up, notifications, and repeatable workflows.
Operations
ERP & Business Workflows
Extend the same foundation into financial, project, scheduling, workforce, product, content, document, commerce, and specialized operational capabilities.
Foundational Standards
Designed for control, separation, connectivity, and growth.
Core establishes the common technical and operational foundation used by Brilliance One while organizations remain responsible for their own configuration, access policies, governance, data practices, and applicable compliance obligations.
Data
Tenant Separation
Customer-specific database deployments can provide database-level separation while application security and access controls govern use of the information.
Users
Grow Without Seat Pricing
Expand the number of authorized platform users without introducing traditional per-user platform subscription charges.
Security
Central Security Controls
Apply supported authentication, authorization, logging, permission, and security controls from the shared platform foundation.
Communication
Connected Outreach
Keep supported email and messaging connected to customer records, workflows, users, and automation.
Architecture
API-First Direction
Build application and integration capabilities around APIs so business services can support more than one user interface.
Growth
Modular Expansion
Add specialized capability while maintaining the shared platform foundation already in place.
Core Pricing
Start with Core. Expand when the business needs more.
Every standard Brilliance One configuration begins with Core. Add specialized modules and usage-based services according to the capabilities your organization needs.
Required Foundation
$147 / month
Brilliance One Core provides the required shared platform foundation for standard modular pricing.
- CRM and relationship foundation
- Communications
- Automations
- Users and permissions
- Security foundation
- Settings and administration
- No per-user platform pricing
- Expandable module architecture
Build Your Configuration
Core is the starting point. You decide what comes next.
Use the Brilliance One pricing estimator to start with Core, add the modules your organization needs, estimate applicable usage, and compare standard modular pricing with the Founders 400 option.
Brilliance One Core
Start with one foundation. Build the operating system from there.
Connect customer relationships, communications, automation, users, permissions, security, settings, APIs, administration, and shared business data before extending Brilliance One into the specialized CRM, ERP, CMS, and industry capabilities your organization needs.
Brilliance One • Core • CRM + ERP + CMS Foundation • No Per-User Pricing