Modular platform · requirements-led discovery

A modular platform that can grow into the business solution you need.

Start by describing where work slows down, duplicates, or disappears between teams. Build a private brief in your browser with maturity and assumptions clearly marked. What gets built next depends on the requirements, time, effort, and budget you are willing to invest.

Private on-device planner Honest module maturity No analytics or third-party scripts

Pain-to-Scope Builder

Turn operational friction into a brief you can scope and discuss in four short steps.

Your answers stay on this page.

They remain in browser memory until you refresh or start over. The site sends nothing. Copy, Print, and Email each show the exact text first.

One example of modular connection

See how approved time can link toward payroll—one path among many you could scope.

Workflows are composed from modular pieces; this payroll-input example is one illustration. Country rules, source systems, cut-off controls, customer setup, and operating evidence still need validation—and links you do not see here take requirements and investment to implement.

  1. 01
    Capture and review timePeople record time; managers review exceptions and approvals.
  2. 02
    Validate payroll inputsApproved hours, leave, and employee changes are checked before the run.
  3. 03
    Review the pay runPayroll specialists focus on blocking exceptions and traceable changes.
  4. 04
    Prepare reconciliationFinalized results can be prepared for an accounting handoff that is validated with the customer.

Illustrative role view

Show the right amount of context without changing permission.

Simple and Advanced change how much context is shown—not what a person is allowed to do.

Simple view

Illustrative only. Actual views depend on validated role, module, record scope, and configuration.

Module evidence

Catalog building blocks today—custom scope when you need more.

The current catalog lists Payroll as GA and twenty entries as Beta. These are catalog labels only—not a promise that every business need is already built. Projects remains validation-only here because supporting evidence does not agree on its current status. Needs outside prebuilt planner routes are gathered, estimated, and implemented as modular extensions.

1 entry listed as generally available20 entries listed as BetaWebsite updated 9 August 2026
PAY

Payroll

Catalog: generally available

Core pay-run, payroll-history, and payslip workflows; local rules, recovery, resilience, and customer configuration require validation.

T&A

Time & Attendance

Catalog: Beta

Worklogs, web punch, schedules, exceptions, and manager-approved hourly input; device, lifecycle, and country-rule scope require validation.

HR

Human Resources

Catalog: Beta

Employee records, requests, lifecycle processes, self-service, and documented talent features; sensitive-data access and boundaries require validation.

BEN

Benefits

Catalog: Beta

Benefit eligibility, life events, and enrollment recommendations; plan tax treatment and country-pack scope require validation. Depends on Human Resources and Payroll.

CRM

CRM

Catalog: Beta

Leads, accounts, contacts, opportunities, and activities, with documented draft handoffs; marketing automation and unsupported channels are outside current scope.

ACC

Accounting

Catalog: Beta

Journals, receivables, payables, payments, payroll posting, statements, and lightweight matching; country accounting and tax treatment require validation.

CNT

Contracts

Catalog: Beta

Lifecycle records, renewal windows, files, counterparties, and internal sign-off. Internal sign-off is not legal e-signature.

SDK

Service Desk

Catalog: Beta

Ticket intake, own-ticket status, agent queues, assignment, comments, and policy-based service targets; omnichannel scope is not promised.

PRC

Procurement

Catalog: Beta

Suppliers, requests, approvals, purchase orders, receiving into Inventory, and an optional draft Accounting bill; match depth and tax treatment require validation.

INV

Inventory

Catalog: Beta

Products, stock levels, movements, transfers, low-stock visibility, and operational valuation; statutory valuation and tax treatment are not included.

WRH

Warehouse

Catalog: Beta

Warehouse-location records and inventory transfers. Receiving, picking, and wider warehouse execution remain subject to validation.

WF

Workflow & Approvals

Catalog: Beta

Workflow definitions, approval steps, an inbox, decisions, delegation, and named optional hooks; only evidenced linked flows should be assumed.

CMP

Compliance

Catalog: Beta

Policies, findings, remediation status, and evidence snapshots. It does not establish certification, legal compliance, or assurance readiness.

ANL

Analytics

Catalog: Beta

Report definitions and submitted period snapshots; source data, calculations, freshness, and authorization require validation.

AST

Asset Management

Catalog: Beta

Asset register, assignment, retirement, and maintenance scheduling; broader history and offboarding links require validation.

INT

Integrations

Catalog: Beta

Connection records, status, disconnection, and recorded updates from reviewed systems. This does not promise ready-made connections to every vendor or automatic synchronization.

DOC

Documents

Catalog: Beta

Document storage, folders, tags, and versioned metadata; retention, legal hold, and content-search depth require validation.

BI

Business Intelligence

Catalog: Beta

Saved BI dashboards and widget compositions over analytics KPIs; source freshness, authorization, and KPI ownership require validation. Depends on Analytics.

HUB

Integration Hub

Catalog: Beta

Unified connector registry, connection health, and boundary provider status; connector coverage and operational ownership require validation. Depends on Integrations.

RPT

Report Builder

Catalog: Beta

Guided visual report builder with datasets that appear from enabled modules, plus PDF/XLSX/CSV/Markdown export and print; dataset coverage and authorization require validation.

PRJ

Projects

Status under review

The catalog lists Beta, while supporting product evidence does not establish a current usable offer. It is not recommended as a current path until that contradiction is resolved.

Catalog maturity does not establish deployment state, support tier, country readiness, entitlement, safety, scalability, compliance, or suitability. Planned catalog entries are not presented as current solutions.

Trust, privacy, and validation

Clear enough to act on. Honest about what is still open.

The planner can suggest a documented starting path when your answers match one, explain why, and mark what remains unknown. When your need sits outside prebuilt routes, it points to requirements gathering and an implementation estimate—not an invented catalog path.

01

Private by default

No assessment answer is stored, submitted, logged, or placed in the URL. Refresh or Start over clears it.

02

Permission stays separate

Role previews describe presentation. They do not grant access or promise a customer's final configuration.

03

Maturity is not readiness

GA and Beta are quoted catalog labels. Customer, country, deployment, support, scale, and evidence still need validation before scope, effort, or budget are committed.

04

No certification claim

The platform may support customer-led evidence and control work. It is not currently certified, accredited, or independently attested.

Reviewed English-language example of an MJS Payroll workspace in a non-production environment.
Reviewed product example

A reviewed product view, with a clear non-production boundary.

This English-language screen is from a non-production environment. It was reviewed and sanitized; it contains no customer identity, employee names, or real pay data.

It demonstrates presentation only—not that every workflow is built, shipped, or ready for your environment. Customer configuration, permissions, modules, and readiness require separate validation.

Requirements-led next step

Bring the work pattern and investment context—not a generic module shopping list.

Use your private brief to open a requirements conversation: copy it for your team, print locally, or hand the exact previewed text to your configured mail app. The site sends nothing; your mail app may store or sync drafts according to its settings.

No email address is required to see, copy, or print your result.

Exact export preview


        
        

Copy and Print stay on this device. Email hands the exact preview to your configured mail app, which may store or sync a draft under its own settings.