How Cirro Hands Over Your Zoho System

How does Cirro hand over the system to our team?

At handover you get four things: full administrator control of your Zoho account, written documentation of what was built and why, a record of the requirements it was built against, and a working session with whoever will look after the system day to day. Everything is in your name from the start, so nothing about running your system depends on us staying involved.

The account is yours, not ours

Your Zoho account is registered to your company and administered by your people. We work inside it as invited users. At handover our access is removed or reduced to whatever your support arrangement needs. You are never in a position where you have to ask us for permission to change your own system.

Documentation you can actually read

You get a written description of how the system is set up: what the main parts do, how the automation behaves, and what connects to what. It is written for the person who will run the system, not for a developer.

Why we write down the reasoning too

Documentation that only lists settings goes stale the moment someone changes something. We also record why each decision was made, so that in a year, when someone asks whether a rule can be turned off, the answer is in writing rather than in somebody's memory. This is the part most handovers skip and the part you will miss most.

The working session

Whoever is going to administer the system sits with us and walks through it: where things are configured, what is safe to change, what to leave alone, and how to spot a problem early. It is a conversation with questions, not a presentation.

If nobody internal can administer it

Plenty of smaller teams do not have anyone who wants this job, and that is fine. In that case we hold the administrator role under a support arrangement, but the account stays in your name and the documentation still comes to you. The point is that you always have the option to take it back.

What this means for you

You should finish a project able to run your own system, or able to hand it to another partner without a rebuild. If a partner cannot hand over cleanly, you are not buying a system, you are buying a dependency.

Next step

See what support looks like after handover: What ongoing support options exist after the project ends?

Related articles