Platforms
Five products we run in production, under our own name.
Each of these started as something a client needed and we had already built twice. Running them ourselves — on call for our own outages, paying for our own mistakes — is the fastest way we know to stay honest about what it costs to keep software alive.
They are also the shortest route to seeing how we build. If one of them is close to what you need, we can start from it rather than from an empty repository.
MaverickDineAI-Powered Restaurant Management & Billing PlatformLiveOne connected platform for billing, kitchen operations, inventory, staff, customers, and restaurant intelligence.For restaurant groups running separate systems per location.Hospitality & restaurant techDetails
MaverickHRNext-Gen Enterprise Workforce & Project Execution PlatformLiveA next-generation platform that unifies workforce intelligence, agile project execution, payroll, and attendance in one place.For organisations tracking people in one system and their work in another.ERP & business managementDetails
School Management SystemSchool Analytics & Management SystemA single dashboard for enrollment, fees, and academic performance.For school leadership working from registers and month-old spreadsheets.Education & e-learningDetailsLearning Management SystemCourses, Assessments & Certification PlatformCourses, assignments, exams, live sessions, and certificates — all tracked in one connected learning platform.For anyone running cohorts and self-paced learners on the same platform.Education & e-learningDetailsMaverickLeadLead Management SystemEvery enquiry from first contact to confirmed admission — tracked, followed up, and never lost between counsellors.For admissions teams losing enquiries between call logs, spreadsheets and WhatsApp.Education & e-learningDetailsWhy we build our own
Running our own software changes how we build yours.
- 01
We are on call for these
When one of these wakes somebody up at three in the morning, it is one of us. That tends to concentrate the mind on operability.
- 02
The cost of ownership is not theoretical
We pay for the hosting, the upgrades and the migrations. It is why we argue about schemas before anyone writes a line.
- 03
A head start, when one fits
If a product is close to what you need, the engagement starts from working software instead of an empty repository.
Before you ask
How buying one of these actually works.
- Can we buy one of these outright?
- Usually yes. Most of these are licensed per deployment, and some can be handed over as source with a handover period. Tell us which one and how you would want to run it.
- Can you adapt one to how we work?
- That is the normal case rather than the exception. Starting from a product that is already running removes months of groundwork, and the configuration and integration work happens on top of it.
- What if none of them fit?
- Then we build what you need instead. The products are an illustration of how we work, not the limit of it — custom software is the larger half of what we do.
- Do you keep running it after handover?
- If you want us to. Support, monitoring, security patching and feature work continue as a separate engagement, and you can end it without losing the system.
None of these quite it?
Custom software is the larger half of what we do. Describe what you need and we will tell you whether to start from one of these or from scratch.