Proof library

The work is organised by what broke first.

Pick the pressure — stale site, missed bookings, manual admin — and inspect the named system shipped against it.

Every card has to earn belief.

  1. 01Before
  2. 02System
  3. 03Proof
  4. 04Stage

Search -> booking -> payment -> CRM -> follow-up

Clinic and local-service systems

For owners losing work to stale sites, missed calls, and paper.

IronOx and SWDM show the full path: found, booked, paid, recorded, reported.

Product -> web -> mobile -> sync -> AI -> billing

Founder product systems

For founders who need a shipped product, not a prototype handoff.

Qurannotate: web, iPhone, Android, offline, collaboration, AI, and payments.

CMS -> permissions -> audit -> local AI -> compliance

Sensitive and authority systems

For teams where content, data, or clinical trust cannot be improvised.

UMMATICS (staging), tafsirtool (private AI), and FlapTrack (in talks): publishing, audit, regulated foundations — stage on every card.

Showing work for Founders / 0-to-1 Products

qurannotate.com
Qurannotate — the live web app
Beta

Qurannotate

More moneyMore customersMore timeLower risk

Built for: Faith-tech & Scholarship, Founders / 0-to-1 Products

Before: People who study the Quran had no proper tool built for it. They were stuck using generic note apps that could not handle the depth and structure their work needs, and that lost their work when the internet dropped.

Outcome: One app, used by 1,000+ people in beta, that lets scholars and students mark up the Quran, study together live, keep working with no internet, and get trustworthy AI help. Works on web, iPhone, and Android. Paid plans are live.

System: A serious app for studying and annotating the Quran — like GoodNotes meets Notion — on web, iPhone, and Android.

Proof

Beta users across web, iOS, and Android
1,000+ Beta users across web, iOS, and Android
Simultaneous collaborators per shared mushaf
Up to 30 Simultaneous collaborators per shared mushaf
In development

FlapTrack

Lower riskClearer operations

Built for: Healthcare & Clinical, Founders / 0-to-1 Products

Before: When early signs of a failing flap get missed, surgeries fail. Nurses watch the bedside with paper charts and gut feel, and there's no reliable way to get the surgeon back in time. That's a broken system, not short staffing.

Outcome: A clinical-grade foundation for catching failing flaps before they're lost. The hard engineering is done — patient records, safety rules, and the path to NHS approval — and it's ready for a hospital pilot.

System: Catch a failing surgical flap early — clinical-grade monitoring built to NHS standards from the ground up.

Proof

Schema tables
33 Schema tables
Enum types
42 Enum types