Software landscape

Who touches the business, through which channels, and how fourteen capability groups share one central integration and data hub. Revision 5 Oct 2026 adds seven modules for running the business and names three integration boundaries that are not decided. Every card opens the matching screens.

Modules and screens Open the integration hub

Business goal. All systems connect through one centralized hub so that website, sales, learning delivery, operations, finance and analytics work together, while staying flexible for future expansion.

Customer and staff touchpoints

People who interact with the training business. Select one to highlight the capability groups they use.

Channels

The ways people reach and receive MALYOMAR's courses.

Website and landing pages

Public front door: course information, marketing, sign-up and lead capture.

On-demand learning

Self-paced online courses, anytime, with progress tracking.

Virtual classroom

Live, interactive training delivered online through a video platform.

In-person training

Classroom and on-site training at client or public venues.

Core capability groups

Fourteen groups. Each one reads and writes through the hub, never directly to another group.

Central integration and data hub

APIs
Workflows
Master data
Automation
Single source of truth

A lead captured on the website, a seat sold, a session attended and an invoice paid are all events on the same records.

Connectors · Data flows · API · Audit log

Added in revision 5 Oct 2026: running the business

Seven modules that use the same hub records as the fourteen groups above. They add no second copy of a customer, a batch or an invoice. HR and purchasing were not in the original work breakdown and are scope additions. Demonstrated in the prototype with sample data.

Extensions inside existing groups: tenders, customer rating and loyalty in CRM; company profit and loss, cash, accounting and period close in Finance; the planning and recovery advisor in the AI layer. The full list is in the module register and the change log.

Integration boundaries that are not decided

Three places where the hub meets a system that has not been chosen. The prototype draws the boundary and shows a simulated status on each side. It does not connect to any package and claims no live books, payroll or publishing.

These decisions do not block reversible layout and workflow work. Calculations and policies that depend on them stay visibly provisional. All ten are listed on open decisions.

AI enablement across the landscape

Embedded in every moduleAI reads from the hub and proposes; people approve. How the AI layer works

Lead capture chat

Answers questions, qualifies leads, books a call.

Content drafting

Course outlines, marketing copy and communications.

Recommendation engine

Suggests the next course on a learner's path.

Lead scoring

Ranks leads so sales calls the right ones first.

Support assistant

Drafts answers to common learner questions.

Reporting insights

Summaries and warnings from business data.

Workflow automation

Routine admin tasks and approval routing.

Planning and recovery advisor

Drafts seasonal allocations, scenarios and recovery actions with stated inputs and assumptions. Simulated in the prototype; management approves.

Key benefits

What the owners should expect once the hub is in place.

Unified operationsAll systems connected and aligned; staff stop re-typing between tools.

Better learner journeyOne experience from first visit to certificate across all delivery modes.

Less manual workReminders, certificates, invoices and follow-ups run from rules.

Stronger analyticsSales, learning and finance visible together, in real time.

Faster decisionsTrusted data for confident action: run a batch, cancel it, or fill it.

Future expansionNew courses, tools, markets and business models added without rebuilding.

Suggested high-level stack

Five layers. The names describe the role each layer plays, not a chosen product; product choices are on build, buy or mix.

Front end

Public website and marketing

Course pages, landing pages, forms and SEO. The original landscape drawing placed WordPress here. Whether it is kept, replaced or used through an integration is open decision DEC-09; the prototype shows what the pages and their administration must do either way.

Public website · Website pages

Core hub

CRM, integration and data

Master records for people, companies, courses, batches and money, with APIs and workflows that every other layer uses.

Data flows

Delivery tools

LMS, virtual classroom, on-site operations

Course creation, delivery and operations: content, batches, sessions, attendance, certificates.

Batches

Back office

Finance, support and analytics

Accounting, customer support and reporting, fed by the hub instead of by spreadsheets. Now also planning and targets, risks and actions, purchasing and payables, and people and HR. Where the books and payroll are kept is open (DEC-01, DEC-08).

Finance overview · Targets

AI layer

Across all modules

Embedded assistance that drafts, scores, recommends and summarises, always with a person approving.

AI layer explained

Central hub principles

Principle	What it means here	Where you can see it
Single source of truth	Each record has one owning module. A learner's name is edited in Learners and nowhere else; other modules read it.	Data model: owners
API-first	Every capability is reachable through a documented API, so a bought tool and a built screen use the same door.	API and keys, Webhooks
Modular	A component can be replaced or upgraded without touching the others: swap the video platform, keep attendance.	Connectors
Role-based access	People see what their job needs. Sales does not see payouts; instructors see only their own rosters. A person can hold several roles, each with a record scope; a partner user sees only their own organisation. In the prototype, hiding is static and is not proof of production authorization.	Roles and access, Roles and permissions, Responsibility profiles
One approval policy	Every form, inbox item and permission text reads approvers and limits from one central matrix. The matrix is provisional until management approves it; new approval types have no monetary default.	Approval policy, DEC-03
Numbers say what they are	Actuals, approved targets, forecasts, commitments and estimates are labelled and never added together. Recognised revenue, bookings, cash collections, receivables and seats stay separate measures, and a summary that differs from its detail shows a bridge.	Finance overview, Target and recovery dashboard
Auditable data flows	Who changed what, and which system sent which event, is recorded for compliance and for ASME reporting.	Audit log
Expandability	New products, regions, currencies and business models are data and configuration, not a rebuild.	Roadmap