Enable works with ministries across five stages, from an honest first look at where you stand through ongoing management of what gets built. Most churches are already standing in one of them and have not named it yet. The right place to start is usually smaller and more specific than leadership expects.
Where You Probably Are Right Now
Find the sentence that sounds like your church. It is usually the right place to begin.
| If this is your situation | Start with |
|---|---|
| We have a policy, but nobody has checked what our systems actually let people reach. | ASSESS |
| Someone on our board asked what our position is, and we did not have a good answer. | ASSESS |
| We have decided against AI on principle, and we still need to know what our staff is doing. | ASSESS |
| Our staff is already using AI and nobody has told them what is allowed. | GOVERN |
| We are paying for AI tools and seeing nothing for it. | ADOPT |
| There is one thing that eats a staff member's week, and everyone knows what it is. | ENGINEER |
| We had something built for us and nobody is keeping it current. | SUSTAIN |
Nothing here sounds like you? That is worth a conversation on its own.
Five Defined Engagements
Each has a scope, a deliverable, and an end. Start where you are, move when there is a reason to.
Assess
Where do we actually stand, and what would break if we turned this on?
- What we do
- We look at what your systems, your data, your permissions, and your staff's current practice can support. That includes what your team is already doing with AI, whether or not anyone approved it.
- What you walk away with
- A clear picture of where you stand, what is blocking progress, and what to fix first, in language your leadership and your board can act on.
- How it works
- A defined engagement with a fixed scope and a fixed fee, run over a few weeks. We need a sponsor on your side and short conversations with a handful of your staff.
- What it needs first
- Nothing. This is where most ministries start.
Govern
Our staff is already using AI. Has anyone told them what is safe?
- What we do
- We put workable rules in place. What information can go where, which tools are approved, what always passes through a person before it goes out in the church's name, and where someone goes when the answer is not obvious. Written for a ministry, not adapted down from a bank.
- What you walk away with
- Guidance your staff and volunteers can actually follow, and a clear answer to the question a board member is eventually going to ask.
- How it works
- A defined setup engagement, with ongoing support available to keep it current as tools change and staff move into new roles.
- What it needs first
- Assess, or an equivalent honest picture of where your data and permissions stand.
Adopt
We are already paying for AI tools. Why are we not getting anything from them?
- What we do
- We turn capability you already own into use your staff can feel. Training by role, clear workflows for the work that actually eats their week, and the permission cleanup that decides whether the tool surfaces the right thing or the wrong one.
- What you walk away with
- Staff who know what to use it for, consistent practice across the team rather than a few enthusiasts, and evidence of what changed.
- How it works
- An onboarding engagement to get it right, then ongoing enablement for as long as it is useful to you.
- What it needs first
- Governance in place, or scoped alongside it.
Engineer
There is one thing that eats my staff's week. Can it be built away?
- What we do
- We build the capability that removes a specific constraint. One at a time, scoped to a real bottleneck, with a person in the loop wherever the decision belongs to someone who knows your congregation.
- What you walk away with
- Something working inside your environment, with clear boundaries around what it touches, and someone accountable for it when it needs attention.
- How it works
- Scoped and priced per build, with an ongoing arrangement to keep it running once it is live.
- What it needs first
- Governance in force, and data and access in a condition we are willing to build on. If they are not, we will tell you, and we will not start.
Sustain
How do we keep this from quietly drifting?
- What we do
- We keep what you have working, governed, and improving as vendors ship changes, staff move into new roles, and new questions come up that your guidance did not anticipate.
- What you walk away with
- Someone accountable when things change, and a standing conversation about what is next instead of an annual scramble.
- How it works
- An ongoing agreement, structured the same way as the managed services relationship many of our clients already have with us.
- What it needs first
- At least one of the above in place to manage.
You are never signing up for all five. We only ever ask for the next one.
Where We Will Not Start
The churches that struggle rarely struggle because the technology did not work. They struggle for reasons that were visible before they started.
- They picked a tool before they named a problem.
- They deployed onto data nobody had cleaned or organized.
- They gave AI access to systems whose permissions had drifted for years.
- They had no guidance, so staff made their own rules.
- They could not measure whether any of it helped, so it quietly stopped.
Every one of these is visible before implementation begins, which is why we look first and build second. If we find that the foundation will not hold what you want to put on it, we will say so and we will show you the shortest path to ready. That answer is worth more to you than a build we both regret.
Start With What Is Possible For You
Thirty minutes with someone who works on this with churches every week.
No cost, no obligation, and nothing to prepare.