A Zoho partner NZ you can brief
A Zoho partner NZ implements Zoho and advises on it. Arcus is New Zealand-based, working with businesses worldwide.
- 01 Record
- 02 Stage
- 03 Hand-off
What is a Zoho partner?
A Zoho partner, in ordinary language, is a firm that implements Zoho and advises on it. Arcus takes the brief, recommends which apps to use, and builds against that brief, so the relationship you can use is the work itself.
Arcus is the Zoho partner New Zealand businesses call when records are scattered and a daily task is too slow. A Zoho implementation partner in NZ configures the apps against a scope you can read before the build starts. Zoho CRM holds the pipeline, and Blueprint holds a stage until the fields that stage requires are filled. Zoho Books holds the finance file the team closes. Zoho One is the suite when several of those apps share one subscription. Zoho Creator holds a record the other apps leave in a spreadsheet. Zoho Flow moves a record from one of those apps to the next, and Zoho Analytics reads the records they already store. A Zoho consulting partner in NZ is that same firm, asked while the process is still a decision rather than a screen. The advice sits on the Zoho consulting page, and the build is a separate proposal in NZD. Zoho reseller NZ usually means a firm that sells the subscription, and you buy the licence from Zoho. Arcus implements the product and advises on it. Rank and any identification number stay off this site, and the brief is what we publish for you to keep.
Do I need a Zoho partner to buy Zoho?
You buy the licence from Zoho. A partner is how the implementation gets done, once you want the apps configured for the way the business actually works day to day.
The subscription invoice comes from Zoho, and the proposal for our work is a separate document in NZD that names a package, a support arrangement, or a project. You can purchase Zoho and run a simple setup yourself when one team will use one app for a straightforward process. Bring Arcus in when you want a written brief, a recommendation you can refuse, and a build that follows that brief. A system that is already live starts well with a Zoho health check, because the findings come before any new scope. A new organisation and a limited import can be a setup package with the edges written down. A longer history, or behaviour written for one business, is a project with its own proposal. The pricing page explains how that figure is written, and the Zoho services index shows the other live work beside this page.
Buy the licence from Zoho
You complete the subscription with Zoho, and the invoice for Zoho CRM, Zoho Books, Zoho One, or Zoho Creator comes from Zoho. Arcus can help you choose an edition while the advice is still open, and that choice leaves the subscription on Zoho’s invoice. Our document stays a separate proposal, so the licence and the labour are easy to tell apart when you compare them.
Brief the implementation
A partner is how the implementation gets done: Arcus writes the brief, configures the apps, and hands the system to the people who will run it each week. The proposal for that work is in NZD and names what is included before anyone starts. A simple case can stay with your own team, and a shared customer record is the point where a written scope earns its place.
What you can brief
You receive four documents, and each one states its contents. The brief names the record and the slow task. The recommendation names which apps to turn on, which to leave, and whether the next step is a health check, a package, or a project. The build covers configuration, the import, and any custom piece the brief already named. The handover is the people who will run the system practising the screens they will open. The engagement follows those four labelled steps, and any dates sit in the proposal.
The record, and the slow task
The brief starts with where the customer record lives today, and with the daily task that takes too long for the team. The menu of apps comes after that conversation, on the Zoho CRM, Zoho Books, Zoho One, or Zoho Creator page that matches the job you actually have.
Advice you can refuse
The advice names which apps to turn on, what to leave alone, and whether the next step is a health check, a package, or a project. You can implement with Arcus, or you can take the recommendation and stop there. The Zoho consulting page is where that decision is written out before a build is commissioned.
A build against the brief
The build covers configuration, the import, and any custom piece the brief has already named in writing. A familiar product name still needs its own connection, and that connection is scoped on the proposal before it is built. The proposal is the boundary of the work, and a later change is quoted beside the original scope.
Two invoices, kept apart
Zoho bills the licence on Zoho’s invoice, and Arcus bills the implementation, the package, or the support on our own document. The two documents stay apart after go-live, so a subscription change and a change to the build are easy to tell apart. You can see which firm is asking you to pay, and for which kind of thing.
A person to ask once you are live
Training and configuration sit with Arcus when a support arrangement has been agreed in the proposal. A fault in the product goes to Zoho, and we can help you describe that fault so the vendor queue can see it. The Zoho support page draws that line, and the about page describes the path from the first brief through to handover.
After you are live
Support is a separate arrangement from the build, and it covers configuration, the process, and small changes on a system that is already in use. A new app, a migration of history, or a new connection is quoted as its own project rather than folded into the original hours. Product faults stay with Zoho, because Arcus is a separate firm that implements and advises. The hours, the channel, and the response target are written in the proposal before support starts, and they belong to that arrangement. Remote delivery is the normal shape, and Arcus is New Zealand-based, working with businesses worldwide.
Questions before you send a brief
Are you a Zoho partner?
In ordinary language, yes. Arcus implements Zoho and advises on it for a business that wants the work written down before anyone builds. Zoho bills the licence on Zoho’s invoice. Arcus bills the implementation, a package, or support, and that figure is in NZD inside a proposal. We publish the brief and the build. Rank and any identification number stay off this site. The account is configured for the way your business operates, in New Zealand or further afield.
Do you work only inside New Zealand?
Arcus is New Zealand-based, working with businesses worldwide. The brief is the same wherever the business operates: which apps, which records, and which daily task is too slow. Remote work is the normal shape, and a written scope names a visit when one is actually required. The Zoho account is configured for that business, and the proposal is still in NZD. Distance changes the meeting, and the scope of the work stays the thing we write down.
Will hiring Arcus change the Zoho invoice?
Hiring Arcus leaves Zoho’s subscription on Zoho’s invoice. Our proposal is a separate figure, in NZD, for implementation, a package, or support. Choosing an edition can happen during the advice, and the subscription invoice still comes from Zoho. The two documents stay apart after go-live as well. Support, when you want it, is another Arcus document, and the licence stays on Zoho’s side of that line.
What should I send with the enquiry?
Send the Zoho apps you run, or the ones you are considering, and the task that is too slow. Say where the customer record lives, and whether the history is tidy enough for a fixed package. We reply by email with the shape of the work. When that shape is honest, the next document is a written scope. The build waits for the scope you accept. A live system can start with a health check instead of a new build.
Who handles a fault in the product?
A fault in the Zoho product goes to Zoho. Arcus handles configuration, the process, and small changes when a support arrangement is in place. We can help you describe a product fault so the vendor queue can see it clearly. Arcus is a separate firm from Zoho. Training for your team sits with Arcus when the proposal includes it. A new app or a new connection is a project, quoted on its own, rather than a line slipped inside support.
Can we use the advice and build it ourselves?
Yes. The recommendation is yours to refuse, or to take to another firm. Advice ends at that document unless you ask Arcus to implement what it says. The quote for a build is a different document, in NZD, and it names what is included before work starts. Some businesses start with the advice, then come back when they want the build. Others already know the scope and want implementation against a brief they can stand behind.
Bring the brief
Tell us the apps you have, or the ones you are considering, and the daily task that is too slow. We reply by email with the shape of the work, and a written scope follows when that shape is honest. The brief can name Zoho CRM, Zoho Books, Zoho One, and Zoho Creator. Zoho Flow moves a record between them, Zoho Analytics reads those records, and Blueprint holds a CRM stage until its fields are filled.