Concepts

Domains

How Solvren categorizes operational changes.

Overview

Domains categorize the functional area affected by a change.

Domains help the platform determine:

• required approvals
• evidence requirements
• operational risk

Each organization may customize domains to reflect their operational structure.


Common Domains

Solvren commonly uses the following domains.


Pricing

Pricing changes affect how products or services are sold.

Examples:

• new pricing tiers
• discount rules
• promotional pricing logic

Pricing changes often require finance or product review.


Billing

Billing changes affect how customers are invoiced and charged.

Examples:

• subscription billing configuration
• invoice generation logic
• billing cycle changes

Billing modifications often require strong safeguards.


Revenue Recognition

Revenue recognition governs how revenue is recorded for accounting purposes.

Examples:

• deferred revenue schedules
• recognition timing adjustments
• accounting rule configuration

Changes in this domain may require finance approval.


Lead Routing

Lead routing changes affect how new leads are assigned to sales teams.

Examples:

• territory assignments
• routing rules
• automation updates

These changes typically involve revenue operations teams.


Reporting

Reporting changes affect dashboards or financial analytics pipelines.

Examples:

• data transformations
• reporting definitions
• financial metrics

Although lower risk than billing changes, reporting updates may affect decision-making.


Why Domains Are Important

Domains allow organizations to enforce governance policies such as:

• domain-specific approvals
• evidence requirements
• risk thresholds

For example:

| Domain | Typical Approvers | |------|------| | Pricing | Finance + Product | | Billing | Engineering + Finance | | CRM | RevOps |

This ensures that the correct stakeholders review each change.

✏️ Edit this page on GitHub
Was this page helpful?
Send feedback