About
Folio exists so a church’s teaching keeps working.
Most churches preach more than they can use again. The sermon is recorded, uploaded, and watched once. Months later a pastor answers the same question someone else asked last year, because the teaching that answered it is buried in an hour of video.
Why we built it
A church’s teaching should stay within reach.
Folio brings a church’s recorded teaching into one place, turns it into notes and answers in the church’s own voice, and keeps a person in charge of what gets said in public.
A church already knows what it believes. It has said it, Sunday after Sunday, in sermons that carry the pastor’s voice and the church’s convictions. What is missing is a way to hold that teaching together and put it back to work without losing the church’s authority over it.
So Folio does two things. It makes the library useful again: a transcript for every teaching, notes a member will read, answers with sources, and a page for what the church has taught on any chapter. And it runs the booth on Sunday, so the right verse reaches the screen.
Between those two, one rule holds everything together: nothing reaches members until it has been approved, and by default that means a person.
Solutions
Built for the people doing the work.
Invite the team, review drafts together, and let approved teaching become useful beyond Sunday, for one church, many campuses, a whole network, or the platform a church already uses.
One team, one library of what was taught.
Pastors ask what the church has already taught. The media team runs Sunday. Comms approve the note, the newsletter and the blog post. Everyone works from the same approved teaching.
- Owners invite staff and choose who can review and approve
- Volunteers take the suggested verse live with one key
- Unanswered questions become pastoral follow-up
Asks what the church taught on Romans 8 before preaching it again.
Answer with 5 sourcesSends the service stream and keeps the Sunday plan.
Service readyApproves the study note and Monday’s newsletter.
Note approvedTakes the detected verse.
Romans 8:28 liveOne church, many campuses.
Each campus can keep its own teaching, while your church chooses what should be shared more widely. Church-wide leaders can compare how a passage is taught across campuses.
- Campuses keep their own teaching and notes
- Choose what is shared across the church
- Compare a verse or a topic across campuses
Every campus reads Romans 8:28 as a promise for every circumstance. London ties it more often to seasons of grief.
Networks and seminaries, by permission.
Churches choose to join and choose what to share. Each church governs itself. The network can advise and compare, and can never place a church under oversight.
- Ask across teaching member churches shared, with every source named
- Study public teaching from churches that allow it. Private content is never imported
- Nothing in Study appears in your own Ask, notes or shares
Build on a church’s teaching.
Church management platforms, apps and sites call the Folio API from their own server with a key a church administrator creates. Webhooks tell you when work finishes, so you do not need to poll.
- Keys that only read never see a draft
- Signed webhooks that follow the Standard Webhooks scheme
- An OpenAPI 3.1 document for Postman or a code generator
Principles
What we hold to.
These hold whether the feature is easy to build or not.
Folio drafts. Staff approve. Members and public links see the approved note. Automatic approval is off until an owner turns it on.
Teachings, transcripts, notes and questions belong to the church that added them. Private work serves that church.
The web console follows the service. The note is written in the church’s voice, and the words stay clear.
We say plainly what was drafted, what a person reviewed, and what was approved automatically.
Talk to us
We’d be glad to hear from you.
Whether you have one campus or twenty, or you build software for churches, write to [email protected].