NovaSoft One buying guide
Which NovaSoft One CRM plan fits your team?
Choose the lowest tier that covers the work you need now. The right plan depends on your workflow and controls, as well as the number of people using it.
Compare the reason to choose each plan
Scroll sideways to compare all columns.
| Plan | What it adds | A useful buying question |
|---|---|---|
| Free | Core customer records, sales steps and quotes within Free limits. | Can you evaluate your core customer and sales workflow within the published allowances? |
| Starter | Forms, bookings, service, projects and customer portal. | Do you need to connect enquiries and sales with delivery or service? |
| Professional | Automation, forecasting, advanced reports and customisation. | Which repeatable process or reporting requirement justifies the next tier? |
| Business | Advanced permissions, audit history and governance. | What access or oversight requirement must your workspace meet? |
| Enterprise | Hands-on NovaSoft tailoring and optimisation within an agreed allowance. | What help do you need from NovaSoft, and what does the agreed service cover? |
This is a workflow comparison, not a copy of the billing table. The official One pricing and capability comparison provides current prices, currency, tax treatment, user charges and limits. Check it before purchasing.
Use a real requirement to decide
A small sales pilot: a founder and colleague need to keep customer details, quote context and next actions together. Begin by testing the core workflow on Free, then check its limits against the records and people you need.
A sales-to-delivery handover: accepted work must be visible to the person managing the project. Test the relevant Starter workflow, including the exception where a customer changes the scope after accepting a quote.
A repeatable follow-up or reporting need: write down the trigger, expected action and exception, or the business question a report must answer. Evaluate Professional against that specific requirement rather than upgrading because “more automation” sounds useful.
Different responsibilities and oversight: list who should see or change each part of the workspace. Evaluate Business if those requirements depend on its advanced controls. Ask for a demonstration of the access model you actually need.
Make the trial a short set of tests
- Create or find a customer and record an enquiry with a named owner.
- Move one opportunity through the stages you use and review its next action.
- If delivery is in scope, have another person find the accepted work and dates.
- Test one changed or cancelled job, rather than only the ideal case.
- Check the report, automation or access control that would cause you to buy a higher tier.
Record whether each test passes, what is missing and whether the gap is configuration, training or a product requirement. A feature can exist without solving your particular workflow. The first-team-workflow guide provides a worked pilot example.
Include mobile work in your evaluation
The iPhone and iPad app is coming soon. When it becomes available, include it in the same pilot as the web workspace.
Ask one person to find the shared customer history, another to review their assigned work, and a service user to check the ticket context available to them. Confirm notification permissions and the access each person actually has. The mobile app follows the workspace’s plan, roles and permissions; a preview screen does not mean every feature is included in every tier.
See the mobile app overview for the team workflow and availability.
Budget for the rollout as well as the licence
List the people who need the workspace and the published billing basis. Then separate the plan charge from data preparation, implementation, training, custom development and ongoing support. Confirm which of those services are included in your proposal.
For Enterprise, ask what fits within the agreed service allowance and what needs a separate scope. If you need specialist integrations, document the systems, records and outcomes before requesting an estimate. A plan with more features is not a promise that every integration is already built.
When another route is worth considering
If you mainly manage your own clients, follow-ups and invoices from an iPhone, read the UPly versus NovaSoft One comparison. An individual can still choose One when the broader CRM suits the work.
If your records, approvals or deployment requirements are unusual, discuss custom CRM development. First check what One can do out of the box. A custom system means extra decisions about what to build, who maintains it and how it’s handed over.
Before you commit
Should a growing company automatically choose Business?
No. Upgrade when you need a specific feature or control, not just because the team is growing.
Does Enterprise mean unlimited custom development?
No. Confirm the service allowance and deliverables in the agreement. Bespoke development and additional work need their own scope.
What should we ask about changing plans?
Ask how access to your existing records and functions changes, who needs to be informed, and whether any workflow depends on a higher-tier capability.
Related guides
Continue with the next decision
Current One prices and billing
Scroll sideways to compare all columns.
| Plan | Published Australian-dollar price | Billing basis |
|---|---|---|
| Free | A$0 | Up to two users |
| Starter | A$15 | Per active user each month, excluding GST |
| Professional | A$39 | Per active user each month, excluding GST |
| Business | A$69 | Per active user each month, excluding GST |
| Enterprise | A$2,300 monthly base + A$80 per active user each month | Sales-assisted; excluding GST |
Free currently includes 250 contacts, 50 companies and 25 active deals. Paid plan features differ. Implementation, migration and custom work need a separate scope. Check the official pricing and capability table before purchase.
Talk to NovaSoft
Want help choosing?
Tell us what you need to keep track of, who’s involved and what you use today.