Rebuild App "Wagr": Sports Betting Model-Builder

Summary
I’m rebuilding an app called Wagr — a sports betting model-builder and tracking app (not a picks app).

I’ve already validated demand:

120+ users in 5 days
100% organic (Reddit)
No ad spend

The current version was built quickly using a no-code tool and is now hitting stability limits. I’m looking for an experienced engineer to help rebuild this properly.

This is a real product with real users — not a spec idea.

What We’re Building

Wagr lets users:
Build their own betting models by defining rules/parameters
Only generate a bet when all rules qualify
Track results (wins, losses, units, ROI)
Compare performance via leaderboards
Get AI-assisted insights to improve models over time

Here's our current MVP: https://wagr.base44.app

Here's the 1 current competitor: https://apps.apple.com/us/app/rithmm-ai-sports-betting/id1641010681

Important:
This is NOT a picks or “lock of the day” app.

What I’m Looking For

You might be a good fit if you:
Have 3+ years of experience building SaaS apps
Are backend-strong (logic, data models, APIs)
Care about correctness and scalability
Can work independently and communicate clearly
Are comfortable shipping MVPs and iterating

Nice to have (not required):
Experience with fintech, analytics, or betting
Experience designing rule-based systems
Familiarity with Supabase / Firebase / Postgres / Node / Python

Not a fit if you:
Are an agency
Only want short-term throwaway work
Don’t like owning logic-heavy systems

Initial Scope (MVP Rebuild)

User authentication
Model creation (rules, thresholds, filters)
Deterministic bet-qualification logic
Bet tracking (W/L, units, ROI)
Public leaderboard
Clean, stable backend
Frontend can be simple — correctness over polished.

Engagement Structure

This can be one of two paths, depending on fit:

Paid Milestones (Preferred to Start)

Small, clearly defined milestones
Modest budget (not a large contract)
Clean handoff & documentation

Option 2: Ongoing Partner

For the right person:
Continued involvement post-launch
Only discussed after initial build progress

Why This Is Interesting
Real users already
Clear differentiation (models over picks)
Strong growth potential
Founder handles growth, creators, monetization
You own the technical foundation

How to Apply (Important)

Please include:
A brief note on your backend experience
One example of a system you’ve built with complex logic
Whether you’re open to long-term involvement (optional)
Generic applications will be ignored.

Next Steps
Short intro call → scope alignment → start immediately.

Final Note
I’m not looking to outsource this and disappear — I’m building something real and want someone who takes pride in what they ship.