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 shape of a project
Three phases, and what each leaves behind.
Six documents run alongside every project, each arriving at a known point. Hover or tap a phase to see what it produces.
Discovery using a standard questionnaire, then a scope and timeline you sign off. Nothing is built until that is agreed.
What you receive
- Feasibility & Understanding Document
- Statement of Work
- Milestone Plan
Every milestone runs the same three beats, so you always know where the work stands and what has been accepted.
We build
You review
Signed off
What you receive
- Solution Architecture
- UAT Test Reports
Go-live, training for your team on the system they will actually use, and thirty days of support as standard.
What you receive
- Sign-off Document
What it costs
You see the number before you commit.
The question everyone asks first, and the one most implementations answer with “it depends”. Here is where money actually enters ours.
Before discovery
The first sixteen hours are ours. Nothing is owed and nothing is signed. We ask what you run today and what is not working, and if Zoho is the wrong answer we will say so here rather than later.
At the end of discovery
A scope and a range you can take to a budget holder. Based on the standard questionnaire and what we found, not on a guess made before we looked.
At scope sign-off
The price is fixed against that scope. It is agreed before we build, so it is not discovered halfway through. Anything added later is scoped and quoted the same way, and you decide whether it goes ahead.
After go-live
Thirty days of support, included. Not an upsell. Cover beyond that is arranged separately, and only if you want it.
Throughout
Zoho licences are billed by Zoho. We quote the implementation on its own, so you can see exactly what you are paying us for.
We do not publish a day rate. The same number means very different things on a two-week setup and a twenty-week build, and a rate without a scope tells you nothing about what a project will cost.
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.
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 at the earliest, not parked in 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 at the start. None of them are heavy — they just need to be someone’s job rather than everyone’s.
01
A single point of contact
One person who can consolidate feedback from your side and decide when opinions differ.
02
Reviews and approvals
The Feasibility & Understanding Document, the Statement of Work and each milestone, turned around in the agreed window.
03
Access and data
Systems, environments and credentials, plus master and test data in a usable format — and someone who can vouch for its accuracy.
04
People for testing
Key users with time set aside to test each milestone properly, and consolidated feedback rather than scattered notes.
And after milestone planning: the tasks you own are put on the project board alongside ours, with dates against them. You can see them, and so can we.
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.