Case Study
Church operations were being coordinated across WhatsApp messages, spreadsheets, forms, and manual follow-ups, making it difficult for leadership to know what was happening across campuses and small groups without chasing people for updates. HovaSee was designed to replace that fragmented process with a single operational system where responsibilities, reports, attendance, people, and follow-up activities are connected. The goal was to turn recurring administrative processes into structured workflows that could be tracked from assignment through completion.
Contribution
I designed and engineered the platform architecture around a multi-campus, role-aware model, covering authentication, onboarding, organizational structure, reporting, small groups, workforce management, and visitor follow-up. I built workflows for Sunday attendance, first-timers, new converts, small-group attendance, outreach, and financial reporting, while designing the underlying infrastructure to support additional reporting domains without exposing unnecessary complexity in the MVP. I also built the visitor assimilation workflow from first-time registration through assignment, contact attempts, small-group invitation, integration, escalation, and loss, with automated assignment and rotation workflows for operational teams. Supabase/PostgreSQL provided the data layer, authentication, and security model, with Row-Level Security used to control access to church and operational data.
Outcome
A centralized operations platform that gives church leadership structured visibility into what is happening across people, campuses, small groups, reports, and follow-up activities. Instead of relying on disconnected messages and spreadsheets, leaders can work from defined responsibilities and measurable workflow states, while operational teams have a clear path from assignment to completion. The architecture also provides a foundation for automation and analytics, making it possible to measure follow-up effectiveness, completion rates, response times, escalations, and integration outcomes as the platform grows.