Modules — Base CRM, Add-ons & Industry Packs
Start with CRM, add Invoice, Booking, or Subscriptions when you need them, then layer industry packs like Coworking or Gym.
ModulCRM is organized into three layers. The base module is CRM — contacts, pipeline, and activity tracking that every workspace runs on regardless of industry. Add-ons sit on top of that base and solve a specific job: Invoice handles billing and payments, Booking handles calendars and resources, and Subscriptions handles recurring plans and membership revenue. Industry packs, currently Coworking and, later, Gym, bundle the base module and relevant add-ons into a vertical-specific workflow so you are not assembling every piece yourself.
Every module — base, add-on, or industry pack — is billed and tiered on its own across Basic, Growth, and Enterprise. That means a small consultancy and a multi-location coworking operator can both run on ModulCRM, paying for entirely different combinations of modules and tiers without either one overpaying for capability they do not use.
You can browse modules by category below, open any module for a full breakdown of its features across all three tiers, or jump straight to the pricing page to see how a few common combinations come together in practice.
Base module
The foundation every ModulCRM workspace starts with.
Add-ons
Plug in billing, bookings, and recurring revenue when you need them.
Invoice
LaunchCreate, send, and track invoices
Send branded invoices, accept online payments, and keep cashflow visible — tightly linked to your CRM contacts.
Open Invoice page →Booking
LaunchRooms, resources, and appointments
Day, week, and month calendars for meeting rooms, desks, and appointments — with self-service booking and CRM-linked clients.
Open Booking page →Subscriptions
LaunchPlans, billing cycles, and MRR
Create plans, manage customer subscriptions, and sync recurring revenue with invoicing and entitlements.
Open Subscriptions page →Industry-specific modules
Vertical packs built for how your industry actually operates.
Coworking
LaunchBuilt for coworking operators
Floor plans, desks, offices, member portals, credits, mailroom, and access — purpose-built for flex spaces.
Open Coworking page →Gym
LaterMemberships, classes, and check-in
A vertical pack for gyms — memberships, class scheduling, check-in, PT packages, and recurring billing.
Open Gym page →Base module vs. add-ons vs. industry packs
It helps to think of the three layers as answering three different questions. The base CRM module answers “who is this customer and where are they in our process?” regardless of industry. Add-ons answer a specific operational question — Invoice answers “how do we get paid?”, Booking answers “how do we schedule time or space?”, Subscriptions answers “how do we bill recurring plans?”
Industry packs answer a narrower question that only makes sense inside a specific vertical — Coworking answers “how do we run a shared physical space with desks, offices, and mail?” A gym or clinic would ask a completely different version of that same question, which is exactly why industry packs exist as their own layer instead of being folded into the generic add-ons.
Which modules should you enable?
Three example stacks show how the same platform fits very different businesses.
Solo consultant or small service team
CRM + Invoice
A single person or small team booking client work and billing for it does not need bookings, subscriptions, or an industry pack. CRM tracks the pipeline and relationship, Invoice handles billing and payment tracking — both at the Basic tier. When appointment scheduling becomes a bottleneck, Booking is one module away.
Coworking operator
CRM + Invoice + Booking + Subscriptions + Coworking
A flex-space business needs the full first-wave stack: CRM for member relationships, Invoice for billing, Booking for meeting rooms and desks, Subscriptions for membership plans, and the Coworking pack for floor plans, credits, and mailroom. Most single-site operators start at Basic across the board and move individual modules to Growth as volume increases.
Multi-location fitness or coworking brand
Same modules, higher tiers on Booking, Subscriptions, and the industry pack
Once a business runs several sites, the CRM module itself may stay at Growth while Booking, Subscriptions, and the industry pack move to Growth or Enterprise for multi-location governance, dynamic pricing, and deeper analytics. Because tiers are chosen per module, you upgrade exactly the parts of the stack that are under strain — not the whole platform at once.
Frequently asked questions
- What is the difference between a base module, an add-on, and an industry pack?
- The base module is CRM — the contact and pipeline foundation every workspace runs on. Add-ons like Invoice, Booking, and Subscriptions extend what the CRM can do for any business. Industry packs like Coworking bundle the specific workflows a vertical needs, built on top of the base module and relevant add-ons.
- Do I have to enable every add-on to use an industry pack?
- Industry packs are designed to work alongside the relevant add-ons — for example, Coworking depends on Booking and Subscriptions for its floor-plan and membership features — but you enable and tier each module independently based on what your business actually needs.
- Can I mix tiers across modules — Basic on one, Growth on another?
- Yes. That is the point of pricing modules independently. A business might run CRM and Invoice at Basic while Booking sits at Growth because room scheduling is the most complex part of their operation.
- Which modules are available first, and which are on the roadmap?
- CRM, Invoice, Booking, Subscriptions, and the Coworking industry pack make up the first launch wave. Gym is the next planned industry pack, with further add-ons on the longer-term roadmap. Join the waitlist to be notified as each one opens for early access.
- How do I know which tier of a module I need?
- Each module page lists exactly what is included at Basic, Growth, and Enterprise. A good rule of thumb: start at Basic, and move a specific module to Growth only once that module's workflow — not the whole platform — becomes a bottleneck.