Notes from the studio
30 articles on the products we build and how we think about software for faith, community and business.
Designing church software pastors actually want to use
Most church management software renames a customer table and calls it done. Here's what changes when you start from Sunday morning instead of the database schema.
TheRehoboth EngineeringWhy we build offline-first for African users
Spinners that never resolve, uploads that silently drop — most apps quietly fail on the connections our users actually have. Here's how we design around that.
AIWhat we learned giving AI agents a WhatsApp inbox
A good AI reply isn't the hard part — knowing when not to send one is. Here's how 247BrandHQ's AI Agents decide when to escalate to a human.
247BrandHQ ProductWhy 50,000 people trust Koinonia with their daily devotion
Fifty thousand people opening an app for a few quiet minutes a day is a bigger responsibility than the download number suggests.
Koinonia BusinessWhat we look at before saying yes to a new product idea
A good idea is not the same as a good product for us to build. Here is the filter every new idea has to survive first.
ProductWhy attendance tracking is the most underrated church feature
Giving and livestreaming get the demo time. Attendance tracking is the feature that actually keeps people from falling through the cracks.
TheRehoboth ProductReading plans that actually get finished
A missed reminder shouldn't reset a reading plan or shame someone with a broken streak. It should just prompt them to continue from where they are.
Edify — Books & Audio ProductRetelling Bible stories without losing the original message
A story has to work without a listener being able to pause and reread a sentence they missed. That constraint changes how a narrative has to build.
Edify — Audio Bible & Stories ProductOne post, four platforms: the case for a single composer
WhatsApp isn't a feed — it's a conversation. Here's why 247BrandHQ didn't force every platform into one identical composer.
247BrandHQ EngineeringWhat "ready to deploy in days" actually means
A custom-built church app means custom bugs for every church. A shared, proven foundation means a new deployment inherits years of fixes on day one.
MyChurchApp PRO DesignTen Bible versions, one reading experience
Switching Bible translations shouldn't feel like opening a different app. Here's how Koinonia keeps ten versions consistent.
Koinonia EngineeringChoosing Flutter for six different products
One codebase, two platforms, and a UI toolkit fast enough to stay smooth on the mid-range Android devices most of our users actually carry.
EngineeringHow TheRehoboth handles multi-branch churches without the chaos
Leadership wants one view across every branch. Each branch wants to run its own week. Most software gets one of those needs wrong.
TheRehoboth AIWhy we added Ask AI to a Christian reading app
Ask AI stays inside the reading experience — built for comprehension and reflection, not for replacing the source material or generating new theology.
Edify — Books & Audio ProductBuilding a Readers Circle inside a listening app
No follower counts, no algorithmic feed. The Readers Circle exists to add community to a private habit, not to compete for attention.
Edify — Audio Bible & Stories ProductWhy we built a unified inbox before we built analytics
A missed message costs a business a sale today. A missing chart costs them a slightly less informed decision next week.
247BrandHQ BusinessNo monthly fees: rethinking how church software gets priced
Software pricing isn't just a business model decision. For a church app, it's also a statement about who the pricing is really designed for.
MyChurchApp PRO EngineeringDesigning an audio player for sermons, not songs
Losing your place in a 45-minute message is far more disruptive than losing your place in a playlist. Here's how the player is built around that.
Koinonia EngineeringWhy NestJS runs behind every backend we build
The biggest backend risk for a small studio isn't picking the "best" framework in the abstract — it's picking one inconsistently across six services.
ProductFrom spreadsheet to system: moving a church's records online
Nobody wants to spend a weekend retyping years of membership records — so onboarding is built around trust, not a dramatic cutover.
TheRehoboth DesignAudio chapters vs. audiobooks: a design distinction that matters
An audiobook assumes a continuous session, start to finish. Edify's audio chapters assume something more fragmented — and that changed how the player works.
Edify — Books & Audio DesignWhy we separated Ancient Faith Stories from Scripture
A listener should never have to guess whether what they're hearing is Scripture, a retelling, or historical storytelling. The app tells them upfront, every time.
Edify — Audio Bible & Stories AIHow AI Autopilot decides when not to post
The AI fills the calendar. A human still approves what actually reaches an audience — and that review step is deliberately not optional.
247BrandHQ EngineeringLivestream, radio and sermons in one player
From a member's perspective, the distinction between a livestream and a sermon recording often doesn't matter. So the player doesn't force them to care.
MyChurchApp PRO ProductWhat makes a 4,000-message sermon library worth using
Size alone isn't a feature. Here's how Koinonia keeps a 4,000-message library from becoming a wall of content nobody can navigate.
Koinonia ProductWhat "ship and support" means after launch day
Launch day gets the announcement. Everything that happens after is the actual commitment, and it's the part we take more seriously.
BusinessBuilding trust into every giving transaction
A member unsure their offering was recorded correctly will quietly go back to paper. Giving software earns trust through boring reliability.
TheRehoboth BusinessGems, membership and the economics of a reading app
Gems let a reader unlock exactly what they want, when they want it — instead of committing to a subscription for content they might use once.
Edify — Books & Audio BusinessWhat agencies actually need from a social media tool
Agencies weren't asking for more features. They were asking for genuine separation between client accounts — not a shared workspace with permissions bolted on.
247BrandHQ DesignPlaylists and bookmarks: small features, daily habits
A bookmark isn't just a saved link — it's how someone returns to a message that spoke to them weeks later. Small features, real daily weight.
Koinonia