OWNED PRODUCT · PRODUCTION
PatchGrid
A production SaaS born from a real live-event coordination problem and now used by dozens of users.
- Role
- Product & architecture owner
- Status
- Production SaaS
- Usage
- Dozens of users
- Stack
- .NET · React · CI/CD
The Problem
Church and outside-event work often requires exchanging console and show files between operators, vendors, and production teams. Files accumulate dates, version numbers, “final” suffixes, and local copies until it becomes unclear which version is authoritative.
Product Direction
PatchGrid turns that file handoff into an explicit workflow rather than relying on filenames and chat history. It also includes scheduled and real-time operational views used around live-production workflows.
Why it matters
This is not a portfolio-only application. The problem came from repeated real-world use, the service is deployed, and dozens of users have used it. Product decisions therefore have to account for compatibility, migration, deployment, and existing behavior.
Modernization
The system is being evolved toward a modern .NET and React architecture with stronger API boundaries, testing, CI/CD, observability, and clearer separation of responsibilities. Modernization is driven by maintainability and product needs rather than adding technologies for résumé keywords.
What this demonstrates
Problem discovery from domain experience, shipping and operating an owned product, evolving architecture under real-user constraints, and balancing engineering modernization with product continuity.