Health, home and travel decision

PeptidePilot: Peptide Tracker

A competent developer can reimplement the core calculators and a local iOS logger (the most valuable user workflow) in a few weeks, but matching the production polish, per-peptide content, and App-Store UX of the existing product would take additional time and ongoing effort.

Visit website
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-off56 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

  • Open app → log a dose tied to a vial → app decrements vial inventory, updates streak and weekly summary → view weight trend and export CSV.

What it still won’t have

  • iOS App store polish and ongoing UX improvements from a maintained product
  • Pre-written per-peptide reference pages and pre-filled examples
  • Brand trust and existing user convenience
  • Quality-of-life refinements (streak timezone edge-cases, visual polish, documentation)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

PeptidePilot: Peptide Tracker 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 Peptide Pilot replacement: use React for a responsive web UI (create-react-app or Vite) and SwiftUI for a native iOS app that share calculation logic ported into a small TypeScript module and a Swift copy. Core features in scope: (1) four client-side calculators (reconstitution, dose, mg↔units, vial duration) with unit tests; (2) an iOS app that stores doses, vials, weights, meals in on-device storage (Core Data or SQLite) with no server or account; (3) dose logging UI that timestamps entries, attaches to vials, decrements inventory, and updates a streak; (4) weekly smoothed weight trend chart and a simple site-rotation visual; (5) CSV export and account deletion that clears local storage. Out of scope: user accounts, server-side backups, analytics, third-party integrations, and paid tiers. Require error handling for invalid numeric inputs, timezone-aware timestamps, CSV generation, and automated tests for calculators and core storage flows.
How we checked1 sources · 3/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 3/3 assessment runs agreed+4
  • Evidence score56

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.

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