A service designed for structured businesses can be challenging for those who work with a few people. A larger business may instead have needs that an elementary solution does not cover. Designing for a heterogeneous network requires observing these differences.
I propose to compare the work needed to use the service, in addition to its stated cost. Modules, updates and operational requirements take up time. When they require skills concentrated in one person, they can become an obstacle for small businesses.
A hypothetical example is a common report that needs a lot of manual data. An essential version can allow a first use, leaving additional insights to those who have the necessary resources. Simplification must retain what is really needed for the result and control.
The differentiation of the service should be motivated by the need addressed and compatible with the rules of the network. It does not mean to assume that all small members are equal or that the size explains each difficulty. Listening and trials on different groups allow to recognize concrete barriers. The desired result is workable access, with conditions that members can understand and compare.