Apple
App Store
Supports public version history, current listing details, and $214.99/$215 yearly price context.
Accessed July 15, 2026This public-safe demo separates App Store facts from PTB concept notes. The short read: a growth app should show steady iteration, while this record shows 13 post-launch updates, a 203-day public gap, and only an estimated 13-26 developer days of update work.
The App Store list shows one launch listing plus 13 post-launch public updates. The clearest issue is the 203-day gap from November 21, 2025 to June 12, 2026.
Actual
13 post-launch updates
Mostly bug fixes, performance, UI work, and one larger AI-feature release.
Longest quiet period: November 21, 2025 to June 12, 2026.
Normal
15-20 growth updates
A funded app trying to gain traction should show steady fixes plus meaningful product movement.
That higher pace is still only about 1-2 public releases per month.
Bottom line: the update pace is not unusually aggressive for an app trying to grow. The long public gap is the part that stands out.
- 2.0.0 - May 12, 2025 - launch / bug-fix listing.
- 2.0.1 - May 23, 2025 - minor update.
- 2.0.2 - July 8, 2025 - UI/UX and performance refinements.
- 2.1.0 - July 17, 2025 - performance improvements and bug fixes.
- 2.2.0 - July 19, 2025 - homepage, reels, programs, video, performance, bug fixes.
- 2.3.0 - August 25, 2025 - bug fixes.
- 2.4.0 - September 9, 2025 - UI enhancements, performance, bug fixes.
- 2.5.0 - September 20, 2025 - performance improvements and bug fixes.
- 2.6.0 - September 21, 2025 - bug fixes and performance improvements.
- 2.6.1 - October 28, 2025 - bug fixes.
- 2.6.2 - November 21, 2025 - UI changes.
- 2.7.0 - June 12, 2026 - bug fixes.
- 2.8.0 - June 22, 2026 - AI features, announcements, free trial, stability, UI.
- 2.8.1 - July 3, 2026 - bug fixes.
Many public notes are bug fixes, performance improvements, or UI changes. That does not capture backend work and does not mean every release required the same work level.
A growth-focused consumer app would commonly show meaningful improvements every 4-8 weeks and roughly 1-2 public releases per month. The late-November-to-June public gap is the slow period that stands out.
A clean market read separates build cost, annual operating cost, and update work. These are benchmark ranges, not actual spend records.
Build today
$60k
Current benchmark to rebuild a simple video/community app from scratch.
High end then
$120k
2-4 years ago, a higher-end growth app could reasonably price much higher.
Operate
$12k-24k/yr
Approximate annual hosting, maintenance, monitoring, and support model.
Update
$2k-3k
Typical minor-update benchmark. Older high-end work could run closer to $3k-4k.
Growth read: a higher-end app trying to grow should be capable of roughly 15-20 meaningful update cycles, not just 13 public post-launch updates.
This is based on market research from multiple sources, and I would love to see an alternative report.
Using 1-2 developer days per post-launch update, 13 public updates illustrate about 13-26 developer days, roughly 3-5 work weeks. This is a workload model, not an invoice model.
The cleaner model is $12,000-$24,000 annually for operating, maintenance, hosting, monitoring, and routine support before larger new features.
This is based on market research from multiple sources, and I would love to see an alternative report.
The useful price story is not just the final $215 number. The price concern was raised before launch, then the lower price still did not solve the product-depth issue.
Gold Glove
$297/year
VS
Nonprofit membership on Thinkific, same platform used by Greg for recruitment programs.
Older product, proven demand, and still priced higher.
Trosky 365
$215/year
App Store listing rounds to $215/year, which is $82 less than Gold Glove.
Lower price did not fix the smaller feature set or flexibility gap.
Price warning: the concept notes say the initial price was considered too high and pricing was still unresolved close to launch. The later lower price matters because it came after that concern was already on the table.
No exact user-count claim is stated because the pasted thread says not to state unsupported exact counts unless internally sourced.
This section is concept context. It is meant to show the product opportunity and the repeated date movement without over-writing the point.
~6 months before launch
App first, team tools next
Concepts were very doable team features people wanted, similar in spirit to Nate's Shot Clock app.
Back then: roughly $20k-$30k to build; smaller features could be about half that now.
2 months before launch
Price and concepts stalled
Pricing was still unresolved, while detailed concepts and competitor-tool ideas were already in view.
Some concepts could be standalone high-value businesses if built right.
Launch delayed ~6 months
May 2025 launch
The app launched later than expected and team-tool timelines moved with it.
The core product still did not include the team tools plan.
May-Summer 2025
Wireframes and design concepts
Full concepts focused on team and camp tools that did not compete with the current app.
They matched Trosky-style programs that have worked before and still make sense.
Late 2025
Another year lost
The team-tools promise had been part of the story through investor conversations.
The practical expectation was still a solution that made sense for everyone.
Final reversal
Tools removed from the plan
The concept shifted from delayed to not being built, despite the earlier direction.
That is the main product promise issue.
Timeline statements are PTB concept notes, not independent public-source proof.
Public web sources are separated from PTB concept notes. App Store rechecked July 15, 2026.
Clutch
$40k-$200k+
Simple to complex consumer app build context.
GoodFirms
$5k-$20k+
Annual maintenance benchmark for most apps.
Upwork
$25-$80/hr
Experienced mobile developer hourly-rate context.
AWS
$100-$1,000/mo
Cloud hosting and CDN pricing context.
Deloitte
15%-25%
Maintenance as a share of original build cost.
McKinsey
20%-30%
Better tooling can reduce build and update costs.
Apple
App Store
Clutch
Pricing
Supports mobile app development pricing and agency-rate benchmark context.
Accessed July 14, 2026
GoodFirms
Cost
Supports broad app development cost and complexity benchmark ranges.
Accessed July 14, 2026
Upwork
Rates
Supports freelance mobile developer hourly-rate context.
Accessed July 14, 2026
AWS
Cloud
Supports cloud pricing as pay-as-you-go operating context, not fixed proof of spend.
Accessed July 14, 2026
D. Deloitte.
Maintenance
Supports maintenance and operating-cost context as a share of build cost.
Accessed July 14, 2026
McKinsey
Velocity
Supports developer velocity and iteration-speed context.
Accessed July 14, 2026
PTB
Handoff
Supports the timeline narrative, Gold Glove comparison framing, and handoff-labeled product notes.
Supplied in the current Codex thread