Built for Campus Ministry. Built by a Campus Minister.
One system for donor support-raising, student discipleship, and event logistics — instead of five apps and a spreadsheet held together with duct tape and hope.
Four problems, and what each one is actually costing you.
Every campus ministry runs the same three jobs at once — people raising their own support, students moving toward Christ or drifting away from Him, and events that need tracking. Here is where it breaks, and what you get instead.
Five staff, one donor list
Everybody raising their own support, and one login between you. Share it and nobody has any privacy. Don't, and you can't see what is happening across the team.
The spreadsheet nobody updates
A student fills out a card in September and lands in a spreadsheet somebody updates when they remember. By November nobody is sure whether anyone called her.
Discipleship that lives in your head
You know which three students are ready to lead something. It is in your head, not in anything. When your intern graduates, it leaves with them.
Retreat sign-ups by group text
Deposits, balances, waivers, medical forms. Thirty students, four ways of paying, and a group text asking who still owes forty dollars.
One Platform. Three Jobs. Built for How Campus Ministry Actually Runs.
Campus ministry isn't one job — it's donor relationships, student discipleship, and event logistics running at the same time, usually on three different tools that don't talk to each other. CV Campus OS puts all three in one system, built around how a ministry team actually works.
Ministry Hub
Student life and discipleship
BETAThis is the soup-to-nuts side of ministry life. Track a student from the first time they show up to the moment they're leading someone else — plus everything in between: communication, events, and your online presence, all in one place.
- Student CRM built for ministry, not sales
- Discipleship pipeline: Community → Crowd → Prospect → Congregation → Committed → Core → Commissioned
- Alumni pipeline to stay connected after graduation
- Texting, email, basic event management, and a website/hub-link presence
Giving Hub
Individual financial support
BETAMost campus ministry staff raise their own individual support — and most donor tools weren't built for that. Giving Hub gives each staff member their own donor list, and the director a rollup of everyone's. Nobody sees a colleague's donors. Everybody sees what they need to.
- Each staff member sees only the contacts assigned to them — the director sees everything
- Five-stage donor lifecycle: Prospect → First Gift → Recurring → Extraordinary → Lapsed
- Automated reminders, receipts, and follow-up sequences
- Built on "Relationship + Results" — automation handles the logistics so staff can focus on the donor
- Payments processed securely through Stripe — PCI-compliant card capture, no card data ever touches the CRM
Event Hub
Retreats, conferences and mission trips
BETAA simple "sign up for the retreat" turns into a logistics nightmare fast — deposits, balances, waivers, medical forms, payment collection. Event Hub handles it inside the same system already tracking your students, so nothing gets lost between a spreadsheet and a group text.
- Registration with deposits and balance tracking
- Waivers and medical forms built into signup
- Payment collection, no separate processor to manage
- Runs inside Ministry Hub — same students, same records, one system
Your Donors. Not Your Colleague's.
One privacy setting solves the problem every support-raising ministry runs into.
If your staff raise their own individual financial support, you already know the mess. Everybody's tracking donors in their own spreadsheet, their own notebook, their own head. Nobody has a real system, and you — the director — have no way to see the whole picture without asking five people to email you their numbers.
Giving Hub fixes this with one flip of a switch. Every staff member sees only the donors assigned to them. Not the office next door's list, not the whole ministry's contact database — just theirs. You, as director, see everything, including your own support. That's it. That's the whole differentiator, and it's the reason we built this instead of pointing people to a generic donor tool.
Because most donor tools weren't built for a team of people all raising their own support. They're built for one organization with one development office and one shared donor list. Campus ministry doesn't work that way. Giving Hub does.
Payment processing runs through Stripe — proven infrastructure that already powers the majority of nonprofit and church giving platforms in use today, with PCI-compliant card capture so no card data ever touches the CRM.
Giving Hub is in beta right now. Get on the list and we'll reach out when your spot opens up.
How It Works
- Assign contacts to a staff member.
- They see only their donors — nobody else's.
- The director sees the whole picture, every staff member, every donor, including their own.
- Automation runs the donor lifecycle in the background — reminders, receipts, sequences — so staff spend their time on relationships, not data entry.
The Five-Stage Donor Lifecycle
Four Tools, Four Logins, and None of Them Talk to Each Other
The three hubs are what the system does. The dashboard is what your Monday morning looks like once it’s doing it.
Donor spreadsheet in one tab. Student notes in another, if somebody remembered. Retreat sign-ups in a form a student built last spring. Texts going out from your own phone, because that’s the only part that reliably works.
Four places to check before you’ve finished your coffee, four passwords, and not one of them knows anything about the others. So you spend the first hour of the week copying things between them.
What you get instead
One login. One screen. The student who registered for the retreat is the same record as the student you had coffee with in September, and the donor who gave last month is already sitting on your follow-up list. Nothing to reconcile, because there is nothing to reconcile between.
The dashboard is the whole point, and it is deliberately boring. You open it and you see what is actually in front of you today.
- Who gave, and who you still owe a thank-you. That is the first thing on the screen, not a report you have to go and build.
- Which students showed up — and which ones you haven’t seen in three weeks.
- What’s outstanding on the retreat. Deposits in, waivers missing, who still owes a balance.
- Nothing else. The rest of the platform is there if you ever want it. You won’t go looking.
Built By a Campus Minister Who Needed It — Not a Software Company Guessing
David Stone serves as Director of Leadership Development and Coaching with the BSU (Baptist Student Union) at Missouri State University. For years, he lived campus ministry the way most staff do: donor tracking in one place, student discipleship notes in another, event sign-ups somewhere else entirely — spreadsheets, sticky notes, and whatever app happened to be free that semester. None of it talked to each other. All of it depended on someone remembering to check it.
At 40, David was diagnosed with ADHD. He had two options: keep pushing through the chaos and hope he didn't drop anything important, or build a system that filtered the noise for him. He picked the second one.
So he started building inside GoHighLevel — a platform he already used for his marketing business, Clear Vision Design. First he solved the piece that was costing him the most: staff raising their own financial support, with no way to give each of them a private view of just their own donors. Then he built the student side. Then the event side. He wasn't building a product yet. He was building the tool his own ministry needed to function.
Somewhere in that process, it became obvious this wasn't just a Missouri State problem. Every campus minister he talked to was running the same three disconnected systems, held together with the same amount of hope. CV Campus OS is that tool, built at a real ministry, now available to yours.
He didn't set out to build software. He set out to stop dropping the ball — and it turned out every campus ministry was juggling the same ones.
Powered by CV Pro Tools
CV Campus OS runs on CV Pro Tools — the white-labeled GoHighLevel platform David built for his own coaching and marketing work before he ever pointed it at campus ministry. It's the same system running Clear Vision Design and Marketing and Cornerstone Coaching Solutions, configured specifically for how a campus ministry operates.
CV Pro Tools is currently going through a redesign, so think of this as the quiet infrastructure rather than the pitch. The pitch is everything CV Campus OS lets you do with it.
Learn More About CV Pro ToolsStop juggling donor tracking, discipleship, and event logistics in three different tools.
All three hubs are in beta, and there is a working demo you can click through. Join the waitlist to get in early, or book a demo call if you want to see it running before you decide.
No pressure — just a real look at what's built.
Questions You'd Actually Ask Before You Join the Waitlist
Is this just for donor tracking?
No. CV Campus OS has three hubs. Giving Hub handles individual staff support-raising. Ministry Hub is the student CRM and discipleship pipeline. Event Hub handles retreats and mission trips.
Is everything actually live, or is some of this still coming?
All three hubs are in beta. They work, and there is a working demo you can click through. A few pieces, like event check-in and attendance, get set up with each campus during the beta, because every ministry runs them a little differently. Nothing on this page is meant to promise more than that.
Can staff see each other's donors?
No, and that's the whole reason Giving Hub exists as its own thing. Each staff member sees only the donors assigned to them. The director sees everyone's, including their own. Most donor tools weren't built with that boundary in mind — they assume one team looking at one shared list.
Do you rebuild GoHighLevel, or does this run alongside it?
Neither, really. CV Campus OS is a pre-built GHL configuration — pipelines, automations, and permissions already set up for how campus ministry actually works. You're not learning new software and you're not bolting something onto GHL. You're getting GHL already configured for you.
Who processes the payments?
Giving Hub's payment processing runs through Stripe — proven, PCI-compliant infrastructure already used by the majority of nonprofit and church giving platforms today.
What does it cost?
During the beta it's $100 a month per ministry, with no tier that climbs when your list grows. Where a state convention is helping, like the MBC for Missouri campuses, the convention covers $50 of that and your ministry covers $50. Texts and emails are billed at cost, about $25 to $30 in a heavy month. Retail after the beta is $150. Want the details? Email me.
Who is this actually for?
Campus ministries, BSU chapters, and collegiate church plants — anyone raising individual staff support while also trying to disciple students and run events without five disconnected systems. If that's not your situation, this probably isn't for you yet.