A 20-update target stays inside the 15-30 expected range for 14 months. The public record lands 7 short, about 35% under that target.
App Store + benchmark modelThe App Store public version history shows 14 entries total: the May 12, 2025 launch listing plus 13 updates after launch. Against a 20-update growth target, that is 7 short, about 35% under pace, with a 203-day public gap from November 21, 2025 to June 12, 2026.
Research Note
0/6 open
This is based on public-source facts plus market research from multiple sources. If a stronger alternative report exists, the numbers should move with the data.
The App Store list shows 14 public version entries total: one launch listing plus 13 post-launch public updates. The clearest issue is the 203-day update gap from November 21, 2025 to June 12, 2026.
01
Update Cadence AnalysisPublic record versus a growth-mode tech pace
Actual: May 2025-July 2026
14Public entries
13Updates after launch.
203Days quiet: Nov 21, 2025-Jun 12, 2026.
AIOne larger AI/free-trial update on Jun 22, 2026.
Growth Pace Target
20Updates
15-30Expected range across 14 months.
1-2Public releases per month.
4-8Weeks between meaningful improvements.
Honest read: many public notes are bug fixes, UI changes, or performance work, with one larger AI/free-trial release. That does not prove every update was equal work.
App Store release notesBottom Line: For a tech division trying to grow, the count is light and the silence is the problem. The 203-day public gap makes the record look more like maintenance mode than steady product movement.
1May 12, 20252.0.0 launch listing / bug fixes.
2May 23, 20252.0.1 UI/UX, performance, fixes.
3Jul 8, 20252.0.2 UI/UX and performance refinements.
4Jul 17, 20252.1.0 performance improvements and bug fixes.
5Jul 19, 20252.2.0 homepage, reels, programs, video, performance, fixes.
6Aug 25, 20252.3.0 bug fixes.
7Sep 9, 20252.4.0 UI enhancements, performance, fixes.
8Sep 20, 20252.5.0 performance improvements and bug fixes.
9Sep 21, 20252.6.0 bug fixes and performance improvements.
10Oct 28, 20252.6.1 bug fixes.
11Nov 21, 20252.6.2 UI changes.
12Jun 12, 20262.7.0 bug fixes.
13Jun 22, 20262.8.0 AI features, announcements, free trial, stability, UI.
14Jul 3, 20262.8.1 bug fixes.
A clean market read separates build cost, annual operating cost, and update work. These are benchmark ranges, not actual spend records.
Build Today$60kApprox current build cost
Build Then$120kHigh-end 2-4 years ago
Operate$12k-24k/yrAnnual maintenance model
Update$2k-3k$3k-4k older high end
Update Workload13 post-launch updates illustrate about 13-26 developer days, or roughly 3-5 work weeks.
Growth ReadA growth-focused app should be capable of roughly 20 meaningful update cycles, not just 13 public post-launch updates.
Benchmark OnlyUse this as market research context, not proof that every release was separately invoiced.
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 shows the product opportunity and the repeated date movement without overwriting the point.
- App first, team tools immediately after.
- Very doable features people wanted, similar in spirit to Nate's Shot Clock app.
- Back then: roughly $20k-$30k to build; smaller features about half now.
- Pricing was still unresolved.
- Detailed concepts and competitor-tool ideas were already visible.
- Some concepts could be standalone high-value businesses if built right.
- May 2025 launch instead of the expected window.
- Timelines moved and team tools still did not have a real plan.
- Wireframes and full design concepts were on the table.
- Team and camp tools did not compete with the current app.
- Ideas matched Trosky-style programs that already worked.
- Another year was effectively lost.
- The expectation was still a team-tool solution that made sense for everyone.
- Keep the point tight: the promise kept moving.
- The concept shifted from delayed to not being built.
- That is the core product-promise issue.
Big Picture: The team-tool concepts were not random extras. They were practical, high-demand add-ons tied to camps, teams, and proven baseball-development workflows.
Timeline statements are PTB concept notes, not independent public-source proof.
Public web source titles below are live links. PTB concept notes stay separated from public proof. App Store rechecked July 15, 2026.
Apple
App Store
Release Proof: public version history plus current $214.99/$215 yearly price context.
Clutch
$40k-$200k+
Benchmark: simple-to-complex consumer app build context and agency-rate pricing.
GoodFirms
$5k-$20k+
Benchmark: annual maintenance range for most apps, used as operating-cost context.
Upwork
$25-$80/hr
Rate context: experienced mobile developer hourly-rate range used to model update workload.
AWS
$100-$1k/mo
Operating context: cloud pricing is pay-as-you-go support, not fixed proof of spend.
D. Deloitte.
15%-25%
Deloitte - Technology Cost Context
Maintenance context: operating and maintenance cost as a share of original build cost.
McKinsey
20%-30%
Velocity context: better tooling can reduce build and update cost and improve iteration speed.
PTB
Concept
Concept Context: timeline narrative, Gold Glove comparison framing, and product-value notes.