When learning QuickBase, I noticed a shift in its cost structure. It operated on a cost-efficient model tied to the number of users, with invoicing based on applicants. The recent changes have increased costs based on user activity, such as viewing reports or interacting with specific fields. This shift makes QuickBase more expensive to use as activity increases. Lowering these costs could potentially broaden QuickBase's user base, similar to how Microsoft PowerApps operates. The visualization in QuickBase could be enhanced. Due to cost and usage efficiency concerns, our utilization of QuickBase is limited within our company. A few individuals are currently utilizing QuickBase. We need to consider the cost-to-usage ratio and prioritize increasing adoption.
