Every module in the registry
Eleven modules, one customer record, one login. Switch on what a company needs, leave the rest off. Nothing here requires a migration to adopt later.
The modules
Each one works on its own and gets better when the others are on, because they all read and write the same records.
-
Phone and messaging
Numbers, calls, texts, voicemail, call handling and an AI receptionist that answers before the second ring.
-
Field operations
Jobs, technicians, dispatch, day routes, proof of work and a technician app that works without signal.
-
Fleet and dispatch
Orders on a live map, a board your dispatcher can actually run, geofences, ETAs and customer tracking links.
-
Scheduling and agreements
Capacity-aware booking and recurring service agreements that generate their own visits and real MRR.
-
CRM and sales
Every contact, every stage, every note, and who sold it, with commission splits that total to the cent.
-
Inventory and assets
Stock across trucks, units, storage and branches, with sign in and sign out and a chain of custody.
-
Billing and payments
Invoices, payments, voids, usage billing and a recurring-revenue number that survives an audit.
-
Email marketing
Campaigns, sequences and a unified inbox that sends from your own domain, with deliverability handled.
-
Marketing and growth
Service areas, demographics, social scheduling, review requests and attribution down to the campaign.
-
Team and collaboration
Team chat, an account timeline, mentions, roles and departments that keep districts from seeing each other.
-
Reports and analytics
The numbers an owner actually reads, and an advisor that turns them into a plan.
Which plan carries which module
Bundles set the floor. Any module can also be added to any plan on its own.
| Module | Free | Starter | Growth | Scale and above |
|---|---|---|---|---|
| Phone and messaging | 1 number, 1 user | 2 numbers, 3 users | 5 numbers, 10 users | 25 numbers, 25 users |
| Field operations | Basic jobs | Jobs and scheduling | Dispatch, routing and proof | Full operations, multi district |
| Fleet and dispatch | Not included | Not included | Board and tracking links | Live map, geofences, ETAs |
| Scheduling and agreements | Not included | Yes | Yes | Yes |
| CRM and sales | Yes | Yes | Yes | Yes |
| Inventory and assets | Yes | Yes | Yes | Yes |
| Billing and payments | Invoices only | Yes | Yes | Yes |
| Email marketing | 100 per month | 2,000 per month | 10,000 per month | 50,000 per month |
| Marketing and growth | Not included | Basic | Yes | Yes |
| Team and collaboration | Single user | 3 users | 10 users | 25 users |
| Reports and analytics | Basic | Yes | Yes | Yes |
| API, CLI and agent access | Not included | Not included | Yes | Yes |
White label carries every module with no limits and no AlphaFlux branding.
Turning a module on is a configuration change
There is no separate database per feature and no import step between them. A module is a view onto records the platform was already keeping.
That is why a company can start with the phone and the schedule, add dispatch three months later, and add fleet after buying its first truck, without any of it being a project.
It is also why reports stay honest as modules appear. The numbers were always being recorded, so history does not start over when a new module is switched on.
-
Registry driven
Screens, permissions and limits all come from the module registry, so the interface matches what a company actually has.
-
Permissions do not grant themselves
Turning on a module makes new permissions available. Someone still has to assign them, so nobody gains access by accident.
-
History is continuous
A module that starts today reads work that was recorded before it existed. Nothing has to be backfilled.
-
Repackageable
Because the catalogue is data, an operator running the platform under their own brand can define their own bundles and pricing.
Modules that pair well
Some combinations are the reason the platform exists. These are the ones companies turn on first.
-
Phone plus scheduling
The agent answers, checks real capacity and books, so the schedule fills itself instead of waiting for office hours.
-
Field operations plus inventory
A job draws down the technician's stock, and a low part is visible before the next job needs it rather than after.
-
Fleet plus reports
Distance, on time percentage and jobs per technician come out of the same records the dispatcher is already using.
-
Billing plus agreements
Recurring visits and recurring revenue are one object, so the invoiced amount and the booked work cannot drift apart.
-
Email plus CRM
A campaign targets a real pipeline stage, and a reply lands on the account timeline rather than in a separate list.
-
Anything plus agent access
Hand an agent a scoped key and it can work across modules under one set of permissions and one audit trail.
Questions people ask before signing up
Can I buy a module without the bundle around it?
Yes. Any module can be added to any plan as an add on, priced on its own. That is usually how a company moves up: it adds the one thing that is currently costing it money rather than changing plan.
What happens if I switch a module off?
It stops appearing and its operations stop being available. The records it produced are not deleted, and switching it back on restores access to all of it.
Is there a module for something you have not built yet?
The registry is open. New modules follow the same contract as the existing ones, so adding one does not disturb the others, and the interface picks it up without a redesign.
Do the modules share one database?
They share one data model, which is the point. Records are scoped to the company that owns them rather than to the module that created them, so the customer your phone module logged is the customer the dispatch board routes to.
Start on the free plan
Twenty customers, one location, every core module, free permanently. Move up when the work outgrows it.