Entry 01 · Plan
Discovery call
Goals, current tools, the date we’re racing.
What should you expect from a Zoho implementation overall?
Expect a planned project with clear sign-off points, not a software install. With us it runs in four phases and twelve steps: plan, set up, build, launch. You sign two things before any build starts, the BRD and the delivery schedule, so there are no surprises about scope, price or dates.
Zoho apps are quick to switch on. Anyone can create a Zoho CRM account in an afternoon. What takes thought is making the software match the way your business actually sells, bills, hires or supports customers, and getting people to use it. That is what an implementation partner is for, and it is why most of the effort sits in the first and last phases rather than in the build.
Our full process, with every step and who takes part, lives on the How we work page. This article is the companion piece: what each phase feels like for you, what we will ask from your team, and where people usually get caught out.
Phase 1: what happens while the project is being planned?
We learn how your business works, turn that into a written scope, and agree a fixed price for it. You finish this phase holding a signed BRD (business requirements document) that says exactly what will be built and how each piece will be checked.
Steps 01 to 04
- What you do
- Join a free discovery call, then free up department heads, plus two or three people who do the daily work, for mapping sessions. Read the BRD properly and push back where it is wrong.
- What we do
- Run the sessions, draw the process maps in your team’s own words, list the Zoho apps, integrations and data imports in scope, and price the work.
- You walk away with
- Process maps per department, a scope summary with license costs at Zoho’s list price, and the signed BRD with our fee fixed inside it.
The mapping sessions are where good projects are won. We trace how a lead becomes a customer, how an order becomes an invoice, or how a candidate becomes an employee, and we note every spreadsheet that plugs a gap. People are often surprised by how much of their week turns out to be copying data between tools. Those notes become the requirements.
Then comes the BRD. It lists the fields, automations, reports, integrations and imports, plus the test each one must pass. Each department head approves their section and the project owner signs the whole document. It can feel formal for a team of twenty. It is also the single best protection you have: if something is in the BRD, it gets built at the agreed price, and if it is not, adding it is a conversation rather than an argument.
Smaller projects are often scoped straight from the first call. Larger ones, with several departments or heavy data, may need a paid scoping phase before the BRD. If yours does, we will tell you and quote it before it begins. Our article on Zoho implementation cost explains what moves that number.
Phase 2: what does the set-up phase involve?
A kick-off meeting, a dated delivery schedule covering each module and connection, and a sprint plan that pairs each piece of work with a reviewer on your side. It is short, and it decides how smoothly the build goes.
Steps 05 to 07
- What you do
- Name a project owner and a reviewer per department. Hand over admin access to the tools we will connect. Check the schedule against holidays, busy seasons and staff leave.
- What we do
- Draft the schedule, set up the communication plan, and split the work into short sprints.
- You walk away with
- A contact sheet, a schedule you can hold us to, and a sprint list showing who checks what.
The most common mistake at this stage is picking a reviewer who is too busy to review. If your sales manager is on the road four days a week, choose someone who will actually open the demo link. A good reviewer answers questions within a day or two, because a question left hanging on our side becomes a delay on yours.
Phase 3: what happens during the build?
Our consultants configure Zoho, write any custom functions and build the integrations, and every week or two we show you finished work inside your own account. Changes are collected while they are still small, and testing ends with each department signing off its area.
Steps 08 to 10
- What you do
- Attend the review demos, click around between them, and send feedback quickly. In testing, your users run their normal daily tasks against the checks written in the BRD.
- What we do
- Build in sprints, demo, adjust, run our own QA first, and start writing user guides and recording short walkthroughs while each feature is fresh.
- You walk away with
- Demo notes after each review and a signed test sign-off per department.
The review demos are the moment your team first sees its own data and its own process in Zoho CRM, Zoho Books or whichever apps are in scope. Expect a list of small changes after each one. That is healthy. A button label, a missing filter, a field that should be required: catching these in week three is cheap, catching them after go-live is annoying for everyone.
Testing is deliberately done by the people who will use the system. Our QA checks that things work; your team checks that they work for the job. When a department head signs the test sign-off, they are confirming their area does what the BRD promised.
Phase 4: what happens at go-live?
Training by department, then the switch-on, then a period of close watching while real use turns up the last rough edges. Training is included in the project, and you get manuals and recorded videos your future hires can use.
Steps 11 and 12
- What you do
- Block time for training sessions, grouped by role. Agree a go-live date that avoids month-end close or your busiest week.
- What we do
- Teach role-based sessions in person around Southern California or by video call elsewhere, work through the go-live checklist and stay close through the first weeks.
- You walk away with
- A live system, trained users, the manuals and videos, and a named support contact.
Most go-live trouble is not technical. It is someone still keeping their old spreadsheet “just in case”. Decide with your managers, before launch, which old files and tools are retired on day one. We can make the old tool read-only if it helps the habit change.
What happens after go-live?
Support continues, and the next round of improvements gets planned from what your team learned in real use. Many clients add a second or third Zoho app once the first one is settled.
A few weeks in, your team will know what they want next: a dashboard for the owner, an approval step in purchasing, a link between Zoho One apps that were set up separately. We scope those the same way, smaller, with their own BRD. Moving off another system instead of starting fresh? The Switch to Zoho pages and the migration track on How we work cover the extra steps a move needs.
