The advice that still circulates in product circles traces back to McKinsey’s repeated “State of AI” surveys: measure what share of any given role can be automated, then budget and staff around that percentage. The framework treats work as a stack of discrete activities that can be sliced, costed, and reassigned without disturbing the surrounding relationships. For teams building tools that land in churches and parachurch ministries, the slice-and-measure approach breaks because ministry work is rarely a set of interchangeable tasks; it is a web of ownership that volunteers accept for free and renew weekly.
When the metric stays at the percentage level, the conversation quickly drifts into questions about model accuracy or token cost. Those numbers look clean on a slide. They hide the actual fracture: some activities can be handed off without anyone noticing the difference, while others quietly transfer responsibility for the person on the other side of the screen. Once that transfer occurs, the original owner stops showing up, and the product team discovers the gap only after usage drops.
This is the foundational misread that causes product teams to ship pilots that look efficient in internal demos and then stall once they reach the actual ministry calendar. The misread treats every hour of work as equivalent. It is not.
Solomon’s judgment supplies the sharper test. Two women claim the same living child. Solomon offers to divide the child so each receives half. The true mother refuses because her stake is not in the fraction but in the whole life of the child. The test does not measure percentage; it reveals whether someone will fight to keep the relationship intact. Applied to AI product work, the same test distinguishes tasks that can be split from ownership that must remain whole.
In volunteer settings the distinction appears quickly. A children’s ministry coordinator can hand a volunteer a pre-written lesson plan generated by a model. The volunteer still owns the moment when a seven-year-old asks an unexpected question during small group. If the tool also generates the follow-up conversation guide and the prayer prompt, the coordinator has begun to transfer ownership of the relationship itself. The volunteer notices the shift within two weeks and stops preparing. Retention falls even though every individual task was completed faster.
The same line appears in pastoral work. Sermon prep contains dozens of tasks—verse lookup, illustration search, slide formatting—that can move to an agent. The ownership that remains is the decision about which text the congregation needs to hear this month and why. When a product asks the pastor to review an entire draft rather than to own the text, the fracture appears. The pastor either rewrites from scratch or begins to treat the output as someone else’s sermon. Either path changes who stands accountable on Sunday.
Once models become cheap enough to run at the edge, distribution patterns shift again. Tools that preserve ownership travel through existing volunteer networks because the volunteer still feels necessary. Tools that quietly absorb ownership require new distribution channels—paid staff, denominational mandates, or direct-to-congregant apps—because the original volunteer network no longer has a role. The cost calculation therefore changes: the cheaper model may require the more expensive distribution strategy.
Why the Percent Question Fails in Volunteer Settings
Volunteer roles are defined by the hours people choose to give, not by job descriptions. When a product team calculates that 65 percent of a volunteer’s checklist can be automated, it assumes the remaining 35 percent will still be performed by the same person. In practice the volunteer experiences the loss of the 65 percent as a reduction in purpose. The remaining slice no longer justifies the drive to the church on a weeknight.
Sermons4Kids data showed this pattern repeatedly. Volunteers who previously spent twenty minutes choosing a craft and ten minutes printing it would accept an auto-generated craft sheet. Once the same system also selected the memory verse and wrote the discussion questions, completion rates fell even though every artifact was still delivered. The volunteer no longer recognized the hour as theirs.
The percent frame also ignores the social contract inside the church. A volunteer accepts the role partly because other volunteers see the effort. When the visible work shrinks, status inside the group shrinks with it. The model has not replaced the task; it has removed the public evidence that the relationship with the children still belongs to the volunteer.
Solomon’s Test Applied to Task Versus Ownership
Map every step of a workflow to one of two categories. A task is complete when the output exists. Ownership is complete only when the person remains responsible for the next human interaction that the output enables. Solomon’s test asks which category a team would fight to keep.
In practice the line appears at the moment of exception handling. A model can generate a small-group question set. It cannot decide, in the moment, whether a particular child’s answer requires a private conversation with a parent. The person who owns that decision must still be present and must still feel authorized to act. Any pilot that removes the need for that person to prepare for the exception also removes the incentive to show up for the exception.
The same line governs data ownership. A children’s director who receives weekly attendance summaries generated by an agent will continue to act on them only if she still owns the follow-up phone call. When the agent also drafts the email to absent families, the director begins to treat the report as background noise. The task moved; the ownership did not survive the move.
Distribution After the Model Gets Cheap
Cheap inference removes the earlier constraint that forced teams to centralize generation inside a single platform. The remaining constraint is who will carry the tool into the room. Tools that leave ownership intact ride existing volunteer and staff relationships. Tools that absorb ownership require paid distribution—regional trainers, licensing deals with denominations, or direct marketing to parents.
The second path carries higher customer-acquisition cost and higher churn once the novelty wears off. The first path scales only as fast as the volunteer network can absorb change, yet it retains the users who already perform the work for free. The choice between these two distribution routes is made at the moment the team decides which ownership transfers it will accept.
Your Turn: Apply This Today
- Pick one current AI pilot and list every discrete step a user performs today; mark each step as either a task or an ownership transfer.
- For every ownership transfer on that list, write the name of the specific person who will still be held responsible when something goes wrong next month.
- Remove or redesign any step where the named person would no longer need to prepare or decide before the next human interaction occurs.
- Run the revised flow with three actual volunteers or staff members and record which steps they still describe as “mine.”
- Compare the revised flow against the original pilot metrics; note any change in completion rate or repeat usage after two weeks.
- Document the ownership line you drew and share it with the next team that proposes a new agent for the same ministry surface.
The posts “How Do You Embed Agents Without Quietly Rewriting Ministry Ownership?” and “The Judgment Step AI Tooling Still Skips in Faith-Tech Pilots” trace the same line through additional ministry surfaces. I consult with product leaders and ministry technology teams on ownership mapping, volunteer retention metrics, and distribution choices after models become cheap. Let’s talk.