Benchmark ReadApp Store + Model
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.
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.
14 public App Store entries. 13 updates after launch. The story is the 203-day update gap from November 21, 2025 to June 12, 2026 - nearly half of the 14-month launch window.
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.
Release MixRelease Notes
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.
Bottom 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, maintenance, 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
Maintain Today$12-24k/yrAnnual operating model
Maintain Max$60k/yrHigh-end first-year model
Update Today$2-3kTypical minor update
Update Then$4-5kPast high-end max
Update Workload13 post-launch updates model 13-26 developer days - about three work weeks even before bigger features.
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.
Nate's Gold Glove
$297/year
VS
Nate's infield membership included team calendars, 5-Tool Training, College Fit List, and recruiting-system pieces.
Platform context: same Thinkific-style system Greg used for baseball/recruiting work, not the same Gold Glove product.
Trosky 365
$215/year
Current public pricing is $19.99/month or $214.99/year, rounded here to $20/month or $215/year.
That is about $57-82 less than a $297 Gold Glove year, depending on monthly versus yearly comparison.
Price timeline scroll sideways ->
Concept notes say the app was marketed around $500 with no discount, before the product had proven depth.
The concern was on the table while launch timing and team-tool expectations kept moving.
The public App Store listing now shows $19.99/month and $214.99/year.
The lower price does not erase the smaller feature set, team-tool gap, or flexibility issue.
Timeline moves left to right swipe / scroll ->
- 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.
Demand context: the team side was described as 2-3x growth over the last year, with Nate's camps still strong and steady demand for uniforms, apparel, academy programs, and college recruiting. That makes the missing team-tool path look worse, not better.
Apple
App Store
Release Proof: 14 public entries plus $19.99/month and $214.99/year pricing.
Clutch
Avg $90k
Benchmark: reviewed mobile app projects average around $90k, with buckets reaching six figures.
GoodFirms
15%-25%
Benchmark: maintenance/support can run 15%-25% of original build cost.
Upwork
$160-$4.5k/mo
Maintenance context: post-launch work can run $160-$4.5k per month.
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, Nate's Gold Glove comparison framing, and product-value notes.