Uncategorised decision

The League

A competent developer can reasonably build and run a small gamification app for a single customer; the product doesn't present hidden infrastructure or data moats in the supplied materials.

Visit website

Built by Rohan Gilkes, CFA, who ships 4 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off34 h to build

$20/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 The League alternatives, with the arithmetic →

What a replacement has to do

  • Track cleaning jobs and shifts, award points for completed tasks, update leaderboards, and notify users of rewards and standings.

What it still won’t have

  • Brand recognition and any existing user base
  • Polish of a commercial UX and cross-device tested client
  • Proprietary integrations the vendor may ship (if any)
  • Ongoing product support and SLAs

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

The League 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

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a minimal Cleaning Business Gamification web app using Next.js (React) frontend, Node.js + Express backend, and Postgres for storage. Core features in scope: user/team auth, create/manage jobs/shifts, mark job completion, configurable points/achievement rules, compute and display leaderboards, email/SMS notifications (use a provider API), and an admin UI to edit scoring rules. Out of scope: multi-tenant billing, native mobile apps, analytics dashboards beyond simple counts. Include input validation, error handling, unit tests for scoring/leaderboard logic, and deployment scripts for a single small VPS (Docker + docker-compose).
How we checked3 sources · 2/3 runs agreed · evidence score 86

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 3 cited sources+3
  • Evidence score86

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.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded