The Crescent Core
Plan

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.

IronOxSWDM

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.

Qurannotate

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.

UMMATICStafsirtoolFlapTrack

Showing work for CMS & Publishing Systems

On staging

UMMATICS

More timeLess adminClearer operationsMore money

Built for: Faith-tech & Scholarship

Before: The think-tank's old site couldn't handle real academic publishing — proper writing tools, a clear approval process, a careful move of years of past work, or a reading experience worthy of the scholarship.

Outcome: A think-tank that can publish serious scholarly work the way it should look and read — with proper academic writing tools, a clear approval process, and every old article moved across safely. Built new from the ground up.

System: A custom publishing platform for an Islamic think-tank — built to replace a worn-out old site that could never carry serious academic work.

Proof

Custom Lexical editor features
11 Custom Lexical editor features
Content types in the system
18 Content types in the system
See the full system