The Navigators Project — Complete Overview

Prepared: 2026-03-20 Author: Joshua Smith, Storyland Studios Status: Pre-Kickoff (March 26, 2026)

What This Actually Is

The Navigators is a 90-year-old discipleship organization with 3+ million app users, a publishing arm (NavPress via Tyndale), and a network of churches. They've spent years with fragmented digital tools — separate platforms for video, courses, groups, content distribution — and engagement is low despite the installed base. The internal culture has been marketing-led, which slowed product progress.

Storyland's pitch, which landed: don't rebuild, reconfigure. KiteString — our existing multi-tenant SaaS platform — already has 255 pages, 467 API endpoints, and 149 database models covering everything from video streaming to AI-powered content search to marketplace settlements. The $50K SOW is essentially a 12-week sprint to configure KiteString for Navigator-specific use cases, build the 30% that doesn't exist yet, and prove enough value to unlock a much larger engagement (potentially $250K+ contingent on a Murdoch Foundation grant).

What Already Exists (the 70%)

KiteString is production software. It's not a prototype. What the Navigators get out of the box:

Content delivery — Mux-powered video with adaptive streaming, auto-captions, transcoding. Full LMS with courses, lessons, multi-format materials (video, text, audio, PDF, workbooks, Scripture references), cohort enrollment, certificates, learning pathways. Podcast hosting with RSS.

Community — Virtual small groups with Stream.io video calls, synchronized content playback, discussion questions, attendance tracking. Prayer requests, direct messaging, discussions.

Engagement — 4-tier badge system, streaks with grace periods, leaderboards, pathways. Gamification is already wired to course completion and content consumption.

AI/RAG — Entitlement-aware search (users only query content their org has access to). Citation enforcement, hallucination detection, token attribution to publishers. This isn't experimental — it's in production with guardrails.

Monetization — Stripe subscriptions, 5-tier church pricing (Free through $499/mo), marketplace with 98/2 publisher revenue split, automated weekly settlements via Stripe Connect, AI attribution revenue (publishers earn passive income when AI Chat cites their content).

Multi-tenancy — Subdomain-based isolation, custom domains, branding customization, role-based access (5 roles), 34+ admin dashboard sections.

Devices — Responsive web, iOS, Apple TV/tvOS, PWA.

What Needs Building (the 30%)

This is where the sprint's real work lives. Six distinct capabilities:

1. YouVersion SSO + Reading Plan Workaround (~40 hours Brendan)

The YouVersion API is more limited than anyone initially assumed. It supports SSO, Bible text, highlights, and notes — but NOT reading plans. This was a major scope adjustment (DEC-03). The build: implement OAuth SSO for seamless cross-app identity, Bible text integration for Scripture-linked materials, and a custom reading plan engine inside the Navigator app as the workaround. The Bible API abstraction layer (DEC-19) hedges against YouVersion partnership risk by supporting multiple providers (API.Bible, Bible Brain) simultaneously.

2. Custom Assessment Engine (~60 hours Brendan)

No off-the-shelf survey tool works here. Navigator spiritual formation tracking needs multi-dimensional scoring across biblical knowledge, spiritual disciplines, character formation, and community investment — with longitudinal measurement over 6-24 months. The REVEAL study (Willow Creek) proved that church attendance doesn't correlate with spiritual maturity, which validates assessment-driven content progression as the core differentiator (DEC-38, DEC-39). This is the feature no competitor has. The build: Typeform-style UX, score-based adaptive paths, progressive unlocking tied to assessment completion and peer interaction. Blocked on Navigator content team delivering assessment questions by April 2.

3. Micro-DLC Framework (~50 hours Brendan)

The original DLC approach was live sessions that don't scale. Stuart (internal product champion) drove the pivot to self-paced async delivery (DEC-20). The build: bite-sized learning modules integrated with reading and notes flows, async delivery pipeline with scheduling, notification sequences, and content targeting. This sits on top of the existing LMS but adds the async delivery layer and the "micro" chunking that makes it daily-habit-forming rather than course-completing. Content production is underway at Navigators — scripts finishing, filming starting.

4. Leader Activation System (~35 hours Brendan)

The journey from consumer to contributor to multiplier. The build: onboarding flows for emerging leaders, a portal/in-app resource center, vetting processes with continuing education requirements, and the ability for leaders to add their own content. This connects the assessment engine (which identifies emerging leaders based on formation metrics) to the reproduction tracking system.

