01
Name the record
Write what is tracked, who creates it, and when it is finished. If that sentence is still fuzzy, the next document is a consulting note, and the build waits.
A Zoho Creator developer in New Zealand
A Zoho Creator developer in New Zealand builds the app that holds the record Zoho CRM and Zoho Books leave in a spreadsheet.
- 01 Record
- 02 Stage
- 03 Hand-off
What can you build with Zoho Creator?
You build the app that holds a record Zoho CRM and Zoho Books do not own, such as an inspection, an application, a job sheet, or an approval.
The app has a named record, the people who create it, and a point at which it is finished. Forms, permissions, and one report are the first version. Extra portals wait until that version is in use. Customers and invoices stay in Zoho CRM and Zoho Books unless a written scope names one step both must see. Zoho Creator in New Zealand is that boundary: the odd record gets a home, and the ledger stays where finance already closes it.
How much does a custom Zoho Creator app cost?
A custom Zoho Creator app costs the figure in a written project quote, and the pricing page explains how Arcus shapes project work.
Each app is specified for one business and quoted on its own, in NZD. The quote names the record, the forms, the permissions, the one report, and the handover. Training inside that scope is the handover, for the people who will use the app. A later change is support or a new quote, and the proposal says which one before the build starts.
What is Deluge inside a Creator app?
Deluge is Zoho's scripting language, and in plain words it is the script that runs when someone saves a form.
That script can calculate a field, check who may open a record, or create a related row in Zoho CRM or Zoho Books when the scope says the step is shared. Zoho Creator app development in New Zealand uses Deluge for those rules, and it uses the form builder for the record itself. Low-code app development in New Zealand means the app lives in the same Zoho account as the other apps, so the team opens it there. Custom functions are development, named in the scope. Support covers a function when the proposal says it is included.
What you hold at handover
A Zoho Creator consultant scopes the app before the build, and a Zoho Creator developer in New Zealand writes the smallest version that runs.
-
The record, named
What the app tracks, who creates it, and when it is finished. A fuzzy sentence means the work is still consulting , and Arcus will say so before quoting a build.
-
A boundary with CRM and Books
Customers and invoices stay where sales and finance already work. Creator holds the step those apps need to see, and the finance file remains the ledger.
-
The smallest app that runs
Forms, permissions, and the one report people will open. Further automation waits until people use the first version. A health check is the way in when someone else already built the app.
-
The script, where the form needs it
Deluge carries the rule the form builder leaves unspoken. The scope lists each function. The people who use the app learn the form, and they learn which steps the script performs.
-
A path for a later change
How a Creator build runs
02
Decide what stays in CRM or Books
Customers and invoices usually stay put. Creator holds the operational step, and a shared field is named in the scope when both sides must see it. A setup package is a different offer, for a clean standard app rather than a custom record.
03
Hand the smallest app over
Build the forms, the permissions, and the one report, then teach the users as part of the scope. Further changes go through support or a new quote, as the proposal stated before the first form was built.
A workbook beside an app you can hand over
The workbook between two Zoho apps is the usual reason to call a Zoho Creator developer in New Zealand.
| Aspect | Workbook | Creator app |
|---|---|---|
| The record | A sheet between two systems, owned by one person. | An app with an owner, and a point at which the record is finished. |
| Customers and invoices | Copied so that everything sits in one place. | Left in CRM and Books, where sales and finance already work. |
| The first version | Extra portals, because the product offers them. | The forms, the permissions, and the one report. |
| Later edits | Assumed to ride along because the app exists. | Support, or a new quote, named before the build starts. |
Who builds the app
Arcus is New Zealand-based, working with businesses worldwide. The build is remote unless a scope says otherwise. Which Zoho One edition includes Creator is a Zoho licensing question, and the subscription invoice comes from Zoho. Arcus quotes the app. The two documents stay apart.
Questions before a Creator scope
Do you write Deluge?
Yes, where the app needs a rule the form builder leaves unspoken. Deluge is the scripting language for that rule: a calculation, a permission, or a related record when a form is saved. Custom functions are scoped as development and listed before the build. A support arrangement covers them when the proposal says they are included. The handover shows the users what the script does, in the same language as the form they fill in.
Can you extend an app someone else built?
Yes, after a health check or a short review of how the app is put together. Seeing the existing forms, permissions, and Deluge is the basis of the quote. A quote made from a description alone misses the rules already in the script. The review says what can be extended and what should be left as it is. The extension, if you want it, is its own written scope.
Is Creator included with Zoho One?
Creator sits in the Zoho range a business buys from Zoho. Which edition includes it is a licensing question, answered on the subscription Zoho shows you, and this page leaves that label to that screen. The subscription invoice comes from Zoho. Arcus bills the build. If you are choosing the suite and the app together, the Zoho One page is where the short list is decided, and this page is where the record is specified.
Will the app become our accounts system?
Customers and invoices stay in Zoho CRM and Zoho Books unless a written scope says one specific step must be visible to both. Creator is the home for the operational record, such as the inspection or the job sheet, and the finance file remains the place the business closes. A second ledger would split the close. The scope draws that line before the first form is built, and the handover repeats it.
What do we receive at handover?
You receive the app, the named record, the permissions, the one report, and time with the people who will use it. The scope is the list of what that first version contains. Deluge functions included in the build are part of the same handover, explained as behaviour rather than as a code dump. Later changes are support or a new quote. The path for that later work is written before the project ends.
When is this still consulting, rather than a build?
It is still consulting when you can describe the pain and the record sentence is still fuzzy. Consulting ends in a recommendation you can refuse, including a recommendation to keep the step in CRM or Books. A Creator build starts once the record, the people, and the finished state are specific enough to quote. The two engagements are separate documents. One can follow the other, and neither one silently includes the other.
Brief a Zoho Creator developer in New Zealand
Tell us what the app tracks and who touches it. The reply says whether Creator is the right place. If it is, the next document is a written project scope in NZD. Zoho Flow can send a Creator record to Zoho CRM or Zoho Books. Zoho Analytics reads the records the app stores. Blueprint remains the CRM stage rule, separate from the form.