It is the objection we hear on roughly a third of first calls, and it is a fair one: if the modules are fixed, what happens when our process is different?
The short answer
Modules are fixed. Packs are not.
You choose which modules make up your pack. You rename every field to your vocabulary. You decide who approves what, and above what threshold. You write as many automations as you like, and they can call any action in any module you have enabled. All of that is yours.
What you cannot do is change what happens inside a module - how stock is issued, how tax is computed, how an invoice is numbered.
Why that line, and not somewhere more generous
Because every line further out costs you an upgrade.
A forked module cannot take a patch. A business running a forked module is running a version of the software nobody else has, which means nobody else has found its bugs. Within two years the fork is load-bearing, the person who wrote it has left, and the upgrade that would fix the thing you are complaining about is a project rather than a Tuesday.
Our support queue is short for exactly one reason: every customer is running the same code.
What we do when a pack genuinely does not fit
About one enquiry in nine needs something no pack can do. We build a custom pack - the same unmodified modules, assembled differently, with new actions and automations written around them - for a fixed fee. Or we say so on the first call and suggest someone else. Both of those are better outcomes than a fork.