Skip to content

Execution Plan

Three Tracks, One Launch

Alex builds the technology. Joshua creates the content and community. They merge at every milestone. Clear ownership, zero confusion about who does what.

⚠️

Honest timeline note

The month numbers below are AI-generated estimates, not commitments. Real timelines depend on how many hours per week each of us can commit, whether we're doing this alongside other work, and how fast we validate demand. The sequence is right — validate before building, build before launching — but the pace is a conversation we need to have.

Key question for Joshua: How many hours per week can you dedicate? That determines whether "Month 3-5" is really 3 months or 6 months. We can move fast — with AI doing most of the development, the app build could be weeks, not months. The bottleneck is content creation and community recruitment.

Alex Technology, AI, Growth
Joshua Content, Community, Ministry
Together Merge points & joint decisions
M1-2

Validate

Month 1-2

A Alex
  • Competitive teardowns (install & document Hallow, YouVersion, Pray.com)
  • Technical architecture: app stack, backend, AI engine design
  • Build survey tool + user interview script
  • Domain & trademark search for app name candidates
  • Financial model v1 (unit economics, pricing tiers)
J Joshua
  • Identify 30 people for user interviews (your community)
  • Document your existing content library (videos, guides, programs)
  • Define Spiritual Fitness Levels (beginner → advanced criteria)
  • Write 10 sample confessional reflection questions
  • List churches/ministries open to early partnership
Together
  • Run 30 user interviews together (Alex builds tool, Joshua recruits people)
  • Decide app name from candidates
  • Agree on MVP feature set (what's in, what's Phase 2)
  • Sign partnership agreement

Milestone

MVP Scope Locked

M3-5

Build MVP

Month 3-5

A Alex
  • Build app shell: onboarding, daily routine player, progress dashboard
  • Build prayer timer with sets/reps tracking
  • Build confessional reflection journal (encrypted, private)
  • Build habit tracker + spiritual fitness level system
  • AI personalization engine (match content to user level)
  • Set up TestFlight + Play Store beta
J Joshua
  • Record 20 prayer set routines (audio, beginner → advanced)
  • Record 10 voice-guided prayers
  • Write 20 confessional reflection guides
  • Write 10 fasting frameworks (who, what, when, why, how)
  • Write 15 scripture reading plans with audio narration
  • Recruit 100 beta users from your network
Together
  • Weekly sync: Joshua reviews builds, Alex reviews content
  • Content integration testing (does the content work in the app?)
  • Beta user onboarding plan

Milestone

Beta Ready

M6-7

Beta Launch

Month 6-7

A Alex
  • Onboard 100 beta users in 4 cohorts of 25
  • Analytics dashboard: track usage, retention, drop-off points
  • Fix bugs and performance issues from real usage
  • Push notifications + streak system
  • Community feed (share progress, prayer requests)
  • Iterate AI recommendations from real behavior data
J Joshua
  • Lead weekly beta user check-in calls
  • Collect testimonials and transformation stories
  • Record 10 more prayer sets based on beta feedback
  • Refine spiritual fitness levels based on actual user progression
  • Identify 3 churches for pilot program
  • Start social media presence (Instagram, YouTube)
Together
  • Bi-weekly feedback review: what's working, what's not
  • Decide on v1.0 feature set for public launch
  • App store submission prep (screenshots, description, keywords)

Milestone

v1.0 Approved

M8-9

Public Launch

Month 8-9

A Alex
  • Submit to App Store + Google Play
  • App store optimization (keywords, screenshots, A/B tests)
  • Launch website + landing page with conversion tracking
  • Set up paid acquisition ($5K/mo: Instagram, YouTube, Google)
  • Email marketing automation (onboarding sequences, re-engagement)
  • Build church admin dashboard for B2B pilot
J Joshua
  • Launch event: live stream + in-person community gathering
  • Podcast tour: 10+ appearances booked (faith + fitness shows)
  • Pastor/ministry leader outreach (personal network)
  • Content cadence: 3 new prayer sets + 2 reflections per week
  • Community challenges: first public 21-day challenge
  • Collect and publish 10 transformation testimonials
Together
  • Launch day coordination (simultaneous app + event + social)
  • Daily metrics review for first 2 weeks
  • First month retro: downloads, retention, revenue

Milestone

2,500+ Downloads

M10-12

Scale

Month 10-12

A Alex
  • Scale paid acquisition to $10K/mo based on working channels
  • Build mentorship matching system
  • Group challenges + leaderboards feature
  • Church licensing portal (B2B self-serve)
  • Begin Series A prep: pitch deck, data room, financial model
  • Hire first engineer (full-time)
J Joshua
  • Onboard 5 church pilots (white-label programs)
  • Expand content library to 200+ pieces
  • Train first 10 mentors on the platform
  • Live prayer sessions (weekly, recorded for library)
  • Speaking engagements at 3+ conferences
  • Hire first content assistant
Together
  • Monthly strategy reviews: what to double down on
  • Pricing optimization based on conversion data
  • Year 1 retro + Year 2 planning

Milestone

25,000 Users

30

Alex Tasks

Tech, AI, Growth

30

Joshua Tasks

Content, Community

15

Merge Points

Joint decisions

5

Milestones

Gates to next phase

The Rule

Alex never waits for Joshua. Joshua never waits for Alex. Both tracks run in parallel — they only come together at merge points. If one track gets ahead, it pulls the other forward. If one gets stuck, the other keeps moving.