Count roles, not names
Separate daily users, managers, administrators, occasional users, external users, and integration identities.
- Paid-seat rules
- Minimum purchase
- Role restrictions
Model seats, editions, add-ons, implementation, migration, integrations, administration, support, and recurring change—not only the advertised monthly price.
The cheapest license can become the most expensive operating model when the team pays for unused seats, add-ons, consultants, workarounds, and slow changes.
Use a three-year horizon and document the assumptions behind every line.
| Cost layer | Include | Common omission |
|---|---|---|
| Subscription | Paid users, admins, guests, billing term, minimum seats, currencies, taxes, and expected growth. | Pricing only the initial pilot seats. |
| Edition and add-ons | Automation, reporting, AI, storage, email, telephony, sandbox, API, support, and portal capacity. | Assuming a feature shown in a demo is included in the chosen tier. |
| Implementation | Discovery, configuration, customization, migration, cleansing, integrations, testing, training, and launch support. | Treating internal staff time as free. |
| Operations | Administration, data quality, access review, integration monitoring, support, release testing, and governance. | Budgeting software but not an accountable owner. |
| Change | New fields, workflow routes, reports, roles, integrations, testing, and adoption updates. | Using the initial implementation rate for a constantly changing process. |
| Exit or replatform | Export, archive, media, integration replacement, overlap, migration, and decommissioning. | Assuming data export equals an executable migration plan. |
Use actual operating scenarios instead of a generic per-seat calculator.
Separate daily users, managers, administrators, occasional users, external users, and integration identities.
Tie each required capability to the exact edition or add-on.
Name who manages data, access, configuration, integrations, support, and release validation.
Estimate one field/view change, one workflow change, and one integration or data-model change.
Compare the same concrete change: add a customer tier, route high-risk records, create a role view, and update the dashboard.
Internal analysis, vendor or partner queue, configuration or code, testing, release, and follow-up create an elapsed cost beyond direct fees.
A trained administrator can often complete and test the focused configuration directly, subject to governance and plan capability.
Jodoo currently includes five users on its permanent free plan. Paid plans expand capacity and capabilities; verify the current official pricing page.
Use representative records and all five roles within current free-plan limits.
Designing a toy pilot that excludes the manager or administrator.
Estimate paid seats, data, automation, storage, administration, and support using expected three-year volume.
Comparing only headline per-user price.
Confirm API, webhook, identity, security, support, and implementation requirements.
Assuming every advanced capability is available on every plan.
Cost ranges widely by users, edition, features, implementation, data migration, integrations, support, administration, and change effort. Build a three-year model using the actual roles and workflows.
Data cleanup, migration, custom process design, integrations, permissions, testing, training, partner services, and low adoption often cost more than the base license.
Jodoo offers a permanent free plan with five users and usage limits. Teams can configure a CRM app within current plan capabilities, then evaluate paid capacity and advanced features as usage grows.
No-code configuration lets trained administrators own many routine changes while the organization keeps governance and testing.
A more expensive specialist CRM can still be the better value when its native sales, marketing, service, analytics, or enterprise capabilities avoid custom work.