Uncategorised decision

São Miguel Bus

A single developer can build and operate a minimal ad-slot booking site for local ads in about a week; the product's value is primarily distribution and brand, not technical moat.

Visit website

Built by Sousa, who ships 5 products in this index

You pay

$5/mo

$60/yr

Read off the official pricing page.

You’d pay instead

$50one-off30 h to build

$15/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 4 seats.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Users reserve an ad slot via a web form → payment is collected → ad assets and metadata are stored → admin schedules and approves slots → API serves active ads to the app

What it still won’t have

  • Existing audience / distribution and brand recognition
  • Built-in users and any app-level ad placements
  • Polished design, ongoing customer support and marketing
  • Any bespoke integrations the vendor may have with local payment or accounting systems

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 4 seats.

Paid seatsseats

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 ad-slot booking web app using Django, PostgreSQL, Celery, and an S3-compatible object store (DigitalOcean Spaces or AWS S3). Core features in scope: (1) public booking form with image upload and text fields, (2) Stripe payment integration for single-slot purchases and receipt emails, (3) Postgres models for slots, bookings, advertisers and assets, (4) admin UI to approve/reject bookings and mark slots as active/inactive, (5) background image processing (resize/compress) via Celery, (6) authenticated REST endpoint returning active banners for the mobile app. Out of scope: native mobile client, multi-tenant billing, advanced analytics, and marketplace features. Deliver runnable Docker compose files, environment config, unit tests for models and API endpoints, basic end-to-end test for booking+payment flow, and error handling for uploads, payment failures, and background job errors.
How we checked1 sources · 3/3 runs agreed · evidence score 85

How the score was reached

  • Build verdict base78
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score85

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 · 1

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded