Platform Release Notes: Module & Industry Cloud Expansion

This is an ongoing release covering the continued build-out of SAVHN's Module Marketplace and the Industry Cloud program, which now spans 22 fully built industry configurations on top of the core module set.

Module Marketplace expansion

The Module Marketplace has grown to cover the full breadth of a business operating system, organized across these categories:

Category	Modules
Core Business	CRM, HRMS, Payroll, Finance, Projects, Tickets
Collaboration	Timeline, Meetings, Chat, Documents
Customer-Facing	Client Portal, Reports
People & Growth	Learning, Skills
Automation & AI	Automations, AI Studio, AI Assistant, Manager Copilot
Intelligence	Business Brain, Revenue Intelligence, Journey Orchestrator, Workforce Intelligence

Each module in the Marketplace now shows its dependency relationships explicitly (see Module Marketplace: Enabling & Configuring Modules), so admins can plan a rollout sequence — for example, enabling HRMS before Payroll, or CRM before Revenue Intelligence — without trial and error.

Notable additions in this expansion

• AI Studio, allowing organizations to configure custom AI agents and workflows on top of their own data, rather than relying solely on the fixed AI Assistant behavior.
• Business Brain, a cross-module question-answering layer that respects each user's existing RBAC scope (see Platform Architecture Overview for how this is architecturally possible without bypassing permissions).
• Journey Orchestrator, extending CRM with configurable multi-step customer/lead journeys.
• Workforce Intelligence, adding analytics on top of HRMS data for organizations that have matured past basic HR record-keeping into workforce planning.

Industry Clouds: 22 built and counting

An Industry Cloud is a curated configuration layer on top of the core modules — pre-set module bundles, default roles, custom fields, and workflow templates tailored to a specific vertical (see Platform Architecture Overview for how this is implemented without forking the codebase per industry).

The following 22 Industry Clouds are built and available:

#	Industry Cloud
1	Construction
2	Healthcare
3	Digital Agency
4	Advertising & Media
5	Real Estate
6	Structural Consultants
7	ISO Consultants
8	Auditing & Accounting
9	Legal Services
10	Architecture
11	Interior Design
12	PMC (Project Management Consultancy)
13	Civil Engineering
14	Pharmacy
15	Laboratory
16	NGO
17	Travel & Tourism
18	Import & Export
19	Manufacturing
20	IT Services
21	Professional Services
22	Education

What an Industry Cloud actually configures

Enabling an Industry Cloud during organization setup (or later, from the Marketplace) applies a bundle of changes rather than a single toggle:

• Module enablement — the relevant core modules for that vertical are enabled together (e.g. Education enables Enrollments-related workflows feeding Fee Invoices; Legal Services emphasizes Documents, Tickets-as-matters, and Client Portal).
• Default roles — a starting role set matched to how that industry typically organizes staff (e.g. Auditing & Accounting ships with an "Engagement Manager" role template).
• Custom fields and statuses — industry-appropriate fields added to core module records (e.g. Healthcare's Projects records carry compliance-oriented custom fields not present by default).
• Workflow templates — pre-built Automations relevant to the vertical, which an admin can adopt as-is or customize.

Choosing an Industry Cloud at org creation is a starting point, not a lock-in — every underlying module and role remains fully configurable afterward exactly as it would be for an organization that started from a blank configuration.

Industry Cloud examples in more detail

A few examples illustrate how differently the same underlying modules get configured across verticals:

• Construction bundles Projects (configured with site/phase tracking fields), Finance (progress-billing-oriented invoice templates), and Tickets (used for site issue reporting), with a Site Supervisor role template scoped to a single site's records.
• Legal Services leans on Documents (matter-centric folder structures), Tickets (used as legal matters with SLA-like deadline tracking), and Client Portal (for client-facing matter status), with role templates separating Partner, Associate, and Paralegal access levels.
• Education bundles Enrollments-oriented workflows feeding Fee Invoices (see Module Marketplace: Enabling & Configuring Modules for this specific dependency), HRMS configured for academic staff structures, and Reports templates oriented around attendance and academic performance rather than generic business KPIs.
• NGO emphasizes Projects (configured around programs and grants rather than commercial engagements), Finance (fund-restricted accounting fields), and Reports templates aligned to donor and grant reporting rather than revenue reporting.

These examples aren't exhaustive of what each Industry Cloud configures, but they illustrate the general pattern: the same core modules, re-shaped by default fields, roles, and templates to match how a given vertical actually operates.

Adoption guidance by organization size

• Small organizations typically benefit most from adopting an Industry Cloud as-is initially, since the default role and workflow templates are usually a reasonable fit and hand-configuring from scratch offers little advantage at small scale.
• Larger or multi-division organizations more often use an Industry Cloud as a starting template for one division while configuring others independently, since a single Industry Cloud template rarely fits every division's workflow identically at scale.

Ongoing nature of this release

Both the Module Marketplace and the Industry Cloud program continue to expand:

• New modules are added to the Marketplace as they reach general availability, each with dependency declarations from day one so existing organizations can adopt them predictably.
• Additional Industry Clouds are evaluated based on customer demand and typically start as a configuration bundle on existing modules before any industry-specific resource is added to the API surface.

How Industry Clouds relate to the API surface

Industry Cloud-specific API access (see the Industry Clouds row in the API Reference domain table) is additive on top of the core domains, not a replacement for them:

• The majority of an Industry Cloud's data still lives under core domains (/api/projects, /api/finance, /api/hrms, and so on) — an integration built against a Construction organization's Projects data uses the same /api/projects endpoints as an integration built against a Digital Agency organization.
• Industry-specific resources are added only where a vertical's workflow genuinely doesn't map onto an existing core resource — for example, a compliance-tracking resource specific to Healthcare, or a matter-type taxonomy specific to Legal Services.
• This means an integration built generically against the core API domains will largely keep working regardless of which Industry Cloud an organization has adopted, since the underlying resource shapes are shared; only integrations that specifically need an industry-specific resource need to branch their logic per industry.

What to check if you're an existing customer

• If your organization predates a given Industry Cloud's availability, you were not automatically migrated onto it — Industry Cloud adoption is opt-in and can be applied later from the Marketplace if it matches your vertical.
• Review the Marketplace periodically for newly available modules; module availability is not announced individually to every organization admin, so periodic review is the reliable way to discover new capability.
• If you operate in a vertical not yet covered by a dedicated Industry Cloud, the core module set (CRM, HRMS, Payroll, Finance, Projects, Tickets, and the rest) remains fully usable without one — Industry Clouds are an accelerator, not a prerequisite for using any given module.

Related pages

• Module Marketplace: Enabling & Configuring Modules
• Organization Setup & Onboarding
• Platform Architecture Overview