Project Manager / Business Analyst
Your single point of contact. Owns requirements, planning, milestones and communication throughout.
How we work
From kickoff to go-live, and after.
One accountable team covers requirements, build, integrations, testing and support. Here is exactly who you deal with, what you receive, and where the boundaries sit.
The journey
From handover to closure, in four phases.
A standard setup is typically live in two to four weeks. A custom build runs four to twenty. Either way the path is the same.
-
01
Understand
- Project opened from the sales handover
- Lead Engineer assigned, requirements gathered
- Understanding Document prepared and confirmed with you
-
02
Agree
- Statement of Work drafted from the agreed requirements
- Scope, deliverables, timeline and terms set out
- Your approval before anything is built
-
03
Build
- Onboarding meeting and workspace access
- Plan, approach and milestones agreed
- Development on a weekly cadence, with test cases per milestone
-
04
Confirm
- User acceptance testing with you at every milestone
- Milestone signed off, then the next one begins
- Go-live, training, and thirty days of support
Phases three and four repeat for each milestone until the project closes. Timings are confirmed at scope sign-off.
Rhythm
Every milestone follows the same three beats.
So you always know where the work stands, and what has been accepted.
We build
The team develops and completes the deliverables agreed for that milestone.
You review
We share the test cases and run acceptance testing with you. You validate and confirm.
Signed off
On your confirmation the milestone is complete, and the next one begins.
Your team
Who you will work with.
Every project gets a dedicated team, led by one point of contact who owns it end to end. You are never bounced between vendors.
Lead Engineer
Leads feasibility, solution design and technical delivery for your implementation.
Solution Engineer
Builds, configures, integrates and tests your Zoho environment.
Transparency
The paper trail you get.
Seven documents run alongside every project, shared with you and kept current as the work moves. Nothing about your implementation should live only in our heads.
01Feasibility Document
02Understanding Document
03Statement of Work
04Solution Architecture
05Milestone Plan
06UAT Test Reports
07Sign-off Document
Every meeting has an agenda
Objectives shared beforehand, topics tied to project priorities, and action items captured with owners and due dates.
Minutes sent after every meeting
A summary, the decisions taken, and action items with owners and timelines — by email, every time.
Your workspace
You get access, not status reports.
At onboarding you are given direct access to the same places we work in — one to track progress, one to reach us in real time, one for every document.
Zoho Projects
Milestones, task progress, timelines and deliverables — visible to you, not summarised for you. Raise an issue directly.
Zoho Cliq
A channel straight to the people building your system. Questions answered in hours, not through a ticket queue.
Zoho WorkDrive
Every document, version-controlled and in one place: implementation artifacts, meeting notes, the lot.
Working together
What we will need from you.
Four things. None of them are heavy — they just need to be someone's job.
A single point of contact
One person who can consolidate feedback from your side and decide when opinions differ.
Reviews and approvals
The Understanding Document, the Statement of Work and each milestone, turned around in the agreed window.
Access and data
Systems, environments and credentials, plus master and test data in a usable format — and someone who can vouch for its accuracy.
People for testing
Key users with time set aside to test each milestone properly, and consolidated feedback rather than scattered notes.
Beyond go-live
We do not disappear at launch.
Go-live is the start of the first month, not the end of the project.
01
Go-live
Your solution is deployed into production, with knowledge transfer to the support team completed first.
02
Training
Role-based sessions walking your team through the system and workflows, with time for questions.
03
Hypercare, 30 days
We stay on hand through early adoption, fixing defects and configuration issues as they surface.
Tell us what you need Zoho to do.
Describe the problem and we will come back with a ballpark scope and timeline.