Workamajig to Zoho: A Structured Transformation
Why we had to act
Our project management system was no longer serving the evolving needs of our teams. It slowed us down, frustrated users, and lacked the adaptability modern teams demand. The mission: design and deliver a tool that helps teams collaborate smarter, work faster, and lead with clarity.
Daily time entry is the most frustrating part of my day.
— Design Team, User Sentiment SurveyFeedback like this — alongside "the dashboard gives no clear visibility" and "we end up avoiding WMJ for real collaboration" — made the case for change concrete, not theoretical.
Six interconnected gaps
Before proposing any changes, I ran structured interviews across the team. The friction wasn't isolated to one system complaint — it spanned six linked areas:
A 37-week, evidence-led transformation
- Weeks 1–3, Preparation: Identified core Workamajig challenges, defined success criteria, aligned leadership on goals.
- Weeks 4–9, Vendor Research: Shortlisted Monday.com, Zoho, Microsoft Planner, and ClickUp; narrowed to Monday.com and Zoho after internal feedback and needs assessment.
- Weeks 10–19, Pilot & Evaluation: A cross-functional pilot group — Account Management, Project Management, Design, and Finance — ran hands-on demos and testing, scored on usability, reporting, automation, and scalability.
- Weeks 20–40, Customisation & Go-Live: 4–5 months configuring Zoho Projects, CRM, and Books to match real workflows, with role-based dashboards and automation.
Zoho was selected through a collaborative, KPI-driven evaluation with real user input — not a top-down decision.
"Say Hello to Zoho" — the internal campaign
A platform switch fails or succeeds on adoption, not configuration. Starting one week before launch, I ran a structured, week-by-week communication campaign:
- Week 1 — Awareness: "Zoho is coming!" — why the change is happening and what to expect.
- Week 2 — Education & Engagement: Tool capabilities, early benefits, testimonials from the pilot group.
- Week 3 — Training & Support: Role-specific training sessions, SharePoint hub with tutorials and guides.
- Week 4 — Launch Plan: Confirmed launch date, final checklist — logins, sessions, who to contact for help.
Training was tailored by function — Project Managers, Account Managers, Designers, and Finance each had customised sessions — supported by detailed user manuals, FAQs, and step-by-step video tutorials. During launch week, Zoho representatives were onsite for real-time support, and the Operations team tracked every reported blocker for fast escalation and resolution.
To manage the risk of migrating legacy data, I chose a controlled overlap strategy: ongoing and critical projects were closed out in Workamajig, while new projects started fresh in Zoho — minimising data loss without an all-at-once cutover.
Results
Annual system cost dropped from roughly $36.8K to $14.6K — a 60% saving, for a platform with more modules, not fewer. The migration ran with full operational continuity — zero downtime, zero data loss — and a 7.8 out of 10 adoption satisfaction score, with user complaints reduced significantly compared to the legacy system. The transition also recorded the highest invoicing value the studio had seen, reflecting better-governed projects and a healthier delivery pipeline.
Standardising the Brand Studio's Way of Working
One studio, dozens of informal variations
A platform migration alone doesn't fix inconsistent ways of working — it just moves the inconsistency onto new software. Alongside the Zoho transition, I designed and documented a single, unified process flow covering every stage of studio work, from the moment a lead enters the system to final invoicing, with explicit turnaround times and named ownership at every step.
Lead Handling
TAT: 4-hour first response- Verify service scope fit
- Capture brief details
- Structured follow-up cadence (Day 3 → Day 30)
Opportunity Handling
TAT: 24hrs standard / 48hrs complex- Scope definition & estimate creation
- Proposal review and approval (BL/GM)
- Present proposal to customer
Project Handling
TAT: based on scope- Resource & schedule planning
- Self-QC + Creative Manager QC before delivery
- Customer acceptance & "First Time Right" tracking
Invoicing & Closure
TAT: 24hrs standard / 48hrs custom- Billing status check & invoice creation
- Discrepancy resolution
- SAP reconciliation & archive
Governance you can actually audit
Every stage above carries an explicit turnaround-time commitment and a named accountable role — Account Manager, Delivery Lead, Creative Manager, Business Controller, Business Lead, or General Manager — so escalation paths and ownership are never ambiguous. This was one of the 20+ SOPs built during the Atlas Copco engagement, and it's the operational backbone the Zoho platform was ultimately configured to run.
Scaling Enterprise Delivery Across 150–200 Concurrent Clients
Fragmented, reactive, inconsistent
- No centralized visibility into resource utilization, capacity, or allocation across projects
- No standardized process for coordinating with internal teams
- Presales operated reactively, with no structured, coordinated proposal process
- No standardized process for providing customers with project status updates
Rebuilding delivery governance from the ground up
- Established a standardized delivery governance framework
- Implemented centralized resource planning and utilization tracking
- Introduced standardized cross-functional coordination workflows
- Formalised accountability through RACI matrices, structured kick-off decks, and detailed project proposals
Results
Turnaround time dropped 20% without quality loss. Escalations stayed under 1% across 150+ concurrent enterprise clients — recognised twice with ValueLabs' Star of the Month award.
Curious about the work behind the results?
Interested in these case studies or curious about other transformation initiatives I've led?