It is the first question almost every client asks, and the answer most partners give is the least useful one available: it depends. It does depend. But the things it depends on are knowable, and you can work out roughly where you will land before anyone quotes you.
Two to four weeks, or four to twenty
We run projects in two shapes. A standard setup is standard Zoho apps configured for how you work, your data migrated, your team onboarded. That is typically live in two to four weeks. A custom build is Creator apps, portals and workflows, several Zoho products joined into one platform, and connections out to systems like SAP, Xero or telephony. Those run four to twenty weeks.
The gap between four and twenty is wide, and that is honest rather than evasive. A single Creator app with one integration sits near the bottom. A multi-product platform for three thousand licences, talking to an ERP nobody is allowed to modify, sits near the top.
What actually moves the number
Integrations move it most. Not because the code is hard, but because every integration involves a second system with its own owner, its own release schedule and its own opinion about giving you API access. A project with three integrations is not three times a project with one; it is three sets of other people's calendars.
Data comes second. Moving records out of spreadsheets or a legacy CRM is routine. Reconciling them, deciding which of four duplicate customer records is the real one, and getting someone to sign off on that — that is the part that slips.
Decisions come third, and they are usually the quietest risk. A build waits on an answer about approval limits or who owns a stage in the pipeline. Nobody logs it as a delay, but it is one.
How to get a real number earlier
We start discovery while you are still deciding. A member of our team works through a standard questionnaire and comes back with a ballpark scope and timeline before you have committed to anything. It is not a quote and we do not pretend it is, but it is close enough to plan around and honest enough to be worth having.
Then the project runs the same path either way: engage, deliver, launch. Intake and discovery, scope and sign-off. Build on a weekly cadence, with user acceptance testing against what you agreed. Go-live, training, and thirty days of support once you are running.
The question behind the question
When someone asks how long it takes, they usually mean something else: when can I stop thinking about this. The answer to that is not go-live date. It is whether the people who built the system are still reachable when something changes in year three.
Timings here are indicative and confirmed at scope sign-off. If you want a ballpark for something specific, describe it and we will come back within a working day.