5. Reproduction Tracking (~45 hours Brendan)

The metric that matters to Navigators isn't engagement — it's multiplication. How many people are being discipled, by whom, and are those disciples making disciples? The build: analytics pipeline tracking the reproduction chain, dashboards showing activation-to-reproduction funnels, executive scorecard. This is what makes the donor narrative work — connecting digital engagement to real-world disciple-making outcomes.

6. Church Pilot Onboarding (~25 hours Brendan)

Crossroads and Harvest are the target pilot churches but neither has signed yet. The build: church-specific KiteString configurations, onboarding workflows, church analytics dashboards, and the coordination infrastructure to support 2-3 live church pilots during the SOW window. The bigger play: this validates KiteString for Church as a product line targeting 20 initial partner churches (DEC-41), turning Navigator-funded work into a repeatable platform business.

The AI-Native View

This project isn't just using AI for development speed — it's building an AI-native product layer that doesn't exist anywhere in faith-tech:

The Content Intelligence Loop

NavPress has a 200K+ item catalog. When that's ingested into KiteString's RAG system, every piece of content becomes queryable, citable, and attributable. A Navigator in a small group asks "what does our tradition say about mentoring across generations?" and the AI surfaces relevant passages from Navigator books, courses, and devotionals — with citations. The publisher gets paid per-token when their content is cited (DEC-31). This creates a flywheel: more content ingested -> better AI answers -> more usage -> more publisher revenue -> more publishers want in.

Assessment-Driven Personalization

The custom assessment engine doesn't just measure — it routes. A new user completes an initial spiritual formation assessment, and the system knows whether to surface foundational reading plans, intermediate DLC modules, or leader activation pathways. As they progress, reassessment adjusts the path. No faith-tech platform does this today. YouVersion shows everyone the same content. RightNow Media is a video library with search. The Navigator app would be the first to adapt its content journey based on measured spiritual formation.

Formation Metrics as the Product Thesis

Every competitor measures engagement (views, time-on-app, DAU/MAU). The Navigator platform measures formation — character development, behavioral integration, community impact, multiplication. This is DEC-39, and it's the single most important architectural decision in the project. It means the dashboard that David Sheppard shows to donors doesn't say "10,000 monthly active users." It says "142 people moved from consumer to active disciple-maker this quarter, and they're collectively mentoring 340 others." That's a fundamentally different narrative.

The Church-as-Publisher Model

Any church on KiteString can become a content contributor (from the GTM strategy). A pastor attaches sermon notes and a discussion guide to their Sunday message. It surfaces in other churches' Resource Networks. AI Chat cites it when relevant. The pastor earns attribution revenue. This turns the platform from a top-down content distribution system into a networked knowledge base where the best discipleship content rises organically.

What's Really at Stake

The $50K SOW is a proof point. The real prize is:

1. The Murdoch Foundation grant — $600K-$1.5M with $400K+ potential for Storyland. Timeline uncertain, but a successful sprint with measurable outcomes is the strongest possible case.

2. KiteString for Church as a business line — 20 initial partner churches, then denominational partnerships. The $30K/year Navigator licensing fee already makes KiteString profitable. Each church at $99-499/mo is recurring revenue.

3. The LearnUpon replacement — If KiteString's LMS replaces LearnUpon org-wide (DEC-33), that's a much deeper integration and ongoing revenue stream.

4. NavPress marketplace at scale — 200K+ items, AI attribution revenue, church-to-contributor pipeline. This is a platform business, not a services engagement.

The Critical Path to March 26

We are 6 days from kickoff. The hackathon (March 20-25) is our window to turn the gap analysis into a live demo. The repo is in solid shape — 43 tracked decisions, research completed, all planning docs current. What matters now:

• Brendan sync (Mon/Tue) — He needs to review docs/brendan-review.md and validate the 305-hour technical allocation is realistic

• Navigator-branded demo environment — A live KiteString instance showing the 70% that already works

• The kickoff narrative — "We're not starting from zero. We're configuring a production platform for your mission. Here's what's already working, here's what we're building in 12 weeks, and here's what we need from you to stay on schedule."

The dependency clock starts at kickoff. Assessment questions by April 2, DLC content by April 9, reading plans by April 16. If those slip, the whole timeline shifts. That's the message for March 26.