For churches on Rock RMS

Technology leadership for churches on Rock.

Rock 19.4 gave every church AI agents that can update records, add people to groups, and draft messages. I help your staff decide what those agents should do, clean up the data they depend on, and build what Rock doesn't.

Who I work with

Churches of about 1,000 or more on Rock, often with more than one campus.

01 · Three ways I help

Software for your staff, a leader at your table, and a Rock that's ready for AI.

01

Church OS

A staff assistant for your Rock, running on an open-source AI model. Your data stays in Rock, and the data entry comes off your team's plate.

Explore Church OS
02

Fractional technology leadership

A technology leader on your staff, part time. I help with vendor decisions, roadmaps, budgets and the hires you shouldn't make alone. Now that Rock has AI agents, that also means writing your staff AI policy and deciding who gets which AI abilities in Rock, and what information should stay inside Rock.

03

Rock AI readiness and data

A project with a clear scope and a clear finish. I help you upgrade to Rock 19.4, check and clean the data your AI agents will read, write down your church's own counting rules (who counts as a member, a regular attender or a first-time guest), and build the first few AI skills worth having. Before you rely on any answer, I test it against those rules so your staff can trust it.

02 · How I work

I build alongside your staff, with the people who will use it every day.

  1. 01

    Discover

    I join your staff rhythm, in person when it matters and remote the rest of the time. I sit in your meetings, talk with the people who feel the problem every week, and read what your systems already say: reports, help desk tickets, how Rock is set up. At one church, that meant finding that "first-time guest" was being counted dozens of different ways.

  2. 02

    Build

    I start with what you have. Your Rock, your giving platform, your spreadsheets. I write down your church's own counting rules, then build only where there's a real gap, alongside your staff and the people who will use it every day.

  3. 03

    Deploy

    I roll it out with the staff who will use it, test the answers against your rules before anyone relies on them, and keep testing after it's live. Your people's information stays in Rock, read where it lives, with no copies made.

  4. 04

    Guide

    Your church owns the strategy, setup and data work I do. Church OS comes with a license your church keeps. You get documentation and training, and I stay on as your technology partner for the decisions that come next.

03 · Questions churches ask me

Rock publishes a list of questions to ask anyone who works on your Rock. They're good questions, so here are my answers.

04 · About me

I've been in your seat.

I'm Jordan Valverde. I spent my first decade in ministry in church planting, parachurch work and missions, so I know what it's like to be responsible for shepherding people and helping them take their next step.

For the last decade I've led technology for the church. I led product at Life.Church across the website, the app and internal staff tools. I was the first product manager at Nucleus, and I led product work on Zúme, the disciple-making system used by church-planting and missions organizations around the world. I've also helped train frontier AI models at Handshake. Today I'm the fractional technology leader for a multi-campus church on Rock in North Idaho.

There aren't enough technology leaders serving the church. For the decades ahead, this is where my experience does the most good, so I'm looking for a few churches to walk with for years.

Jordan Valverde · Founder, HEED

Tell me what's in front of you.