Internal · Build Comparison

MWChope vs ShepherdOS

A feature-by-feature and architectural compare of Mo's Mountain West Church build (momwchurch/MWChope) against our ShepherdOS platform. Mo's is a deep, production-deployed church operating system; ours is a younger, SaaS-first platform with a cleaner modern stack and a few genuinely differentiated modules.

Generated 2026-06-12 · Sources: live clone of both repositories

Mo's Build

MWChope

REST · Express + Next.js · Live in production

339

Prisma models

130+

REST route files

170+

app pages (admin+member)

DB migrations

apps (api·web·mktg·native)

100+

unit test files

versus

Our Build

ShepherdOS

tRPC · Next.js 15 / React 19 · SaaS-first

Prisma models

tRPC routers

admin pages

DB migrations

apps (admin·kiosk·mobile)

unit test files

The headline

Mo is ~5× further along on raw feature surface — especially in staff/HR operations, worship planning, a full member-facing app, and integrations. We are ahead on a handful of strategic modules (habit engine, Bible reading plans, engagement scoring, AI-native architecture) and on stack modernity (tRPC end-to-end type safety, React 19). His is church-built-first but multi-tenant capable; ours is product/SaaS-first but earlier.

Full — built + UI + data flow Partial — schema/API or partial UI Missing — not started

Architecture & stack

Same core choices (Next.js, Prisma/Postgres, Clerk, Anthropic) — different API philosophy and maturity layer.

Dimension	MWChope (Mo)	ShepherdOS (Ours)
API style	REST (Express, 130+ routers)	tRPC 11 (end-to-end typed, 24 routers)
Frontend	Next.js 15.5 · React 18	Next.js 15.5 · React 19
Monorepo	npm workspaces · 4 apps / 6 pkgs	Turborepo · 3 apps / 7 pkgs
Auth	Clerk + DB-driven RBAC + API keys	Clerk + role enum
Background jobs	BullMQ + Redis (separate worker)	Inngest
AI	Claude — search, drafts, generosity, in progress	Anthropic SDK — habit coach, insights, narratives (native layer)
Email / SMS	Resend + Twilio + web/native push	Brevo (SMS/push schema-ready)
Multi-tenancy	Yes — Organization root, campus-scoped (built MW-first)	Yes — churchId scoping, plan-gated, white-label config
Observability	Sentry + Pino structured logs	None yet
Tests / CI	100+ unit tests · 8 CI workflows	No tests · deploy workflow only
Hosting	Vercel (web) + Railway (API/DB/Redis) · live	Vercel · scaffold deployed

Feature gap matrix

Grouped by domain. Each row shows build-out status in Mo's build vs ours. The verdict chip flags who leads each domain.

👤 People & Households

Mo leads

FeatureMWChopeShepherdOS

People directory & profilesFullFull

Householdsmerge, notes, tagsFullBasic

Person relationshipsFullMissing

Notes & tagsFullFull

Saved lists & viewsFullMissing

Duplicate detection & mergeFullMissing

Custom fieldsFullMissing

Import / export (CSV)FullPartial

Profile completeness scoreFullMissing

✅ Check-In

Mo leads

FeatureMWChopeShepherdOS

Check-in sessions & recordsFullFull

Kiosk interfaceFullApp exists

Pickup auth + label printingFullMissing

Auto room-distribution rulesFullMissing

Allergy / visitor alertsFullMissing

👥 Groups

Mo leads

FeatureMWChopeShepherdOS

Groups CRUD + membership rolesFullFull

Attendance trackingFullFull

Join requests + approvalFullFull

Member-facing group finderFullMissing

Curriculum & resourcesFullMissing

🎵 Services / Worship Planning

Mo leads big

FeatureMWChopeShepherdOS

Service times & plansFullBasic

Song library + arrangements/keysFullMissing

Media library + live service controlFullMissing

Service evaluations & reviewsFullMissing

RehearsalsFullMissing

AI setlist suggestionsFullMissing

🙋 Serving / Volunteers

Mo leads

FeatureMWChopeShepherdOS

Teams & positionsFullFull

Assignments + schedulingFullBasic

Rotations, swaps, blackoutsFullMissing

Skills & spiritual giftingFullMissing

Volunteer onboarding / shadowingFullMissing

💝 Giving & Generosity

Mo leads big

FeatureMWChopeShepherdOS

Donation recording + fundsFullFull

Recurring givingFullFull

Year-end tax statementsFullMissing

Generosity pipeline + AI intelligenceFullMissing

Capital campaigns + pledgesFullMissing

Budget tracking + reconciliationFullMissing

Online giving widgetPartialMissing

📣 Communications

Mo leads

FeatureMWChopeShepherdOS

Campaigns (email/SMS/push)FullFull

Templates + delivery analyticsFullFull

Consent / unsubscribeFullFull

Drip automationsFullPartial

A/B testingFullMissing

🙏 Pastoral Care & Prayer

Roughly even

FeatureMWChopeShepherdOS

Prayer requestsFullFull

Pastoral inbox + routingFullPartial

Next steps / follow-upsFullFull

Care plansPartialMissing

🌱 Discipleship & Formation

We lead

FeatureMWChopeShepherdOS

