What we have built, and the kind of work we take on
Most of what we build lives behind a login, which makes a traditional gallery of screenshots fairly useless. What follows is an honest account of our flagship platform, which anyone can go and look at, followed by descriptions of the categories of work we deliver regularly so you can judge whether your project resembles them.
QuranRecord, built here and still operated here
QuranRecord is a complete school management platform for Quran education. It is used by schools, madrasas, mosques, private teachers and families across many countries, it handles more than a million page views a month, and it exists on the web, on Android and on iOS. It is provided free to every school that uses it, with no advertising and no premium tier holding back the features that matter.
Everything in it came from this company. The Django backend and the MySQL schema that stores years of recitation and attendance records. The REST API that feeds both mobile applications from one set of business rules. The native Android client written in Kotlin and the native iOS client written in SwiftUI. The Celery workers and Redis cache that let thousands of notifications go out without a page ever slowing down. The Firebase messaging infrastructure. The Linux servers, the certificates, the backups and the monitoring. The app store listings and the review submissions. The support replies that go back to school administrators.
We mention it constantly for one reason. Any development company can describe a technology stack. Very few can point at a system of that size, say they designed every layer of it, and then confirm they are still the ones keeping it running today.
Modules inside the platform
The projects we deliver again and again
Client work is confidential unless we are given permission to discuss it, so the descriptions below are written as project types rather than named case studies. Each one reflects work we have genuinely delivered, repeatedly, over eighteen years.
Business websites with content management
A company needs a site that explains what it does, loads quickly on a phone, appears in search results and can be updated by someone in the office without calling a developer. These projects cover structure and copy planning, responsive design, content management, contact and enquiry handling, search fundamentals and analytics.
The success measure is simple. Six months later, is the site still being updated by the client, and are enquiries arriving from people who found it through search?
Internal business systems
The most common request we receive. A company has outgrown a spreadsheet that three people edit at once, and needs a proper system with accounts, permissions, validation and history. Typical builds cover job or case tracking, approvals, scheduling, inventory, document handling and reporting for management.
These projects live or die on adoption, so the daily entry screens receive far more design attention than the management dashboards that get looked at once a month.
Customer and member portals
A secure area where customers, members or partners can log in to see their own information, submit requests, download documents, update details and track progress. These reduce telephone and email volume dramatically, which is usually the reason they are commissioned.
The technical heart of these builds is the permission model, because the cost of showing one customer another customer data is far higher than the cost of the entire project.
Native mobile applications
Android applications in Kotlin and iOS applications in SwiftUI, usually built because the people who need the system are not sitting at desks. These include field data capture, job sheets, notifications, offline tolerant flows and everything required to publish and maintain a listing on both stores.
Publishing is only the start. Each platform raises its requirements every year, and an app that is not maintained will eventually be removed from sale.
Online stores and ordering systems
Ecommerce builds covering catalogue, search, checkout, payment integration, shipping and tax rules, discount handling, stock control and order management for staff. Some are public stores and others are trade ordering portals where pricing differs by customer.
Speed is treated as a commercial requirement here, because a slow checkout on a mobile connection loses orders quietly and continuously.
Rescue and modernisation projects
A system exists, it matters to the business, and the people who built it are gone. We assess the code, the database and the server, produce a written report on what is sound and what is dangerous, then either stabilise it, extend it or plan a staged replacement that keeps the business running throughout.
These arrive more often than any other kind of enquiry, and the honest assessment at the start is the most valuable part of the engagement.
Artificial intelligence features inside existing software
Adding language model capabilities to systems that already run a business, such as an assistant that answers questions from internal documents, a classifier that routes incoming enquiries, or a drafting tool for repetitive correspondence. Built with platforms including Claude and DeepSeek.
The engineering effort sits in the guardrails, the data access and the logging rather than in the model itself, which is the part most people underestimate.
Infrastructure and hosting migrations
Moving applications onto properly configured Linux servers with NGINX, Gunicorn, Redis, background workers, certificates, firewalls, offsite backups and monitoring. Often triggered by an outage, an expiring certificate or a hosting company that stopped responding.
Migrations are rehearsed against copies until the result is clean, and there is always a documented route back before anyone touches production.
Why we do not publish a wall of client logos
Plenty of agencies fill a page with logos, and some of those relationships amount to a single small invoice from six years ago. We take the view that client work is confidential by default. Many of the systems we build are internal tools that a company would rather competitors did not know exist, and a portal behind a login cannot be shown as a screenshot without exposing real data.
What we will do, at the point where you are seriously considering working with us, is arrange a private demonstration of relevant work where the client has agreed to it, and put you in touch with people who can speak about what it was like to work with us over several years rather than several weeks. That conversation is far more informative than a logo grid.
In the meantime, QuranRecord is available for anyone to inspect. It is the most complete answer we can give to the question of whether we can design, build, deploy, scale and support a serious platform, because every part of it is ours and it is running right now.
Does your project look like one of these?
Tell us what you are trying to build or fix. We will say plainly whether it is the kind of work we do well, and what a realistic scope and schedule would look like.