CASE STUDY

Reimagining Leadership Reporting with AI.

Built in under 30 days.
Industry: AdTech / SaaS
Organisation Size: 235 Employees
Geography: Southeast Asia, Global Operations
My Role: Senior Manager, Process Excellence and Transformation
Engagement Type: Internal Transformation, AI Deployment
THE CASE
PROBLEM

The leadership team of a fast-growing AdTech organisation was operating without a reliable reporting infrastructure. Every week, department heads compiled their Progress, Plans and Problems manually. Updates were typed into spreadsheets, narrated in weekly meetings, discussed, then updated again after the retrospective. The cycle was repetitive, time-consuming and produced information that was already outdated by the time it reached the CEO.

There was no single source of truth. Data lived in inboxes, chat threads and individual files. Leadership was spending more time collecting information than acting on it.

IMPACT

Across 235 employees, the manual reporting cycle consumed approximately two hours per person per week. That is over 24,000 hours of organisational capacity lost annually to an administrative process that added no analytical value. Senior leaders were making decisions based on fragmented, manually compiled data with no consistent structure or timing.

The cost was not just operational. The absence of real time visibility meant that problems surfaced late, escalations were reactive and strategic alignment across departments was inconsistent.

APPROACH

The requirement came directly from the CEO and Chief of Staff. Weekly reporting was consuming the organisation and producing information that was already stale by the time it reached leadership. The question was not whether to fix it. It was how.

Existing systems were evaluated first. The organisation already operated on the Zoho ecosystem. Each application was assessed against the reporting requirement. None could fulfil it without significant customisation that would still fall short of what was needed. The decision to build a custom solution was made on that basis.

The design brief was defined with the CEO and CoS: automate the collection, synthesis and presentation of weekly Progress, Plans and Problems across all departments, and deliver a structured dashboard that leadership could access in real time. No unnecessary features. No external vendor. No expensive licensing.

The build was owned and delivered as a solo engagement. Architectural guidance was sought from three members of the Engineering and Product teams at the outset. The development itself was done independently. The prototype was built in Google AI Studio to validate the concept with the CEO. Once approved, the build was moved to Claude and completed. IT Infrastructure deployed the system to production.

The platform was built on a full-stack architecture. React and TypeScript on the frontend, Node.js on the backend, MongoDB Atlas as the database, and Google Gemini as the AI engine. Integrations were built across Gmail, Google Calendar, and the Zoho ecosystem. The system was deployed on Kubernetes with GitLab CI/CD pipelines and hosted on AWS CloudFront and S3. The architecture was deliberately kept lightweight so the platform could be built, deployed and operated without introducing a new enterprise software dependency.

The entire build took 30 days. Total development cost: under USD 20.

OUTCOME
What this engagement delivered:
30 Days
Time to Build
USD 20
Total Development Cost
<USD 20
Monthly Operating Cost
10,400 hrs
Annual Hours Saved
101
Active Users
What this would have cost with an external partner:
USD 8,000 to USD 15,000
Freelance Developer Equivalent
USD 25,000+
Agency Equivalent
USD 1,000 to USD 3,000
Annual Maintenance Retainer Avoided
What changed for the organisation:
Single source of truth for leadership.
Reporting runs in the background, not in meeting rooms.
Weekly reporting hours redirected to actual work.
Leadership sees live data. No more chasing updates.
Faster decisions, earlier escalations.
Strategic alignment visible across departments.
LEARNING

What this engagement confirmed.

The best solution is rarely the most expensive one. Enterprise tools exist for enterprise problems. A focused, well-scoped custom build will outperform a bloated platform every time when the problem is specific enough.
Adoption is the real measure of success. A tool that nobody uses has no value regardless of how well it was built. Designing for the CEO's actual workflow, not an idealised version of it, was what drove consistent weekly usage from day one.
AI is most powerful when deployed against a well-defined problem. The reporting gap at this organisation was clear, measurable and bounded. That clarity is what made a 30-day build possible. Organisations that deploy AI without that clarity rarely see the outcomes they expected.