Platform as a service · for ministries

Your ministry gets a platform, not a project.

Capstone stands up a ministry's entire digital operation — public website, back office, and a reading app for your own published material — on cloud infrastructure we build, own, and keep running. You get the login. We keep the pager.

Book a walkthrough See how it works

Issued by: SR Freed ConsultingVendor of record
Applications: ThreeWebsite, admin, reader
Capabilities: TenSwitched per ministry
Status: In serviceTwo ministries live

The situation

Most small ministries are running six products and a volunteer.

Nobody chose this. It accumulated. Every tool was reasonable on the day it was added, and together they cost more than anyone adds up.

A website builderMonthly, per site. Nobody remembers the password.

An email toolIts contact list disagrees with every other list.

An events productTakes a cut of every registration.

A storefrontSeparate customers, separate orders, separate tax.

A spreadsheetThe actual system of record, and everyone knows it.

A volunteerWho built it, and has since moved away.

Six bills, six logins, and no single place where a person who gave, registered, subscribed and bought is one person.

What Capstone is

One multi-tenant platform. Every ministry gets its own isolated slice of it.

Capstone is a platform-as-a-service control plane. Underneath it is one engineered codebase — a content management system, a contact and forms database, an events manager, a commerce engine, a campaign and email pipeline, and a digital library — built once, hardened once, and improved for everyone at the same time.

On top of it, each ministry is a tenant: its own Google Cloud project, its own database, its own storage, its own domain, its own sign-in, its own secrets. Not a folder in a shared account. A tenant's data is separated by the cloud provider's own boundary, not by a WHERE clause somebody has to remember to write.

And it is done for you. Nobody at a ministry ever sees Capstone itself. Our team runs the provisioning, the domains, the releases, the certificates, the backups and the upgrades. What the ministry gets is a working website and a plain-English admin panel with their own logo on it.

You are live on day one on a seeded starter site, with real pages already in place. Then you make it yours.

The applications

Three apps, and you choose which ones you need.

The admin is always built. The public website and the Library Reader are chosen per ministry, and a capability that needs an app it doesn't have simply isn't offered.

Always built

The Admin

The back office. Staff and roles, contact records, the form builder and its submissions, events and registrations, campaigns, reports over your own data, and the library manager. Delegated access means a volunteer can be granted exactly one page and nothing else.

Used by: staff and volunteers

Optional

The Website

Your public site. Every page is a stack of content sections edited in the admin — no developer, no deploy, no ticket. Home slider, forms that belong to the page they sit on, a podcast page fed straight from your YouTube playlist, a newsletter, and a store with real checkout when you want one.

Used by: everyone you serve

Optional

The Library Reader

A reading app for material you have written — books, studies, curriculum — published from the admin, with highlighting and progress that follow the reader across devices. On the web, and on Android through the Play Store.

Used by: your readers and cohorts

The capability catalogue

Ten capabilities. Switched on per ministry, changed whenever you ask.

A plan decides what you are born with, not what you are allowed. Every switch below is free to flip afterwards — there is no upgrade wall and no second build.

Capability	In market terms	What it gives you	Needs	Light
Core	Identity & access	Sign-in, staff, roles and delegated permissions. Always on.	—	Always
Content	CMS	Site pages built from a section library, home slider, page builder.	Website	Included
Contacts	CRM	Contact records, the form builder, and every submission attached to the person who sent it.	—	Included
Events	Registration	Events manager and registrations, with no per-ticket cut taken by anyone.	—	Included
Reports	Analytics	Report screens over the ministry's own data, plus per-tenant visitor analytics.	—	Included
Podcasts	Media	A podcast page on the site, fed from the ministry's own YouTube playlist.	Website	Included
Newsletter	Publishing	A newsletter on the site, written in the admin. You name it and pick its address.	Website	On request
Campaigns	Marketing automation	Campaign manager and the send pipeline, targeted at the contacts you already hold.	—	On request
Store	E-commerce	Product catalogue, cart and checkout, PayPal, live shipping rates and sales tax.	—	On request
Library	Digital publishing	Library manager in the admin, publishing your titles straight to the Reader.	Reader	On request

Brand

Set twelve colours. The system derives the other fifty.

A ministry's brand is entered once, as twelve seed values and a type pairing. From those, the platform derives roughly fifty design tokens — button fills, link text, borders, surfaces, muted states — and checks the contrast of every one of them as it goes. A brand colour that works as a button but fails as body text gets corrected automatically rather than shipped unreadable.

You edit against a live preview of your own site, save drafts that change nothing public, and publish when it looks right. It is the difference between picking a theme and having a brand.

Provisioning · run by the Capstone team

One form, twelve steps, a whole cloud estate.

This is the part nobody else does for a ministry your size. From a single record — name, domain, plan, capabilities — an automated worker builds the entire footprint. Each step is checkpointed, so a run that stops can resume exactly where it stopped rather than starting over.

