case study

From scattered spreadsheets to an auditable data pipeline for a multi-country NGO

A multi-country NGO was running its operations on Google Sheets and Excel files held in individual staff accounts. I replaced that with a single, governed pipeline that management can audit end to end and analysts can report on directly.

stack:
zoho forms, zoho crm, zoho flow, supabase, postgres
reporting:
power bi, tableau
client:
international ngo, multi-country (name withheld for confidentiality)

The problem

before

  • Data lived in many Google Sheets and Excel files, spread across individual staff accounts.
  • No single owner, no consistent structure, and no reliable record of who changed what.
  • When staff left, access to their files and the data in them often left with them.
  • Management could not audit how data moved from the field to a donor report.

after

  • Every record is captured through one standard set of Zoho Forms.
  • Zoho CRM is the single operational system, owned by the organization, not individuals.
  • Zoho Flow runs the rules, checks, retries, and routing between systems.
  • A Supabase relational database holds a clean, governed copy for reporting.

How data moves

field entry → donor report, one traceable path

  1. 01

    Capture

    Zoho Forms

    • Required fields
    • Controlled picklists
    • Validation at entry

    ↳ validated submission

  2. 02

    Operate

    Zoho CRM

    • Org-owned records
    • Defined modules
    • Audit trail

    ↳ record events

  3. 03

    Orchestrate

    Zoho Flow

    • Business rules
    • Checks and routing
    • Automatic retries

    ↳ relational sync

  4. 04

    Govern

    Supabase / Postgres

    • Normalized schema
    • Foreign keys and constraints
    • Row-level security

    ↳ direct query

  5. 05

    Report

    Power BI / Tableau

    • Reads relationships
    • No manual exports
    • One version of truth

The build

01

Capture: Zoho Forms

I replaced ad hoc sheets with a unified collection of Zoho Forms. Each form maps to a defined record type, with required fields, controlled picklists, and validation at the point of entry. Field staff submit data the same way regardless of office, and management can trace every record back to the form, person, and time it came from.

02

Operate: Zoho CRM

Form submissions land in Zoho CRM, which became the organization's single operational system. Modules and relationships were designed around how the programs actually run, so staff work in one place instead of hunting through personal files. Ownership sits with the organization, so data no longer disappears when people move on.

03

Orchestrate: Zoho Flow

Zoho Flow coordinates the movement of data between forms, CRM, and the database. It handles automations, business rules, validation checks, conditional routing, and retries when a step fails, so the pipeline recovers on its own instead of silently dropping records.

04

Govern: Supabase relational database

All Zoho CRM content feeds into a Supabase (Postgres) database built on a properly normalized relational schema. Primary keys, foreign keys, and constraints enforce strict data and referential integrity, so orphaned or inconsistent records cannot enter the reporting layer. Row-level security controls exactly who can see which rows.

05

Report: Power BI and Tableau

Because the schema is clean and explicit, tools like Power BI and Tableau can read the relationships directly. Analysts connect to the database and build reports without manual exports, copy-pasting, or reconciling conflicting spreadsheets.

The result

  • One owned source of truth instead of files scattered across personal accounts.
  • A traceable path from every form submission to every number in a report.
  • Integrity enforced by the database itself, not by someone checking spreadsheets.
  • Access controlled at the row level, so each team sees only what it should.
  • Power BI and Tableau read the schema directly, with no manual exports.

This is the kind of problem I solve.