01
Name the first apps
Write the apps the operation depends on, and park the rest until each one shares a record. A clean single-app start can be a setup package instead of a suite rollout.
Zoho One in New Zealand, turned on as a short list
Zoho One in New Zealand is the short list of apps a small business will actually use, with the licence bought from Zoho.
- 01 Record
- 02 Stage
- 03 Hand-off
What is included in Zoho One?
Zoho One is the suite a business buys from Zoho, and the apps on an account are whatever that subscription lists.
Arcus leaves Zoho's full catalogue off this page, because a name on the menu is a licensing fact and the build is a separate choice. A Zoho One consultant in New Zealand writes down the handful the operation will use. The list often starts with Zoho CRM , Zoho Books , and a Zoho Creator app when the record lives outside those two. That short list is the Zoho One implementation in New Zealand. Zoho One New Zealand buyers are choosing which apps the team will open. A Zoho One partner NZ writes that list down, and you still buy the licence from Zoho. The written scope names those apps.
Is Zoho One worth it for a small New Zealand business?
Zoho One is worth buying when a small business will run more than one Zoho app and wants them on one subscription from Zoho.
A single app is a different job, and CRM, Books, and Creator each have an implementation when that app is the whole brief. Turning every included app on in one week produces a menu, while the spreadsheet often remains the system people trust. Choosing the suite or the single apps is a consulting question while the daily process is still being named. Arcus is New Zealand-based, working with businesses worldwide, and the same test applies wherever the business operates.
How long does a Zoho One implementation take?
A Zoho One implementation in New Zealand takes the time written in the scope for that short list, and this page leaves the figure in that document.
The scope names the apps, the records that move, and the order of the work. A later app is a new scope, or a return to consulting when the process has changed. One shared duration would treat every small business as the same job, so the number stays with the proposal.
What a small business actually turns on
The Zoho One setup is the short list below, and each line is something you can point at when the work ends.
-
The first apps, named
The daily work names the apps it depends on. Zoho CRM holds the customer the sales team works. Zoho Books holds the finance file. Zoho Creator holds a record when the other two leave it in a spreadsheet. Further apps wait until each one names the record it shares.
-
The account, read on the screen
Business location, users, and the data centre shown on the account. Read that screen. Do not assume a region.
-
One customer the apps agree on
The apps you turned on agree who the customer is. That agreement is configuration, written in the scope before the wider team is invited in.
-
A reason for every extra app
Each extra app names the record it shares with the others. An app joins the short list when that sentence is specific. Inclusion in the suite stays a Zoho licensing fact, and the build decision stays in the scope.
-
The licence, bought from Zoho
Arcus explains the subscription the business is buying. The invoice for that subscription comes from Zoho. The Arcus invoice covers the implementation and, when you ask for it, support for the apps in use.
How the Zoho One setup runs
Three moves, in this order. The account line is the screen Zoho already shows.
02
Confirm the account
Business location, users and the data centre on the account. Do not infer the centre from the city of the business.
03
Leave help on the apps in use
After go-live, configuration and small changes sit with Arcus support when the proposal includes them. When an account is already live and feels larger than the work, start with a health check .
Who configures the short list
Arcus is New Zealand-based, working with businesses worldwide. We implement the short list and explain the subscription. Zoho sells the licence. How a written scope is priced sits on the pricing page, and that page is about Arcus work, separate from Zoho's invoice. The working relationship is the brief and the build.
Questions before a Zoho One scope
Who sells the Zoho One licence?
You buy the Zoho One licence from Zoho, and Arcus configures the short list in a written scope. The subscription invoice stays on Zoho's document, and the Arcus invoice covers the implementation. Support for the apps in use sits on that Arcus arrangement when you ask for it. Arcus is New Zealand-based, working with businesses worldwide, so the split holds for a local team and for a team elsewhere.
Can Zoho CRM and Zoho Books join later?
A sensible Zoho One setup starts with the app the operation depends on, then adds Zoho CRM or Zoho Books once that record is stable. Each of those apps has its own implementation, because the pipeline and the finance file are different work. A later expansion is a new written scope, or consulting if the process still needs a name. Support, when the proposal includes it, covers the apps already in use.
What if the account already feels too large?
Start with a health check of the apps already turned on, before anyone adds another. The health check returns written findings and a priority list your team can act on. Arcus then names which apps earn a place on the short list, and which wait until they share a record. The remedy for a crowded account is that short list, scoped before the next app goes live.
Who helps after the short list is live?
Arcus support covers configuration, process, and small changes for the apps you kept, when the proposal includes that arrangement. Zoho handles a fault in the product itself. A new app, or a new path between apps, is a new scope written before the work starts. The handover shows the people who own each record how it moves, so the team can run the short list once Arcus steps back.
When is a single app the better brief?
A single app has its own implementation, and the brief stops at that system. Zoho CRM, Zoho Books, and Zoho Creator are the right pages when the business needs that one tool. Zoho One is the right conversation when more than one app will share the customer, or when the suite is already on and feels larger than the work. Consulting is where that choice is made, before anyone buys.
What do you receive when the setup ends?
You receive the named short list, the path each record takes between those apps, and a note of which apps stayed parked and why. The people who will use the system learn that path as part of the written scope. Small changes to the apps in use can sit in support when the proposal says so. A later expansion is consulting or a project, written before another app is turned on.
Start a Zoho One in New Zealand brief
Name the apps you already pay Zoho for. Enquire, and the reply names what to turn on, what to leave parked, and the order a written scope would follow. Zoho Flow moves a record between the apps you turned on. Zoho Analytics reads those records. Blueprint holds a CRM stage until the fields that stage needs are filled.