MyCelulas emerged from a real operational need in Alejandro's local church: bring fragmented information, leadership workflows and growth reporting into one product.
PROBLEM / CHALLENGE
What needed solving.
The product had to support multiple organizations and users while keeping structure, reporting and access levels understandable for people who are not technical.
SOLUTION
What I built.
A responsive, multilingual SaaS interface for organization, cell and user management, with dashboards, growth reports, leadership workflows and subscription plans.
ENGINEERING DECISIONS
Intentional choices over complexity.
01
Server-rendered PHP
PHP keeps the product straightforward to deploy and lets the interface render close to the data and business rules.
02
Permissions as a product concern
Different users need different access levels, so authorization is part of the application model rather than an afterthought in the interface.
03
Built for iteration
The system has evolved with feedback from real users, which makes clear boundaries and maintainable data relationships more valuable than unnecessary complexity.
LESSONS FROM PRODUCTION
What real usage teaches.
Building a growing product teaches lessons that a tutorial cannot: permissions need to be legible, data structures have to evolve safely and production feedback should shape the next technical decision.
Next project
Current technical priorities include increasing automated test coverage, refining application boundaries and improving deployment automation.
