Why We Built Lifted Prayers

Most churches already collect prayer requests. They come in through a contact form, a sticky note handed to a greeter, a comment under a livestream, a text message to the pastor’s personal phone. Each one carries something real — a diagnosis, a marriage under strain, a child who has stopped calling home. And each one, too often, ends up in the same place: a shared inbox nobody quite owns, or a spreadsheet that gets opened once a week if it’s opened at all.

That gap is not a failure of care. It’s a failure of tooling. Most of what churches have used for this was built for something else — a generic contact form, a comment box, a plugin meant for blog replies — and asked to hold something it was never designed to hold.

We built Lifted Prayers around a simple conviction: a prayer request should move through a church the way real pastoral care moves — deliberately, privately, and with someone responsible for what happens next.

That’s the shape of the product. A member receives the space to bring a need without friction — no required account, no pressure. What they submit is protected by default; the person asking decides what’s shared and with whom. A real person on the care team reviews every request before anything reaches the congregation — nothing publishes itself. What’s approved becomes something the church can pray over together, quietly, without turning care into a counter. And because a submitted request is rarely the end of the story, the ministry can follow up — a private note, a check-in — so the relationship doesn’t stop the moment the form is submitted.

None of that is complicated. It’s also not automatic — every step still depends on a person choosing to show up for it. What Lifted Prayers does is make sure the request survives long enough to reach that person, intact and unread by no one.

We didn’t set out to build a plugin with a dashboard full of metrics. We set out to build a place dependable enough that a vulnerable message never becomes another forgotten email.