Pathways / journeysFullFull

Habit engine (James Clear model)identity habits, logs, streaks, AI coachDevotional onlyFull

Bible reading plansdedicated @shepherdos/bible packagePartialFull

Formation streaks + milestonesFullFull

Engagement scoring (at-risk tiers)PartialFull

Badges / gamificationFullMissing

🏢 Staff Ops & EOS

Mo leads huge

FeatureMWChopeShepherdOS

Staff directory / profiles / departmentsFullMissing

Onboarding & termination workflowsFullMissing

Reviews · growth plans · 1:1sFullMissing

PTO / HR managementFullMissing

EOS — L10 meetings · Rocks · scorecardFullFull

Weekly staff reports + AI summaryFullFull

Project managementFullMissing

Surveys · kudos · succession · SOPs · VTOFullMissing

📱 Member-Facing App

Mo leads huge

FeatureMWChopeShepherdOS

Member dashboard / portal (20+ pages)FullApp shell

Self check-in · giving · events · groupsFullMissing

Sermon watch · bookmarks · reflectionsFullMissing

Member messaging & notificationsFullMissing

Native iOS/Android wrapper (Capacitor)FullPlanned

⚙️ Forms & Workflow Automation

Mo leads

FeatureMWChopeShepherdOS

Form builder + submissionsFullBasic

Form → field mapping + automationsFullPartial

No-code workflow builder (branches/cards)FullRules only

📖 Sermons & Content

Mo leads

FeatureMWChopeShepherdOS

Sermon library + seriesFullFull

Transcripts · bookmarks · reflectionsFullMissing

Watch progress + content distributionFullMissing

✨ AI Layer

Split — different bets

FeatureMWChopeShepherdOS

Pastoral intelligence / insightsPartialFull

AI natural-language searchFullMissing

AI drafts (emails, letters)FullMissing

Habit coachingMissingFull

Report summarizer + dashboard narrativePartialFull

Generosity intelligenceFullMissing

📊 Reporting & Dashboards

Mo leads

FeatureMWChopeShepherdOS

Church overview dashboardFullFull

Exec / campus KPI packetsFullPartial

Discipleship funnelFullPartial

Sunday brief / pastor digestFullPartial

Custom + scheduled reportsFullMissing

🔌 Integrations & Migration

Mo leads

FeatureMWChopeShepherdOS

Planning Center migrationFullPartial

Strety migrationFullMissing

Inbound webhooks (Resend, SecureGive)FullMissing

Calendar sync (Google/Outlook)FullMissing

Public API + API keysFullMissing

🏗️ SaaS Platform & Infra

Split — we lead SaaS, Mo leads infra

FeatureMWChopeShepherdOS

Multi-tenancyFullFull

Plan tiers + Stripe billing gatingPlan fieldFull

White-label configPartialFull

Super-admin / org management portalFullFull

Audit logFullFull

Automated testsFullMissing

CI/CD pipelineFullDeploy only

Observability (Sentry/logging)FullMissing

🟢 Where ShepherdOS is genuinely ahead

Habit engine (James Clear)Full identity-based habits, daily logs, streaks + AI coaching. Mo only has devotional entries. This is our #1 differentiator.
Bible reading plansDedicated @shepherdos/bible package with enrollment + completion tracking. Mo's is partial.
Engagement scoringWeekly at-risk tiering with trajectory baked into the model. Mo's is partial/unclear.
AI-native architectureClaude wired as a first-class service layer (coaching, narratives, summaries) — not bolted on.
SaaS plumbingStripe plan-gating + white-label config built for selling to any church.
Stack modernityEnd-to-end type safety via tRPC + React 19 — fewer runtime surprises than 130 REST handlers.

🟡 Our biggest gaps vs Mo

Entire member-facing appMo has 20+ member pages (self check-in, giving, sermons, messaging). We have an app shell.
Staff Ops / HR / EOS suiteOnboarding, PTO, reviews, 1:1s, projects, surveys, SOPs, VTO — none of it built on our side.
Worship planning depthSong library, arrangements, media, live control, evaluations. Ours is a basic plan model.
Giving depthTax statements, generosity pipeline/AI, campaigns, pledges, budgets, reconciliation.
Integrations & public APIPCO + Strety migration, webhooks, calendar sync, API keys.
Production hardeningTests, CI, Sentry, structured logging — Mo is live; we're a deployed scaffold.

What I'd do with this

Mo has effectively built the broad "operating system." Rather than race him on surface area, the move is to borrow his proven schema/feature patterns where he's ahead and double down where we already differentiate (formation + AI). Concretely:

Mine his schema, not his code

His 339-model Prisma schema is a goldmine of field-level decisions (check-in pickup auth, song arrangements, generosity stages). Adopt the data shapes; we keep our tRPC layer.

Pick 2–3 domains to close fast

Member app + worship planning + giving depth give the biggest "feels complete" jump. Decide which matters most for the first paying churches.

Defend the moat

Keep pushing habits, engagement scoring, and the AI formation narrative — that's the thing Mo (and PCO) don't have. Make it undeniable before broadening.

Harden before we sell

Add tests, Sentry, and CI. Mo's production maturity is a real gap if we onboard real churches with real giving + member data.