Case Study
Symphonia is a complete platform for running an Orthodox parish. We designed and engineered it end to end, built it on the liturgical year, and it is live with parishes today.
The Parish Studio, our back office for the parish: a parishioner directory, one of a dozen areas built on the same shell.
Overview
A parish carries a public website, a weekly bulletin, a membership roll, a giving program, and a sacramental archive meant to outlast everyone in the building. We built Symphonia to hold all of it in one place, shaped by the Orthodox calendar and owned by the parish outright.
We led the work from first strategy through design and engineering, and we tend it now on a steady release cadence. It is the first work of the studio, and it is in daily use.
- Year
- Since 2025
- Category
- Parish platform
- Role
- Design & engineering
- For
- Orthodox parishes
- Stack
- SvelteKit · PostgreSQL · TypeScript
- Status
- Live
- Site
- symphonia.church →
- Client
- Orthodox parishes
- What we did
- Strategy, design, engineering, ongoing care
- Year
- Since 2025
- Status
- Live
The challenge.
A parish is one of the most demanding small organizations there is. It runs a public website, a weekly bulletin, a membership roll, a giving program, a sacramental archive meant to outlast everyone in the building, and a calendar unlike anyone else’s. Most parishes run all of it on the unpaid evenings of one or two people.
The available tools were built for a different world. General church-management software has no concept of the fast, the tone of the week, or the difference between a name-day and a feast, and it treats the calendar as a flat list of events rather than the frame of the year. So parishes assemble a website builder, a spreadsheet of sacraments, a separate donation processor, and a group chat: five systems that do not speak to each other, held together in one volunteer’s memory.
That patchwork is fragile. Records a community is supposed to keep for a century sit in a file only one person understands, and the day that person steps back, the parish loses its own memory. What they needed was a single system, built for the actual life of a parish, that a volunteer could learn quickly and the parish could own completely.
A parish keeps records meant to outlast everyone in the building. Its software should be built to the same standard.
Our approach.
We started by learning the domain from the inside, and we built Symphonia on the Orthodox calendar from the first line of code. It knows the old reckoning and the new, the moveable feasts and the fixed, the fasts and their dispensations, and the saints of the day. That knowledge is a layer the rest of the product reads from, so the bulletin prints the right commemorations, the website shows the coming feast with no one updating it, and the readings for the day are simply there.
We designed for the people who actually run a parish. Most parish administrators are volunteers, often older, often wary of software that assumes a fluency they never claimed. So the interface is calm and legible on purpose: warm paper tones, a real reading serif, one restrained accent, and generous space. Nothing blinks for attention. And because the work does not stay at a desk, every part of Symphonia is a real surface on a phone, installable to the home screen, so a priest can look up a parishioner or check the day’s feast from the parking lot.
Then we built the whole system rather than a demonstration of it. One database and one login, and a place a new volunteer can be shown in an afternoon. The parish owns its data and can export everything at any time, so leaving is always a door, never a trap.
The liturgical day, with feast, tone, fast, and readings, read automatically by the bulletin and the parish website.
What we built.
On that foundation sits the working life of a parish.
The website
A public parish site the office keeps current without a webmaster: service times, the coming feast, news, and ministries, all drawn from the liturgical calendar.
The bulletin
The weekly bulletin, composed from templates that pull the day's commemorations and announcements from the same data, so it goes out on time every week.
Sacramental records
Baptisms, chrismations, marriages, and funerals kept as a permanent, searchable register, the archive a parish holds for generations, with the reports the diocese asks for.
The pastoral spine
One record from first visit to full membership. Visitor, inquirer, catechumen, and communicant run as a single thread, with catechism tracked and reception filing baptism and godparent bonds in one step.
Stewardship & giving
Pledges, recurring gifts, and capital campaigns, with statements that reconcile and a giving history that lives beside the member instead of in a separate system.
The directory, done right
Households, roles, and access decided by the parish, with real privacy controls, because a church holds a deeper trust than most businesses ever will.
Communications
Parish-wide email with delivery tracking, so an announcement that has to reach everyone actually does.
The Works suite
For parishes that want it, a full workspace of shared drive, documents, forms, and tasks on the same login, so the office stays in one place.
The outcome.
Symphonia is live with parishes today and improving on a steady release cadence. The results that matter to a parish office are the plain ones: less time lost to administration, and a record the community can trust. We are gathering the numbers as parishes settle in, and we will report them here honestly.