Brilliance One Accounts

Every relationship. One connected business record.

Manage customers, leads, organizations, contacts, vendors, suppliers, partners, and the people your business works with from a shared relationship foundation.

Brilliance One Accounts connects communication, sales activity, tasks, documents, financial history, projects, scheduling, marketing, automation, service, and operational context to the relationships behind the work.

Customers • Leads • Organizations • Vendors • Partners
Brilliance One account contact company and relationship management

Relationship Foundation

Know who you work with. Know the business around them.

Accounts provides a shared foundation for organizations and people so customer-facing and operational workflows can work from common relationship context.

Organizations

Companies & Business Entities

Maintain organizations, companies, vendors, suppliers, partners, customers, and other business entities independently from the people associated with them.

People

Contacts & Individual Relationships

Maintain the people who work for, represent, buy from, sell to, support, influence, or otherwise participate in each business relationship.

Context

The Business History Around the Record

Communications, tasks, financial activity, documents, projects, scheduling, marketing, notes, opportunities, and supported operational workflows can stay connected to the underlying relationship.

Shared Business Context

Stop rebuilding the same relationship everywhere.

In disconnected software stacks, the same customer may exist separately in CRM, accounting, project management, marketing, support, scheduling, invoicing, and other systems. Brilliance One is designed so multiple business workflows can reference a common relationship foundation.

  • Organization information
  • Contacts and people
  • Addresses
  • Email addresses
  • Phone numbers
  • Relationship classifications
  • Custom attributes
  • Communication history
  • Activity history
  • Connected module context

One Relationship Foundation

Customer data should become more valuable as the platform expands.

When another Brilliance One module is added, the account record can gain additional operational context instead of forcing the organization to recreate the same business or person inside another isolated application.

The relationship becomes richer as more of the business operates on the same connected platform.

Beyond Contact Management

CRM tells you who they are. Operations tell you everything happening around them.

Contact and company records are essential CRM capabilities. Brilliance One extends that relationship model into broader business operations so the record can continue to gain context after the sale.

Relationship

Who Are They?

Maintain the organization, people, contact details, addresses, classifications, notes, preferences, tags, and business-specific relationship information.

Engagement

What Has Happened?

Connect communication, activities, tasks, opportunities, campaigns, appointments, documents, and other interaction history to the relationship.

Operations

What Is the Business Doing for Them?

Extend the relationship into projects, financial activity, products, inventory, scheduling, documents, services, and other supported business workflows.

Account Capabilities

Organize the relationship. Connect the work around it.

Organizations

Company Records

Maintain companies, agencies, nonprofits, partners, vendors, suppliers, customers, departments, and other organizational entities.

Contacts

People & Roles

Connect multiple people to organizations while preserving names, roles, titles, communication details, preferences, and individual relationship history.

Leads

Prospect Relationships

Track potential customers and the activities, communication, qualification, and business context leading toward an opportunity or future relationship.

Classification

Relationship Types

Distinguish customers, prospects, vendors, suppliers, partners, and other relationship categories relevant to the organization.

Custom Data

Business-Specific Attributes

Use custom fields, tags, classifications, and operational metadata to capture information unique to your organization or industry.

History

Relationship Timeline

Preserve communication, activity, tasks, notes, documents, financial records, projects, and other supported history around the account.

Segmentation

Filters & Organization

Organize account lists according to relationship type, lifecycle, industry, priority, tags, services, attributes, or other business criteria.

Communications

Connected Conversations

Associate supported email, SMS, MMS, notes, notifications, and communication history with the people and organizations behind the conversation.

Security

Controlled Visibility

Use authentication, roles, permissions, security groups, module access, and administrative controls to help determine which information users should access.

Relationship Types

Your business works with more than customers.

Accounts can support the broader network of organizations and people involved in running the business.

Leads & Prospects Track potential customers and the activity leading toward future business.
Customers Maintain the customer relationship, communication, history, and connected operational activity.
Vendors Manage organizations providing products, services, expertise, or other resources to the business.
Suppliers Maintain supplier relationships alongside purchasing, product, inventory, or operational context where applicable.
Partners Track referral, strategic, implementation, technology, marketing, or other partnership relationships.
Other Organizations Represent agencies, associations, nonprofits, departments, households, institutions, or other entities where appropriate.

People & Organizations

Understand the organization. Understand the people inside it.

Business relationships often involve multiple people with different responsibilities. Accounts can preserve the organization while connected contacts provide the individual context needed for communication and operations.

  • Primary contacts
  • Multiple contacts per organization
  • Titles and roles
  • Email addresses
  • Phone numbers
  • Addresses
  • Relationship notes
  • Communication preferences
  • Operational relationships
  • Contact history

