Health, home and travel decision

Fake It Till You Make It

A single competent developer can build and maintain a minimal replacement in about a week; the product is a small, single-purpose app with no evident durable moats and no public pricing to block self-hosting.

Visit website

Built by Marc Lou, who ships 32 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-off36 h to build

$0/mo1 h/mo upkeep

No published price to break even against.

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

  • Configure a product and price → generate a sequence of fake Stripe-like sale events → deliver them as local notifications (or via a demo UI) → adjust tempo and content

What it still won’t have

  • Polish, cross-platform installers, and QA that a paid app would have
  • Built-in demo content, UX refinements, and ready-made templates
  • Marketing, support, and legal/terms/abuse handling provided by the vendor

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Fake It Till You Make It 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 single-user macOS Electron app with a Node.js backend and SQLite for local persistence. Core features in scope: generate realistic Stripe-like sale payloads with templating and randomized buyer data; schedule emission of hundreds of notifications at configurable intervals; render a web-based demo UI inside the app showing incoming notifications; push native macOS notifications via node-notifier or native modules; store settings (product price, template selection, cadence) in SQLite and expose import/export of settings. Out of scope: remote multi-user syncing, Windows/Linux packaging, analytics dashboard, payment collection. Include input validation, error handling, unit tests for payload generation and scheduling, and packaging instructions for notarized macOS distribution.
How we checked3 sources · 3/3 runs agreed · evidence score 85

How the score was reached

  • Build verdict base78
  • 3 cited sources+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 · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded