Sports Prop Hit-Rate Dashboard
Budget: $30 – $250 AUD
I need a small web app that pulls real-time player-prop feeds from an API and instantly shows me which legs have been cashing most often, ranked from highest to lowest hit percentage.
Scope of the data
• Sports: Football, Basketball, baseball, soccer and australian rules football.
• Props: Points scored, rebounds or yardage gained, goals, disposals ,assists or passes completed—plus any other categories the feed makes available.
Core workflow I have in mind
1. Your back-end service pings the API at a reasonable interval, stores the incoming props and their outcomes, and calculates historical hit rates.
2. The front-end presents a clean, sortable table where I can filter by sport, prop type, player, or team, then instantly see the percentage chance each leg has hit in the past.
3. Clicking a row should open a quick modal or sub-page that graphs recent performance so I can verify the trend.
Tech preferences
I’m flexible, but I expect modern tooling (e.g., Node/Express or Python/FastAPI for the server, React/Vue/Svelte for the UI, and a lightweight database such as PostgreSQL). If you have a better stack for fast data pulls and snappy tables, pitch it.
Acceptance criteria
• Automated API ingest with basic error handling and rate-limit respect.
• Percentages refresh at least once per hour.
• Table defaults to “best hit rate first” and re-orders instantly when filters change.
• Deployed to a live URL I can test, with source code handed over at completion.
Let me know the API you’d like to use, roughly how long you’ll need, and any hosting considerations I should prepare for.
Scope of the data
• Sports: Football, Basketball, baseball, soccer and australian rules football.
• Props: Points scored, rebounds or yardage gained, goals, disposals ,assists or passes completed—plus any other categories the feed makes available.
Core workflow I have in mind
1. Your back-end service pings the API at a reasonable interval, stores the incoming props and their outcomes, and calculates historical hit rates.
2. The front-end presents a clean, sortable table where I can filter by sport, prop type, player, or team, then instantly see the percentage chance each leg has hit in the past.
3. Clicking a row should open a quick modal or sub-page that graphs recent performance so I can verify the trend.
Tech preferences
I’m flexible, but I expect modern tooling (e.g., Node/Express or Python/FastAPI for the server, React/Vue/Svelte for the UI, and a lightweight database such as PostgreSQL). If you have a better stack for fast data pulls and snappy tables, pitch it.
Acceptance criteria
• Automated API ingest with basic error handling and rate-limit respect.
• Percentages refresh at least once per hour.
• Table defaults to “best hit rate first” and re-orders instantly when filters change.
• Deployed to a live URL I can test, with source code handed over at completion.
Let me know the API you’d like to use, roughly how long you’ll need, and any hosting considerations I should prepare for.
Related categories:
PHP
JavaScript
Software Architecture
HTML
Node.js
PostgreSQL
Web Development
API Development