Modular CRM billing for small business owners

The moment arrives when a micro-business owner realizes they need one specific CRM feature — a second pipeline, a second user login, or a deal tracking view — and the only way to get it is to upgrade every seat in the account to the next tier. One complaint describes this exactly: jumping from $15 to $50 per user for all users, just to unlock one feature. That's not a pricing decision made for the customer's benefit — it's made for the vendor's revenue expansion, and incumbents have every incentive to keep it that way because tier-based billing is their upsell engine.

The structural problem is that CRM vendors bundle features into tiers to manufacture urgency toward upgrades. They're not going to unbundle themselves. The buyer — often the business owner — is also the user, so the pain is real, but they lack leverage to demand change from a vendor who'd rather they upgrade entirely.

What's missing is a lightweight CRM billing layer that charges per feature actually used, not per tier, so a two-person shop pays for two pipelines and two logins and nothing else. Not a watered-down free tier with paywalls, and not a 'starter edition' with a pricing jump too large for micro-businesses — which is a specific complaint here.

This is a business because the need recurs every time a small team grows by one person or wants one new capability. Without it, they either overpay dramatically for features they don't use, or they stay on a limiting plan and manually work around missing features — which costs time every single week.

What to build

Build a CRM with per-feature billing — each pipeline, each additional user seat, each automation rule priced individually — so a two-person business pays only for what they actually activate, starting with invoicing and pipeline management as the core.

Where to start

Target freelancers and consultants who need invoicing plus pipeline tracking and currently pay for a CRM and a separate invoicing tool — offer both in one bill with no tier floor, undercutting the combined cost of two subscriptions.

The hard part

Per-feature billing is technically straightforward but commercially fragile at the low end — customers who buy only two features have too little switching cost and too little revenue to justify support overhead, so you have to design the feature set so natural usage expands spend without requiring an upsell conversation.

How it makes money

Usage-based monthly billing: a base fee of ~$9/month covering one user and one pipeline, then flat per-unit add-ons (e.g., $4 per additional user, $6 per additional pipeline, $8 for automation), with no annual commitment required.