Contract Rock RMS development

For the parts where you do need a developer.

Workflows, dashboards, check-in, and the data cleanup nobody on staff has time for, or that's too complex or too custom. I administer Rock full time across five campuses, and take on contract work for other churches during my off time.

Remote across Canada & the US Fixed quotes, documented handover
Hadley Sutherland at a Rock RMS conference
What I do

Four things churches keep meaning to fix.

If a staff member is doing it by hand every week, it's probably already a feature you own.

01

Workflows

Volunteer onboarding, background-check follow-up, facility requests, benevolence approvals. Replaces the shared inbox nobody owns with something that actually chases people.

02

Dashboards & data views

Attendance, giving trends, group health and serving gaps, on a page your team opens Monday morning instead of an export that dies in someone's downloads folder.

03

Check-in & registrations

Check-in areas, room ratios, grade promotion and custom label templates. Registration templates that collect what you need the first time.

04

Lava, SQL & cleanup

Custom Lava blocks, SQL data views, duplicate merges, attribute sprawl, and untangling whatever the last admin left behind.

Work

Built in Rock. Used every week.

Everything below runs at Centre Street Church, a five-campus church in Calgary. Three of them you can open right now.

Live on cschurch.ca

Serve Finder

A volunteer matching tool covering 150+ serving roles across five campuses. Someone filters by campus, ministry and spiritual gift, and every role card shows the campus, the ministry behind it, the gifts and skills it suits, and when it actually happens: weekends, weekdays, evenings, behind the scenes or up front.

Roles without their own artwork fall back to a branded campus graphic rather than an empty box, so a page of 150 cards still looks deliberate. From there, someone can take a spiritual gifts assessment and register interest in up to three ministry areas from a single form, landing with the right coordinator instead of a general inbox.

Built with
Lava, data views, multi-facet filtering, workflow on the enquiry
Open Serve Finder
Live on cschurch.ca

Events & Classes

The public calendar for a five-campus church, carrying 60+ concurrent events: weekly Bible studies, sports leagues, ESL classes, retreats. Two views from the same data: a visual grid of upcoming events, or a detailed calendar for people who want the list.

Free-text search runs alongside campus and ministry filters down the left, with a live count so it’s obvious how much a filter narrowed things and a single Clear to start over. Coordinators enter an event once and it surfaces on the right campus.

Built with
Rock calendars & event occurrences, Lava, campus-aware filtering
Open Events
Live on cschurch.ca

Sermon Search

A searchable archive of past messages. Someone who half-remembers a sermon can search it in plain language, or narrow by year, speaker and guest speaker, and sort by date.

Each result carries the title, date, speaker, the scripture references it covers, and a short summary of what was actually said, so you can tell from the results page whether it’s the one you meant. Every message links straight out to YouTube, Spotify, Apple Podcasts and audio, rather than dead-ending on the website.

Built with
Content channels, Lava, faceted search, syndication to podcast platforms
Open Sermon Search
Internal

Connection dashboard for connectors

Connection requests do a lot, and staff found the standard screens over-complicated, enough that nobody could be handed the module without being trained on it first. I rebuilt it as one page: a connector opens it and sees only their own requests, what’s waiting, what’s gone cold and what needs an action today. Staff still get the roll-up across every opportunity.

The result is that a new connector needs almost no training, which is what was actually costing the team time.

Built with
Connection requests, Lava, custom dashboard blocks

Behind the staff login

Most of what I build isn’t public, so there’s nothing to link to. It’s also where most of the work is.

Custom person profile badges

Badges that surface what staff actually need at a glance on a person record, without clicking into four tabs to find it.

Advanced check-in label templates

Custom Zebra label designs beyond Rock’s defaults: conditional content, security tags, and allergy or note flags printed where volunteers will see them.

Content channels

Structured content in Rock driving the public site (sermons, articles, resources) so nothing lives in two places.

Workflows & automations

Approvals, follow-ups and routing that replace the email chains staff were using to move work between people.

How it works

Four steps. No surprises on the invoice.

  1. A call

    Thirty minutes, free. You show me what's manual right now, I tell you whether Rock can fix it and roughly what that takes.

  2. A written scope

    What gets built, what it costs, how long. Fixed price where the work is well-defined, hourly only where it genuinely isn't.

  3. I build it in your Rock

    I work in your instance at whatever access level you're comfortable granting. You see progress as it goes, not a reveal at the end.

  4. Handover with documentation

    Written notes on what was built and how to change it, so your team isn't locked into calling me. Ongoing support if you want it.

Pricing

Published, so you can budget before we talk.

Invoiced in CAD or USD. Net 30.

Hourly

$150 /hr CAD

For open-ended or ad-hoc work

  • Billed in 15-minute increments
  • No minimum commitment
  • Monthly invoice

Scoped project

Fixed quote

For a defined piece of work

  • Price agreed before work starts
  • The quote is the price
  • Documentation included
  • 30 days of fixes after handover

Ongoing support

Let’s talk

For churches without a Rock admin

  • Retainers available
  • Priority when something breaks
  • Upgrade testing & support
  • Scaled to your instance, not a fixed package

Tell me what's still being done by hand.

Send a sentence or two about what you're trying to fix. I answer everything within a business day, including the ones where the answer is no.