The questions churches ask before moving to Flocksy.

If you've been evaluating church software — or putting up with what you have — you've already asked most of these. Here are straight answers to the five objections that come up most often, from pricing and migration all the way to what happens when something breaks on a Sunday morning.

It's actually affordable. Flocksy runs $49–59 per month, flat, plus a 1% transaction fee on giving. That's it. No per-seat charges that creep up the moment you give a second admin a login. No "premium tier" upgrade that gates the feature you actually need. No setup fee, no onboarding surcharge, no annual renewal trap that doubles the price the second year.

Compare that to PowerChurch, Tithe.ly and Pushpay — all of which most often price per seat or at a higher 3–4% transaction fee. For a 200-person church with a part-time office manager and a few staffers, that's the difference between Flocksy being a line item in a tight budget and being a line item that has to get approved by the board.

It comes with you, and the import is part of what we do, not something we hand you as homework. Flocksy has a guided CSV bulk-import for members — preview it, confirm it, watch it land — and on the giving side we accept exports from the prior ChMS so historical donations and year-end statements stay intact.

During onboarding, a real person from our team walks the migration with your admin. We don't ask you to do it over a cutover weekend while the congregation is watching, and we don't make you re-key ten years of names and addresses by hand. Member and donation history are preserved; what you got on your old system stays on your new system.

That's the audience Flocksy is built for. A 120-person church with an office manager and a part-time admin volunteer — not a church with a full-time tech director. The everyday tasks a Wednesday-morning admin volunteer needs to do — finding a member's record, recording a check, sending a quick communication, scheduling a Sunday-service role — each take a click, not a configuration.

Training is included in the first month. We run your admin through the tool live, not by handing them a manual. If the person in the seat is struggling six months in, they can write to us and a real person answers. Flocksy is designed for the church that has 50 people on a Sunday and scales to the church that has 500 — but it starts simple either way.

For the work a small or mid-size church actually does week to week — members and directory, online giving, year-end statements, communications, volunteer scheduling, events and calendar — yes, Flocksy covers it. We built the four things church offices spend the most time on, into one tool, instead of selling a "platform" that covers everything superficially and nothing deeply.

We're transparent about what isn't shipped yet. Child check-in, for example, isn't in the product today — it's on our roadmap with a planned timeline that's published so you can plan around it. PowerChurch and other long-standing tools have features Flocksy doesn't try to match; we're focused on the CRM core and we want to do it really well, not pretend to be an operating system for your whole church.

Support means a direct line to a real human — not a ticketing portal, not a chatbot that walks you through a script. The founder's email is on every page, and a question sent on a Tuesday gets a reply the same week, usually the same day. If something breaks on a Sunday morning, that gets escalated before anything else.

On the reliability side, Flocksy is hosted on Render and runs on a Postgres database on Neon, both of which have a multi-year track record and status pages visible to anyone who wants to look. We're a small team but we run on infrastructure that's built to stay up — and we don't bill you extra per-incident or per-seat when something needs fixing. Support is part of what you already pay for.