Step 01

Create project

A dedicated Google Cloud project, owned and governed by us.

Step 02

Link billing

Ours by default; your own billing account if you'd rather.

Step 03

Enable APIs

Only the services this ministry's chosen capabilities actually need.

Step 04

Create database

Your own Firestore instance in your chosen region.

Step 05

Auth and owner

Sign-in, and the first administrator account handed to you.

Step 06

Storage bucket

Private file storage for images, documents and published titles.

Step 07

Hosting sites

A public site and an admin site, each with managed certificates.

Step 08

Write secrets

Every credential generated into your own secret manager, never shared.

Step 09

Push configuration

Your capabilities, brand and settings pushed into the tenant.

Step 10

Build and deploy

Your apps built from a pinned platform release and shipped.

Step 11

Attach domain

We show you the exact DNS records. The job waits here — deliberately — until your domain answers.

Step 12

Verify

An automated check that every piece actually responds before we call it live.

Step 11 is the only place a human is in the loop, and that is on purpose: your domain belongs to you, so the records are yours to add. Everything before and after it is automated, repeatable, and identical for every ministry — which is precisely why we can afford to do it for ministries that couldn't otherwise pay for it.

Upgrades work the same way. Every tenant is pinned to a numbered platform release, and moving one forward is a job, not an outage.

Tenancy

A ministry inside a ministry, without a second bill.

Ministries grow arms — a coaching practice, a regional chapter, a conference, a publishing imprint. Each one wants its own website, its own name and its own front door, and none of them wants to be a separate organisation.

First-tier customer

The ministry Its own cloud project, database, storage, sign-in and domain. Fully isolated from every other tenant on the platform.

OWN PROJECT OWN DOMAIN OWN DATA

A second-tier customer Lives inside the parent's project. Its own website, its own admin, its own domain and its own brand — sharing the parent's infrastructure, billing and payment setup.

OWN SITE OWN ADMIN OWN BRAND SHARED BILLING

A second-tier customer is a full tenant in every way that shows: its own address, its own look, its own pages, its own staff and its own admin panel. What it shares is the plumbing underneath — and the bill.

It can even sell. A second-tier customer picks products from the parent's catalogue and sells them through its own storefront, on the parent's payment and shipping setup, with every order attributed back to where it came from. The selection is enforced at checkout, not just hidden in the storefront — a product that wasn't offered cannot be bought.

And it isn't a trap. A second-tier customer that outgrows the arrangement is lifted out into its own project when it's ready.

Plans

A plan is where you start, never a ceiling.

Both plans are the same platform and the same build. The difference is what's switched on the day you open it. Nothing is withheld to sell back to you later.

Light

Talk to us

The website plan. For a ministry that needs to be findable, contactable and organised.

Public website and admin
Pages, sections and home slider
Contacts and the form builder
Events and registrations
Reports and visitor analytics
A podcast page

Store, campaigns, newsletter and library stay off until you want them. Then we switch them on.

Full

Talk to us

Everything the platform supports, on from the first day.

Everything in Light
Store, checkout, shipping and tax
Campaigns and the send pipeline
Newsletter
Library Manager and the Reader app
Second-tier customers under you

Priced per ministry, because a ministry of six and a ministry of six thousand are not the same customer.

On price: we are still setting it, and we would rather set it with a few real ministries in the room than guess. Book a walkthrough and we will talk about what your ministry actually needs and what it should cost.

In service today

We run our own work on it.

Capstone is not a pitch deck. Two ministries are live on it right now, on the same release, and one of them is the second-tier arrangement described above.

Impact Disciples

Live First-tier Full plan

Website, admin and the Library Reader. Store with live shipping and tax, campaigns, events, a podcast page, a newsletter, and a published library reaching readers on the web and on Android.

Coaching with Impact

Live Second-tier Light plan

A coaching practice running inside Impact Disciples' project with its own site, its own admin, its own brand and its own domain — provisioned end to end from the Capstone console, and selling from the parent's catalogue.

On the drawing board

What's coming, said plainly.

We would rather tell you what isn't finished than let you find out during a demo.

In build

The Page Designer

A visual, drag-and-drop designer for site pages — the same block designer our email composer already uses, brought to the website. Today you build pages from a section library in the admin, which works and is in daily use. The designer makes it visual. Shipping shortly.

In build

Cost transparency

Per-ministry infrastructure cost reporting, so you can see what your tenant actually costs to run rather than take our word for it.

Book a walkthrough

Thirty minutes, a real system, no slides.

We will open a live tenant, build a page, add a form, switch a capability on, and show you a provisioning run from the console. Then we will tell you honestly whether Capstone is right for your ministry.

Prefer email? Write to shane.freed@srfreedconsulting.com.