A Zoho case study in NZ names the client, the apps delivered, and figures that client has approved.
Story standard
No approved figures are published here yet. Results that NZ businesses get from Zoho appear on this page only as figures a named client has approved.
Arcus is New Zealand-based, working with businesses worldwide. Zoho implementation results are those approved figures, tied to apps that were actually delivered, with a sentence in the client's words. A Zoho CRM case study New Zealand would name the pipeline and the records that moved. A Zoho One case study in NZ would name the short list of apps that went live. Each of those waits for a client who approves the draft.
Miss one part and the piece stays a note, rather than a Zoho case study in NZ. Arcus drafts the five parts from finished work. The client approves them before anything is public.
A few sentences plus the figures the client has approved, because an estimated number prepared for the page fails the standard. The approved figures are the numbers a story carries, and they are the figures that client has already signed off.
Who the client is, the sector, and the situation they were working under, with the detail taken from that engagement. A borrowed industry benchmark stays out of the draft, because the constraint has to belong to this client.
The Zoho apps, the connections, and any migration that were actually delivered. Zoho CRM, Zoho Books, Zoho Creator, and Zoho One are named only when that app was part of the delivery. Zoho Flow is named when it moved a record between those apps. Zoho Analytics is named when a report read the records they store. Blueprint is named when it held a Zoho CRM stage until the required fields were filled. A conversation about an app stays a conversation.
The result is in the client's figures, and hours, money, or volume qualify when that client has approved the number and the wording around it. Zoho implementation results live in this part of the draft, beside the sentence below.
Words from a named person, as they approved them, kept in the client's words rather than rewritten for the page. The client sees the whole draft, including this line, before it is public.
The story follows four labelled steps, and it waits until all four are true. The work finishes, the client agrees to be named, the client approves the figures and the sentence, and the five parts go up together. Dates stay in the proposal. Being named is a choice after the work, separate from the scope you hire Arcus under. The pricing page covers that commercial document, and this page covers the story.
A real engagement has been delivered, while a sketch of work Arcus might do is a sales note and stays off this page. The consulting page is where a new brief starts. Support appears in a story only when that support was part of the delivered work.
The business is identified because the client agreed, and an anonymous composite is a different kind of writing from the named account this page is for.
Figures and the sentence both need approval, because a rewritten sentence fails the standard and unapproved figures fail it too. You see the draft first, and if the name, the figures, or the sentence are off, the story stays in draft.
They are tied to the service that was delivered. The about page describes the company, and this page describes one finished job once the client has approved it. The home page is where a buyer starts when they are still choosing a consultant rather than reading a finished job.
A Zoho CRM case study New Zealand would include the pipeline that was configured, the stages and fields that went live, and the records that moved. Blueprint, if it was part of the delivery, would be named as the gate on a stage. A discussion that stayed on a call stays in the notes, and it is recorded as a conversation rather than as delivered work.
A Zoho One case study in NZ would name the short list of apps that were switched on, and the work those apps took over. Included in the licence and needed by the team are different things, and the story would say which apps went live. The Zoho One page explains that short list for buyers who are still choosing.
A Books story would name the file that finance closes, the import that was run, and the trial balance the opening figures came from. Creator would name the form, the permission, and the report that were handed over. Those paragraphs are the bar a matching story has to clear, and they become a client story when a named client approves one. These pages are also gathered on the solutions index.
A Zoho case study in NZ names the client, the Zoho apps that were delivered, the figures that client has approved, and a sentence that same client has approved. Arcus drafts those parts from finished work. The client sees the draft and approves the name, the figures, and the sentence. The page then shows those approved parts. Anything still awaiting approval stays in the draft.
A Zoho CRM case study New Zealand would include the pipeline that was configured, the stages and fields that went live, and the records that moved, plus figures the client approved. It would name Zoho CRM as delivered work. A discussion that stayed on a call, with the build still ahead, stays off the page. The CRM page explains the product, and this page waits for a named delivery.
A Zoho One case study in NZ would name the short list of apps that were switched on, and the work those apps took over, with figures the client approved. The story would say which apps went live, because included in the licence and needed by the team are different things. The Zoho One page explains that short list. This standard asks for the delivered list.
Zoho implementation results are the figures a named client has approved, tied to work Arcus delivered. Hours, money, and volume qualify when that client has approved the number and the wording around it. An estimate prepared so the page looks full fails this standard. The story also needs the client's sentence, in the words they approved, beside those figures.
A client can ask once the engagement is finished and they are willing to be named. Arcus replies by email with a draft of the five parts. The client approves the name, the figures, and the sentence before anything is public. Being named is a choice after the work. Hiring Arcus stands on the scope, and a story is separate from that agreement.
This page explains the standard so a reader knows what a future Zoho case study in NZ will contain. Arcus publishes a story after the client approves the draft. The five parts are the short version, the business and the constraint, the setup, the change in the work, and the client's sentence. Each part has to be true of one finished engagement.
Enquire. Arcus replies by email with a draft of the five parts. The page changes when you approve the name, the figures, and the sentence. A published story would name the apps in that work, such as Zoho CRM, Zoho Books, Zoho Creator, or Zoho One, and whether Zoho Flow, Zoho Analytics, or Blueprint was in the scope.