Relationship Structure

A company is not a contact. A contact is not the company.

Separating organizations from the people associated with them helps preserve cleaner business relationships when employees change, several contacts participate, or different people interact with different parts of your organization.

The organization remains the business relationship while contacts can change around it.

Relationship Lifecycle

Relationships change. The history should stay connected.

A relationship can evolve from prospect to customer, customer to repeat customer, vendor to partner, or into other organization-defined roles without losing the business history accumulated along the way.

1

Create the Relationship

Add the organization or person, classify the relationship, and capture the information relevant to the business.

2

Build the History

Connect communication, notes, activities, tasks, opportunities, documents, financial records, projects, scheduling, and other supported workflows.

3

Grow the Relationship

Use accumulated context to support sales, service, retention, marketing, operations, reporting, and future opportunities.

Connected Communication

Keep the conversation with the relationship.

Communication is more useful when users can understand who was involved, what happened previously, why the conversation matters, and which business process it supports.

Email

Email History

Connect supported email activity with the account or contact involved in the conversation.

Messaging

SMS & MMS

Keep supported text and multimedia messaging activity connected with customer and contact history.

Context

Notes

Maintain internal context that helps authorized users understand the relationship beyond formal communication.

Follow-Up

Tasks

Connect follow-up activity and internal work with the account or relationship requiring attention.

Workflow

Automation

Use relationship context inside supported communication, tagging, notification, and workflow automation.

Timeline

Activity History

Preserve broader activity so authorized users can understand what has happened across the life of the relationship.

CRM & Sales Context

Know the relationship before asking for the business.

Account context can support sales activity by giving teams a broader view of who the prospect or customer is, which people are involved, what has happened previously, and what other parts of the business already know.

  • Lead and prospect information
  • Organization details
  • Contact roles
  • Opportunity context
  • Communication history
  • Notes and activities
  • Tasks and follow-up
  • Customer history
  • Products or services
  • Existing operational context

Relationship Selling

A pipeline should not erase the relationship behind the deal.

An opportunity represents potential business. The account provides the broader relationship context around that opportunity.

Keeping the two connected helps teams understand the customer beyond a pipeline stage or projected value.

Module-Aware Accounts

The account becomes richer as the platform expands.

When additional Brilliance One modules are enabled, related information can become part of the broader relationship context instead of remaining inside an unrelated application.

Accounting

Quotes, Invoices & Payments

Connect appropriate customer financial activity and history with the account responsible for it.

Projects

Work & Delivery

Connect supported projects, tasks, related work, deadlines, and operational activity with the customer or organization behind them.

Scheduling

Appointments & Events

Associate scheduled activity with the customer, contact, organization, resource, or broader business workflow where configured.

Marketing

Campaign & Engagement Context

Use relationship types, classifications, tags, and account data in supported marketing and customer-engagement workflows.

Documents

Files & Business Records

Associate appropriate files and documents with the accounts, contacts, projects, financial records, or other business relationships they support.

Products

Product & Commerce Context

Connect supported products, services, purchases, orders, inventory-related activity, and commerce workflows with customer relationships where applicable.

Communications

Relationship Conversations

Keep email, SMS, messaging, templates, notifications, and communication history connected with the appropriate account and people.

Automation

Relationship Workflows

Use account information in supported automated communication, notifications, tagging, follow-up, and operational workflows.

Service

Support & Operational History

Connect supported service, request, support, or operational activity with the broader customer relationship.

Customer + Operations

The customer record should not stop when the opportunity closes.

Closing a sale often begins a much larger operational relationship. Brilliance One Accounts is designed to remain relevant as the customer moves from prospect into delivery, billing, support, scheduling, projects, documents, repeat sales, and ongoing service.

  • Lead
  • Opportunity
  • Customer
  • Quote
  • Invoice
  • Project
  • Appointment
  • Document
  • Communication
  • Ongoing relationship history

Full Relationship Context

CRM begins the relationship. Operations continue it.

The goal is not simply to know that someone became a customer.

The goal is to preserve the context of what the business sold, delivered, scheduled, billed, communicated, documented, supported, and learned throughout the relationship.

Business-Specific Data

Your relationships do not all look the same.

Custom fields, classifications, tags, and business-specific attributes can help Accounts reflect the way your organization actually manages relationships instead of forcing every business into one rigid data model.

  • Custom fields
  • Account classifications
  • Relationship types
  • Tags
  • Business-specific attributes
  • Industry information
  • Priority
  • Service categories
  • Opportunity context
  • Operational metadata

Flexible Structure

Model the relationship your business actually has.

Different organizations may need different information about customers, members, donors, vendors, residents, partners, clients, suppliers, or other relationships.

