# Every module in Valenys Core, in one list

> Valenys Core is delivered as one system with fourteen modules: CRM, CMS, email, invoicing and finance, management, sales management, customer support, marketing, marketing automation, reports, commerce, AI and communication, access and security, and settings.

Source: https://valenys.com/platform/modules/
Updated: 2026-09-13

---
_The platform page argues. This one just lists._

These are the modules as they appear in the panel’s own navigation. Not every implementation switches all of them on — you pay for a scope, not for a catalogue — but this is what exists and what can be turned on later without a rewrite.

## The fourteen modules

### CRM

Leads, opportunities, prospects, call-backs, cadences, duplicates, clients, contacts, offers and meetings — with a “Today” screen that puts them in the order they have to happen.

[See the platform](/platform/)

### CMS

Pages and posts, media library, global sections, templates, menus, categories, FAQ, galleries, price tables, popups, forms, comments, newsletter, SEO settings, statistics, redirects and broken links.

[See the platform](/platform/)

### Commerce

Catalogue, variants, stock across warehouses, B2B accounts and group pricing, checkout, payments, couriers, marketplaces and feeds.

[See details](/platform/commerce/)

### Email

Transactional templates, campaign sending in batches with a per-recipient log, and a communication history that stays attached to the company it belongs to.

### Financial

Invoices, receipts, payments, balances, several currencies with a daily rate, units of measure, and VAT as a setting rather than as hard-coded logic.

### Management

Contracts and hosting with expiry alerts, plus a document register with templates, analytics and its own outbound email.

### Sales management

The team’s pipeline, prospects, accounts, forecast and sales reports — the view a sales manager needs and an agent does not.

### Customer support

Tickets with service levels, a client portal, and the handover point where a conversation stops being automated.

### Marketing

A monthly content plan approved before anything is produced, an editorial calendar, capture points, and the leads that arrive from the site.

### Marketing automation

Sequences that run from the same records: when a lead does this, send that — with the plan and the log visible in the panel.

### AI and communication

Claude, Gemini and GPT with a spending cap checked before each call, a chatbot that answers from indexed content, an assistant in the panel and translation at scale.

[See the chatbot](/solutions/ai-chatbot/)

### Reports

Cross-module reporting: what was invoiced, what is in pipeline, what expires, what is selling and what the team did about it.

### Access and security

Roles by capability, two-factor sign-in, scoped API keys, IP rules, an audit log, a maintenance mode and security headers.

### Settings

Sites, languages, company profile, nomenclatures, currencies, backups and the scheduled tasks that keep the recurring work running.

## A list is not a proposal

Nobody switches on fourteen modules in the first month, and nobody should. An implementation starts with the part that hurts — usually sales, commerce or content — and the rest is added against the same data when there is a reason to.

The reason to look at the whole list anyway is the second question, the one that gets asked eighteen months later: **can this thing grow with us, or do we buy a second system?** Everything above runs on the same database, the same permissions and the same audit log.

## Tell us which part hurts

We scope that, and quote it. The rest of the list stays available, not billed.