Individual Modules or All Access: Choose Around Your Team’s Work
Compare individual PD modules and All Access by workflow, edition and installation. A practical decision guide for WHMCS and Blesta hosting teams.
Choose individual modules when your requirement is narrow and established; consider All Access when several teams need a broader toolkit that will grow. The useful comparison is the work you expect to do, the editions it needs and the installation it belongs to—not simply how many products you can unlock.
PD Modules supports both WHMCS and Blesta. This is one decision guide for the two platforms, because the buying questions are shared. Use your own platform’s catalogue for the current modules and terms.
Three situations, three sensible starting points
| Your situation | Starting point | Reason |
|---|---|---|
| One repeated task, such as shared notes | A suitable free module | Solve the task before expanding the toolkit |
| One defined paid workflow | An individual module | Match the licence to a specific operational need |
| Several workflows across support, sales and operations | Evaluate All Access | Consider current needs and realistic upcoming adoption together |
Scenario 1: a small team with one bottleneck
Imagine two colleagues losing the next action between shifts. If shared notes and reminders address that problem, start there. A broad subscription does not make an unclear handover process clearer on its own.
Write down the task, the person responsible and the result you want to see. A free module can be a complete answer rather than a temporary stop on the way to a paid plan.
Scenario 2: one specialised workflow
A team may have a defined need for versioned customer agreements, or for a particular automated offer. An individual module gives that decision a clear scope. Compare its current edition and features with the task, rather than buying capabilities nobody plans to use.
Keep a short list of related needs that are genuinely expected next. If the list grows, revisit the licence choice using current terms instead of assuming a fixed break-even number will always apply.
Scenario 3: several teams sharing a growing toolkit
All Access makes more sense to evaluate when support, operations and sales each have useful workflows to introduce. The current offer includes PD modules for the installation, Pro editions where available, and modules added while the subscription is active. You still choose which modules to install and when to introduce them.
That is the practical distinction between availability and adoption. Access to another module can remove a separate purchase decision, but it does not configure your process, teach staff or establish the right settings automatically.
Check these four boundaries
- Installation: All Access applies to the installation it is added to. A second installation needs its own coverage; do not assume one subscription covers every business or staging site.
- Edition: where a module has Pro, the current All Access offer includes it. When buying individually, identify whether the feature you want is free, paid or Pro.
- Future additions: the offer covers modules added while the subscription is active. This is not a reason to assume an unannounced feature or a particular release date.
- Provider services: a module licence is separate from charges for a cloud or AI provider you connect. Include those services in your own planning.
Make a short decision sheet
For each intended workflow, record the module, required edition, installation, responsible person and planned adoption date. Mark needs as “now”, “next” or “no current use”. Compare current individual terms for the first two groups with All Access on the same installation.
Include the time needed to configure and teach the workflow. A module that nobody owns will not create value merely because it is available. Equally, a growing team may value having the next useful tool available without a separate purchase each time.
Review the decision when the work changes: a new service launch, another support colleague or an additional billing installation are better triggers than collecting modules for their own sake.
Check the current offer for your platform
Use the WHMCS catalogue or Blesta catalogue for current individual options and All Access details. The PD Modules overview explains the shared panel and support approach. We keep changing prices and requirements on those product pages rather than repeating them here.
Frequently asked questions
Does All Access install every module automatically?
No. It provides access to the covered modules; you choose the ones to install and use.
Are Pro editions included?
Yes, the current All Access offer includes Pro editions where a module has one. Check the current catalogue when making your decision.
Does it include future modules?
The current offer includes modules added while the subscription is active. It does not promise a particular future product or launch date.
Are cloud and AI provider bills included?
No. Charges from a provider you connect are separate from your PD module subscription.
Can one subscription cover multiple installations?
All Access is tied to its installation. Plan separate coverage for another installation and check the current terms before purchase.
