Understanding Licensing and Database Limits
WebDev CRM uses database capacity to define licensing — not feature restrictions.
All core functionality is available based on your licence. What changes between plans is how much data you can store, not what you’re allowed to do.
This approach reflects how client work actually grows over time.
Why Database Limits Are Used
As your business grows, so does the amount of information you manage:
-
Contacts
-
Companies
-
Quotes
-
Invoices
-
Projects
Limiting features often breaks real workflows. Limiting capacity allows you to keep working the same way while scaling naturally.
You can start small and upgrade only when your data grows.
What Counts Toward Your Limit
Each record stored in the database counts toward your plan’s capacity.
Examples include:
-
One Contact
-
One Company
-
One Quote
-
One Invoice
-
One Project
You always have full access to existing data. When you reach a limit, you can upgrade to increase capacity - without losing functionality or history.
How Licensing Works
Licences are tied to your site, not your clients.
Upgrading a licence:
-
Increases available database capacity
-
Does not remove or unlock features
-
Does not require reconfiguration
Downgrading reduces capacity for future records but never deletes existing data.
Summary
Licensing in WebDev CRM is designed to respect continuity.
By basing plans on database limits rather than features, WebDev CRM allows you to grow without changing how you work — keeping ownership, context, and workflow intact as your business evolves.
