The three stopping points
-
Foundation + live journey pages
- Discovery confirmed
- Data model and Supabase/PostgreSQL schema with creator/admin permissions
- Network/creator recruitment site, Statement of Faith and legal pages
- Unique creator URL/slug and the public 3-step mobile journey page
- Response forms with consent and spam protection, saving to the database with creator attribution
Accepted whenA visitor can open a creator's link, go through the three steps and submit a response that is saved under that creator.
-
Creator platform
- Open registration with configurable approval mode
- "Sign in with Google" for creators and admins, alongside email sign-in, using the OAuth support built into Supabase Auth
- Creator dashboard and editor with preview
- Content blocks: text, video embed, image, PDF/file, link/button, approved embed
- Creator people/responses view with CSV export, and creator analytics
Accepted whenA new creator can register, configure and publish their three sections, and see and export their own responses and analytics.
-
Network CRM, follow-up + launch
- Admin creator management, settings, templates and basic audit log
- Network admin analytics
- Immediate network-sent follow-up email with creator-specific content/CTA, plus email logging and suppression
- VisitorReach outbound link tracking (how contacts are handed to VisitorReach has not been clarified yet; see below)
- Responsive/accessibility QA, staging + production deployment and handoff documentation
Accepted whenThe MVP acceptance statement below is met in production.
A new creator can register, receive a unique URL, configure the three journey sections, publish the page, receive trackable audience responses, see their own data/analytics, and the network can see those same responses aggregated across every creator and trigger network-managed follow-up.
Expected timeline
An estimate to plan around, not a deadline. Each stopping point is complete when it is delivered and accepted, not on a date, so quality isn't traded for speed. Each stopping point starts once the one before it is accepted, so the finish dates add up in order, starting from mid-October. A later start moves every date back by the same amount.
- Stopping point
- Length · estimated finish
- 1 · Foundation + live journey pages
- 6–8 weeksWeek 6–8 · late Nov – mid Dec 2026
- 2 · Creator platform
- 5–7 weeksWeek 11–15 · end of Dec 2026 – late Jan 2027
- 3 · Network CRM, follow-up + launch
- 6–8 weeksWeek 17–23 · mid Feb – late Mar 2027
- Full MVP
- 17–23 weeks (about 4–5 months)Launch · mid Feb – late Mar 2027
The timeline can move with how quickly feedback, content, brand decisions and approvals come back, with what VisitorReach and other outside services require, and with changes to the scope. The dates assume reviews and approvals come back within a few days, and they don't include holiday breaks: Thanksgiving and Christmas fall inside the first two stopping points and may add about a week.
Working agreement
- Both sides will sign a written agreement for this project. The contracting parties are Jesus People Network and the developer.
- The developer plans to operate through an LLC. An LLC is a business structure, not a guarantee of protection for either party; the protections come from the signed agreement.
- After the MVP is completed and accepted, there is a 90-day period for fixing defects in what was delivered. New features and ongoing support are quoted separately.
- The final terms are in the signed agreement. If this page and the agreement differ, the agreement applies.
Not part of the MVP
Anything outside the MVP list (Phase 1.5, Phase 2, SMS, a VisitorReach handoff and ongoing support) is quoted separately and is not part of the MVP.
Phase 1.5 · near-term enhancements
- Multi-email nurture sequences and automation builder
- Additional response types/custom fields
- Webhook/API integrations with external CRMs/email systems
- Advanced segmentation, tags, deduplication and saved reports
- Enhanced application/approval/review tools
- Localization/multiple languages
- SMS follow-up — future phase
SMS follow-up — future phase
SMS functionality is excluded from the MVP. Before implementing any SMS program, Jesus People Network must obtain legal review of the proposed messaging, consent process, applicable federal and state requirements, opt-out handling, and recordkeeping. Any SMS functionality will require a separately approved scope and budget.
Phase 2 · 1–2 year vision
- First-party church recommendation/search platform
- Verified church database + church partner portal
- Closed-loop local church handoff reporting
- Creator directory/discovery
- Advanced cohort/funnel benchmarks
- Public impact dashboard
- Additional community/app experiences only if validated by usage
Also quoted separately
- VisitorReach handoff: not yet clarified. No contact data is sent to VisitorReach until the method, the data shared and the consent wording are agreed and scoped.
- SMS follow-up of any kind (see the note under Phase 1.5)
- Ongoing support: maintenance, monitoring, backups and bug support
What the MVP covers
The platform has three visible experiences plus one shared data and automation layer. All four are in the MVP.
Network / join site
Explains the vision, beliefs and commitments; invites creator registration.
Creator dashboard
Customize the public journey, see data and analytics, export their own records.
Creator journey page
Presents the three next steps, resources, forms and calls to action.
CRM + admin
Stores and reports data, manages creators, runs follow-up and integrations.
Backend robustness
The parts visitors never see carry the most responsibility: personal details, spiritual responses and the follow-up that goes out in the network's name. The backend is built to be reliable first, with as few moving parts as possible, and to grow when real usage calls for it.
One source of truth
All creator, contact and response data lives in one PostgreSQL database (Supabase). Database rules (required fields, links between records, no duplicates where duplicates would cause problems) stop bad data from being saved at all.
Permissions enforced in the database
Each creator's data is protected by database-level rules (Row Level Security) as well as server-side checks, so a bug in a screen can't expose another creator's records.
Every input checked on the server
Forms, sign-in and admin actions are validated on the server, never trusted from the browser. Public forms and sign-in are rate-limited and protected against bots.
Safe retries, no duplicates
Each form submission and each email carries a unique key, so a double tap, a retry or a timeout is saved and sent exactly once.
Email that can't silently fail
Every email is recorded before it is sent, then marked sent, bounced or failed. Failures are retried safely and anything that still fails is shown to admins, and unsubscribed addresses are blocked on every sending path.
Errors are seen, not hidden
Server errors, failed emails and unusual sign-in activity are logged and raise an alert, so problems are found before users report them.
Careful database changes
Schema changes are written as reviewed, reversible migrations and tried on staging first. Nothing is dropped or deleted without explicit approval.
Tested before every release
Automated tests cover the rules that must never break (creator isolation, attribution, consent records, unsubscribe) and run on every change. A staging site is used to try changes before production, with a security review before launch.
Recoverable
Daily backups, a restore that has actually been tested, and an audit log of sensitive admin actions.
Secrets stay on the server
Database keys and service credentials never appear in browser code or in the repository.
Data protection and reliability
The platform holds personal details and spiritual responses, so access is restricted by role. Each creator sees only their own contacts and responses. Responses combined across all creators are visible only to authorized Jesus People Network admins, and that rule is enforced in the database itself, not just hidden in the screens. No creator can reach another creator's data or the network totals behind it.
To be agreed in writing before launch
- Why each piece of data is collected and how it is used
- How long records are kept
- What happens when a creator or visitor asks for their account or data to be deleted
- How long backups are kept, and how deletions apply to them
- How a data breach is handled, and who notifies the people affected
- Which analytics or other third-party services receive any data, and what they receive
Situations the MVP must handle
- A visitor submits the same form twice: one contact, every response kept, no duplicate follow-up
- A message would go out twice, for example after a retry: it is sent once
- A submission times out or the connection drops: nothing is lost or saved twice, and the visitor sees what happened
- A person unsubscribes: no other workflow can email them afterwards
- A message lands in spam or fails to send: the failure or bounce is logged and visible to admins
- The sending domain isn't set up correctly: email stays off until the domain is verified
Launch readiness checklist
A working list of checks to run before launch. It is a starting point, not a fixed commitment: items can be added, changed or removed as the build takes shape and both sides agree what matters most.
Show the current checks
Access control
- Creator A cannot view Creator B's contacts or responses.
- Creator A cannot access admin pages or admin APIs.
- Direct URL and API requests enforce the same permissions as the interface.
- CSV export cannot bypass creator-level restrictions.
- Signing in with Google and with email using the same address leads to one account, not two.
Forms and data
- Invalid inputs and oversized submissions are rejected safely.
- Spam protection works without blocking legitimate users unnecessarily.
- Repeated submissions do not create unintended duplicate follow-up emails.
- Consent records capture the relevant wording/version, timestamp, and action.
- Unsubscribed addresses are suppressed across every sending path.
- Email failures and bounces are recorded and handled.
- Retries do not accidentally send duplicate emails.
- Creator-specific links and content are sent to the correct recipients.
Deployment and recovery
- The public site and creator pages work on iPhone, Android, and desktop.
- A missing page, invalid creator slug, or expired link has a graceful response.
- Secrets and service-role credentials are not exposed in browser code or public repository files.
- Backups can be restored and deletion/retention behavior is documented.
Legal and compliance
The platform will collect names, emails, phone numbers and people's spiritual responses, and will send email on the network's behalf. That brings in privacy, consent, email and accessibility rules. The developer builds the features that support compliance (consent records with version and time, unsubscribe and suppression, data export and deletion, access controls). The developer is not providing legal advice, and that does not replace the developer's own contractual or technical obligations.
Follow-up email is a core part of the MVP. It carries less risk than SMS, because it only goes to people who asked to be contacted and the system is designed with unsubscribe and suppression built in. It still needs clear protocols and legal groundwork in place before it goes live, so that Jesus People Network, its creators, the developer and the people receiving messages are all protected:
- Approved templates, with correct sender, subject and contact details in every message
- Recorded consent and a working unsubscribe that is honored promptly
- Test sends and a full review before email is turned on for real contacts
- Written agreement on who approves message content and who is responsible for email practices, with legal review of the consent and email wording
Jesus People Network is responsible for its own legal review and decisions: the Terms of Use, Privacy Policy, consent wording, Statement of Faith, email practices and any later SMS program. We recommend having a lawyer review these before launch. Legal review is not part of the MVP.
Loading comments…