About Arcus Automations is the company account of a Zoho consultancy, and it states the work a client receives. Arcus is New Zealand-based, working with businesses worldwide. The work is a written scope, the Zoho system configured to that scope, and a handover the team has practised.
Scope
System
Handover
Who runs Arcus Automations is the consultancy named on this page, and a client receives a written scope, the configured system, and a handover the team has practised.
The Arcus Automations team is the group that writes the scope and configures Zoho. Names and roles join this page with their biographies when those biographies are written for publication. Readers who look up the Arcus Automations founders find the company and the work here, and the biographies when they are ready to publish. Product faults stay with Zoho, and a client story waits for the standard on the case studies page.
Arcus Automations is New Zealand-based, working with businesses worldwide.
Projects run remotely unless a written scope says otherwise. A business outside New Zealand uses the same sequence as a business in the country: education, the scope, the configuration, and the handover. Arcus Automations Zoho experience is that sequence made concrete, from the first conversation to the team running the system. Meetings and the documents are written into the scope. Hours and a reply target, when a job needs them, are proposal terms in New Zealand time.
Each item is something you can point at after the work, and each one is named before configuration starts.
The scope names Zoho CRM, Zoho Books, Zoho Creator, or Zoho One, plus the included work and the excluded work. Training is named there too, with the audience, and the pricing page is where the commercial shape of that document is explained, in NZD, with the Zoho licence on Zoho's invoice.
Arcus says which apps to buy, what stays a person's job, and what we would leave unbought. You can take that recommendation and implement it with your own team. The consulting page is where the process is mapped before that recommendation.
The organisation matches the work you already do: Zoho CRM holds the pipeline, Zoho Books holds the finance file, and Zoho Creator covers a record the first two leave out. Zoho One is the suite when the short list needs one licence. A setup package is the lighter start when one team and one app are enough.
The people who run the system practise it before Arcus steps back, and later configuration help is a separate arrangement on the support page. A fault in the Zoho product still goes to Zoho, on Zoho's own desk.
When people are working around Zoho, a health check is findings and a priority list. The fix-up is optional and quoted on its own. The fee is confirmed in writing before the review starts.
Education, a written scope, configuration, then a handover: that is the path on a new organisation and on a live one.
Where a tool helps this team, and where a person should keep the step, is settled before anyone is asked to change how they work.
The workflow, the data, and the systems already in use are the input, and a health check is that review when Zoho is already live.
Zoho is configured against the process you run, and the scope, the training, and what sits outside the build are written first.
Your team runs the system, and later help, if you want it, is Arcus support. The home page is the short version of how a consultant is chosen, before a scope is written. These pages are also gathered on the solutions index.
A client receives a written scope, a Zoho system configured to that scope, and a handover the team has practised. The scope names the apps, the included work, the excluded work, and the training, with the audience named. The people who run the system practise that handover before Arcus steps back. Later configuration help is a separate support arrangement. A fault in the Zoho product stays with Zoho.
Arcus is New Zealand-based, working with businesses worldwide, and the work runs remotely unless a written scope says otherwise. A business outside New Zealand uses the same sequence: education, the scope, the configuration, and the handover. Meetings and documents are part of that scope, the about page is the company account, and the consulting page is where the process mapping is written out.
The Arcus Automations team is described here by the work: writing the scope and configuring Zoho. Names and roles join this page when the biographies are written for publication. Until then a client still receives the scope, the system, and the handover. A personal profile is a later page addition, and the company account stands on the work in the meantime.
Contact Arcus about configuration and process, and contact Zoho when the product itself is at fault. Arcus says which is which during the work, so the ticket lands with the desk that can change the outcome. Support after go-live is an arrangement of its own, described on the support page. It covers configuration, and the product desk stays with Zoho.
A client story is published after the client agrees to be named and approves the draft. The case studies page sets that standard: the client, the apps delivered, approved figures, and an approved sentence. About Arcus Automations links there so a reader can see the bar a story has to clear. You see the draft before it is public, and being named is a choice after the work.
Start with a Zoho health check when people are working around a live system. Arcus reads the layouts, the automations, the users, and a sample of live records, then writes findings and a priority list. The fix-up is optional and quoted on its own. A business that has yet to buy Zoho starts on the consulting page, where the process is agreed before configuration.
Name the system and the workaround, and Arcus replies by email with the next document: a consulting note, a health-check quote, or a written scope. The work itself covers Zoho CRM, Zoho Books, Zoho One, and Zoho Creator. Zoho Flow moves a record between those apps, Zoho Analytics reads the records, and Blueprint is a CRM stage rule.