CRM and sales decision
My Requests App
A small hosted requests app for clubs is realistic for a single technical person to reimplement and run; there are no evident durable moats on the public page and useful prior-art CRMs exist to accelerate work.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off27 h to build
$40/mo3 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All My Requests App alternatives, with the arithmetic →
What a replacement has to do
- Collect requests from club/agency users, store them, notify staff, and let staff triage and respond via a simple admin UI.
What it still won’t have
- Hosted, turnkey service and vendor support
- Any football-specific productisations or prebuilt workflows
- Unknown proprietary integrations the vendor may provide
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
My Requests App does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted 'Requests for Clubs' app using Node.js (Express) backend, React admin UI, PostgreSQL, and SendGrid for email. Core features: user auth with roles (player, staff, agency), request submission form with file attachments, REST API and DB models for requests/users, admin dashboard with list/filter/sort/update status, email webhook notifications for new/updated requests, basic RBAC and input validation. Out of scope: multi-tenant billing, mobile-native apps, advanced analytics. Include error handling, input validation, and unit tests for API endpoints and critical UI flows.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score90
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productMy Requests — Football Platform for Clubs and Agencies
- open sourcehitobito/hitobito
- open sourcekrayin/laravel-crm
Integrity checks
What held up, and what did not.
