Conflict of interest

The operator has material relationships in church tech, including a financial interest in at least one product that may appear in stacks. Those products never get an editorial buy verdict from us.

The person who runs this site has material relationships in the church-tech space, including a financial interest in at least one product that may appear in documented stacks. You deserve to know that, and to know exactly what it does and doesn't change.

The firewall

Any product the operator has a material relationship with is excluded from editorial endorsement. Full stop. Such a product can appear in a stack when a documented church genuinely runs it. We report what's true, but it is never recommended, ranked, featured, or given a "buy" verdict in a review by us. No exceptions, and no quiet adjustments over time.

Why we don't name the products

Naming the relationships would identify the operator, and the operator writes under a pen name so the work stands on its own. So the ownership stays private, but this policy never does. It's public, it applies before any conflict arises, and it doesn't change when one does.

What this means when you read a page

Stacks show what a church actually runs: nothing more, nothing less. Workflows show how a church actually made those tools work. Reviews give a clear verdict only when the tool sits outside the operator's firewall. When we evaluate or recommend anything, affected products sit outside that judgment entirely. If that trade-off doesn't sit right with you, that's fair. Judge us by the pages.

How to verify us this week

Open any public setup or how-to. You should see named tools, ordered steps, real cost, and a last-checked date near the top. Compare that page to our editorial standards. If a live page fails the checklist, tell us. We correct in public.