Question 1

What's the difference between a module and a feature?

Accepted Answer

A module is a functional area — sales, payroll, inventory. A feature is a capability inside it — lead scoring, an attendance punch, a reorder alert. You choose modules to decide what your CRM does; the features within each are configured to how you do it. The full capability list lives on the features page.

Question 2

Do we have to take a whole module, or can we take parts?

Accepted Answer

Parts. A module is a convenient grouping, not an all-or-nothing package. If you need attendance but not payroll, you take attendance. The composer above groups them for clarity, but the build is scoped module-by-module and feature-by-feature to what you actually use.

Question 3

Can we add a module later?

Accepted Answer

Yes, and it is a configuration rather than a new purchase, because it is one build with no per-module pricing. Many clients start with sales and support, get the data flowing, then add finance or HR once the core is settled. The data model is designed at the start to accommodate what you might add.

Question 4

What if the module we need isn't in this list?

Accepted Answer

We build it. This list covers what most businesses share; the module that matters most to you is often the one no product has — a token booking desk, a BOQ tracker, an 80G receipt engine. Those are built from scratch as first-class parts of your system, not squeezed into a custom field.

Sales & Revenue

Finance & Accounting

People & Payroll

Operations

Customer & Support

Insight & Control

The module that matters most is usually the one no product has

Modules, answered

Bring your six must-have modules

Pick the rooms. We build the house.

Switch on what you need. Leave the rest off.