Soft Launch Operations Hub
Founder guide for managing the first careful review period
"I have yet many things to say unto you, but ye cannot bear them now."
John 16:12 KJV
Soft Launch Purpose
This page helps you manage the private, prayerful review phase after Born Again 360™ is deployed to production. This is not a public announcement and not an endorsement request. This is a humble request for wise counsel from trusted pastors, mentors, and church leaders.
✓ Private review with trusted people
✓ Prayerful request for correction and wisdom
✓ Careful attention to theology and safety feedback
✓ Patient, humble approach before wider sharing
Who to Invite First
Recommended Founder Send Order
Send your humble, prayerful message (no endorsement request)
Include Final Review Packet and Master Review Hub links
Ask reviewer to use Reviewer Feedback Template
Explicitly ask for correction, wisdom, and discernment (not endorsement)
Give reviewers 3–5 days to provide feedback
Collect feedback in private Feedback Template file (keep outside the app)
Wait for all first-wave feedback before deciding on next steps
7-Day Soft Launch Review Plan
Pre-Launch Verification
- ▸Confirm final production domain substituted in robots.txt
- ▸Confirm HTTPS certificate installed
- ▸Verify homepage loads at https://yourdomain.com/
- ▸Verify /start-here page loads
- ▸Confirm sitemap.xml accessible at https://yourdomain.com/sitemap.xml
- ▸Confirm robots.txt accessible at https://yourdomain.com/robots.txt
- ▸Quick manual test: try 1 simulator, 1 course module
First Reviewer Wave (1–2 trusted pastors)
- ▸Send prayerfully written message to 1–2 trusted pastors/mentors
- ▸Include Final Review Packet and Master Review Hub links
- ▸Ask for theology and safety feedback only (not endorsement)
- ▸Set expectation: prayerful review, not public announcement
- ▸Request feedback within 3–5 days
Second Reviewer Wave (1 Bible teacher, 1 tech reviewer)
- ▸Send message to 1 Bible teacher focused on Scripture clarity
- ▸Send message to 1 tech/UX reviewer for usability feedback
- ▸Ask Bible teacher to review: /what-is-born-again, /simulators, /course-mode
- ▸Ask tech reviewer to test on mobile, report broken links/UX issues
- ▸Collect feedback in private Feedback Template file (not in app)
Read & Prioritize Feedback
- ▸Read all feedback carefully (no rush to respond)
- ▸Identify theology concerns FIRST (highest priority)
- ▸Identify safety language concerns SECOND
- ▸Flag any crisis/counseling overclaims THIRD
- ▸Organize other feedback into: urgent fixes vs. future ideas
- ▸Do NOT announce anything publicly yet
Evaluate & Test Fixes
- ▸For urgent theology/safety feedback: test corrections carefully
- ▸For UX/mobile issues: verify they exist, prioritize by impact
- ▸Separate urgent fixes (deploy immediately) from future improvements
- ▸Ask: Does this feedback require code change? Or just documentation?
- ▸Do not overreact to minor preferences; stay focused on core concerns
Extended Testing
- ▸Test full mobile flow on common phones/browsers
- ▸Review all simulator sensitive content language
- ▸Print all course print packets, check formatting
- ▸Verify reflection journal privacy (localStorage only)
- ▸Confirm no analytics/tracking is present
- ▸Check that all 30 simulators still load correctly
Reflect & Decide Next Step
- ▸Prayerfully review what you've learned this week
- ▸Document: What worked? What needs fixing? What can wait?
- ▸Decide: Are you ready to invite a second small group of reviewers?
- ▸If yes: prepare message for 3–5 second-wave reviewers
- ▸If no: continue refining before wider review
- ▸Do NOT expand to public announcement yet
Feedback Priority Guide
HIGHEST PRIORITY
- →Theology errors or unclear theology
- →Safety language concerns
- →Anything that sounds like salvation tracking
- →Anything that sounds like replacing pastors/churches
- →Crisis counseling overclaims
- →Abuse minimization or unsafe reconciliation language
- →Broken production domain or SEO issues
- →Critical mobile usability bugs
MEDIUM PRIORITY
- →Navigation or clarity confusion
- →Print packet formatting issues
- →Course Mode usability questions
- →Visual Learning Lab suggestions
- →Simulator choice clarity questions
- →Minor spelling/grammar errors
LOWER PRIORITY
- →Style or color preferences
- →Feature requests for future phases
- →Nice-to-have UI improvements
- →Requests for analytics or tracking
- →Requests for user accounts (not in scope for prototype)
Red Flag Feedback — Treat as Urgent
If you hear ANY of these concerns from reviewers, stop and investigate immediately:
What NOT to Do During Soft Launch
Current Platform Status (Accurate as of Phase 3A)
Total Routes
107
Active Simulators
30
Completed Waves
3
Course Packets
6
Storage Type
localStorage only
Device-only
Backend
None
Prototype
Accounts
Not built
N/A
Analytics
Not tracked
Private
"Created by Brother Gregory Mahabee, a humble servant of the Lord Jesus Christ."
This platform is a teaching tool, not a replacement for Scripture, pastors, churches, or the Holy Spirit.
Core Theological Anchors
✓ Jesus Christ saves — not the platform
✓ Scripture is the authority — all teaching rooted in KJV
✓ Holy Spirit transforms — the platform is only a vessel
✓ Church is essential — Born Again 360™ supports, never replaces
✓ Pastoral care is final — the platform is secondary to relationship