Flexible account data allows the relationship model to adapt without abandoning the shared platform foundation.

Organization & Segmentation

Find the relationships that matter right now.

Tags, classifications, filters, attributes, and relationship information help teams organize large account lists and identify records relevant to a specific business objective.

Relationship Type

Separate customers, leads, vendors, suppliers, partners, and other relationship categories.

Industry

Organize accounts according to industry, market, business type, or other relevant classifications.

Priority

Identify strategic, urgent, high-value, or otherwise prioritized relationships.

Products & Services

Group relationships according to the products, services, programs, or operational areas associated with them.

Lifecycle

Organize relationships according to prospect, customer, inactive, vendor, partner, or other configured lifecycle states.

Custom Criteria

Use business-specific attributes and classifications when standard categories are not enough.

Relationship Security

One account can contain many levels of sensitive information.

Account records can accumulate personal, financial, contractual, communication, operational, and other sensitive business information. Brilliance One uses the broader platform security model to help organizations control appropriate access.

  • User authentication
  • Role-based permissions
  • Security groups
  • Module-based access
  • Administrative controls
  • Customer data separation
  • Audit-oriented activity
  • Operational history
  • Privacy-related controls
  • Organization-defined access policies

Appropriate Visibility

Show users what they need to do their job.

A salesperson, accountant, project manager, administrator, and customer service representative may all work with the same account while requiring different information.

Permissions and module access help keep the experience relevant to each user's responsibility rather than simply exposing every available record to everyone.

Account Architecture

Flexible enough for the business. Structured enough to remain useful.

Connected

Module-Aware Relationships

Accounting, communications, automation, documents, projects, scheduling, products, marketing, service, and other supported workflows can connect with the relationship record.

Flexible

Custom Business Attributes

Use custom fields, classifications, tags, and relationship data to model information specific to the organization or industry.

Organized

Tagging & Segmentation

Group and filter accounts by relationship type, lifecycle, priority, industry, service category, tags, or custom business criteria.

Scalable

Growing Relationship History

Support expanding account lists, additional users, increasing activity history, new relationship types, and more connected workflows as the organization grows.

Relationship Platform Strategy

Modern CRM already centralizes relationships. Brilliance extends the record into operations.

Modern CRM platforms provide strong contact, company, communication, activity, opportunity, segmentation, and automation capabilities. Brilliance One builds on that foundation by allowing the same relationships to participate in a broader business operating system.

CRM Context

Contacts, Companies & Opportunities

Centralize people, organizations, communication, sales activity, notes, tasks, opportunities, and other customer-facing context.

Operational Context

Finance, Projects & Delivery

Extend the relationship into invoices, payments, projects, scheduling, documents, products, inventory, vendors, service, and other operational workflows.

Shared Context

One Relationship Across Both

Keep customer-facing activity and internal operations connected around the same broader relationship foundation where supported.

Included in Brilliance One Core

Accounts are part of the platform foundation.

Brilliance One Core provides the shared users, security, settings, communications, automation, permissions, customer relationships, and platform infrastructure that allow Accounts to connect with broader business workflows.

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 Accounts

Locations

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 Addresses

Email, 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 Communications

Workflow 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 Automations

Identity & Access

Users

Manage identities, roles, permissions, security groups, profiles, account relationships, module access, authentication, and operational responsibilities across Brilliance One.

Explore Users

Platform Protection

Security

Protect business information with authentication, authorization, roles, permissions, security groups, encryption, session controls, logging, monitoring, and administrative safeguards.

Explore Security

Platform Configuration

Settings

Configure organization defaults, branding, permissions, communication providers, payment services, AI preferences, integrations, module behavior, and shared platform settings.

Explore Settings

Data Operations

Tools

Import, export, map, validate, review, migrate, clean, and maintain supported business information with administrative workflows designed for controlled data operations.

Explore Tools

Core Platform Pricing

Accounts begin with Brilliance One Core.

Accounts is part of the Brilliance One Core foundation rather than a separate per-user CRM license. Add additional business modules as your organization needs broader operational capability.

  • Accounts included with Brilliance One Core
  • No per-user platform pricing
  • CRM and relationship foundation
  • Shared communications and automation
  • Expandable business modules
  • Founders 400 alternative available

Build Your Platform

Start with Accounts. Add the operations around them.

Use the Brilliance One pricing estimator to start with Core, select additional modules, estimate applicable usage, and build the configuration that fits your organization.

Brilliance One Accounts

Know the relationship. See the business around it.

Centralize customers, leads, organizations, contacts, vendors, suppliers, partners, communication, financial activity, documents, projects, scheduling, tasks, and operational history around the relationships that drive your business.

Brilliance One • Accounts + CRM • Connected Business Relationships