Book a Systems Review ↗
Case study
Lagos Business School previously relied on email, Excel, paper forms, separate payment tools and manual committee handoffs across parts of the student and programme journey. Nadmaa designed and delivered a connected platform spanning applications, governed admissions, registration, payments, documents, student self-service and management visibility.
The operating problem
Email, Excel, paper forms, separate payment systems and manual committee review created handoffs between application intake, academic decisions, finance, documents and student support. Information could be reassembled as the same person moved through different teams.
How do you capture information once, preserve human academic judgement, connect the financial and document steps, and give applicants and students a clear place to complete actions without turning every stage into another follow-up?
The connected education journey
Built around institutional rules
The goal was not to automate academic judgement. It was to make the surrounding process consistent, traceable and easier for applicants, programme teams, finance and management to operate.
Executive Education and MBA-style admissions follow distinct stage maps with role checks, comments, checklists and controlled transitions. Applicants move through the process without reducing committee or academic decisions to a simple automatic status change.
Multistep applications capture personal, education, professional and billing information with validation and signature requirements before submission, giving staff a consistent operating record rather than a loose form response.
Open-seminar registration connects participant details, agreements and commercial records so a completed registration can continue into invoice, payment, executed documents and programme activity instead of becoming another isolated web lead.
Beyond admissions
Live Paystack payment flows connect transaction verification to the financial record, while wallet and virtual-account capabilities support additional payment and allocation journeys.
Applications, admission letters, executed agreements, receipts and paid document-request outputs are generated or managed from the same underlying records.
Applicants and students can return to one portal for applications, programme activity, invoices, receipts, agreements, document requests and wallet information.
Document services have their own request, payment and fulfilment states so service teams can manage the work without separating the commercial step from the request.
Admissions, programme teams, finance and administrators work from structured stages, linked records and configuration rather than reconstructing the journey across separate files.
Stage age, milestone timing, invoice value, amount paid, outstanding balance and progression flags can be surfaced from the operating data without rebuilding another manual report.
What changed
Email · Excel · Paper forms · Separate payment tools · Manual committee handoffs · Repeated follow-up
Application → Review → Committee decision → Invoice → Paystack → Admission / enrolment → Documents → Student portal → Reporting
The improvement was not replacing human judgement. It was connecting everything around that judgement so the institution no longer had to rebuild the learner journey at every handoff.
The Nadmaa approach
Led by Andrew Ukegbu, Nadmaa mapped the admissions pathways, decision points, payment states, documents, roles and student-facing actions before translating them into workflows. The technology supports the operating model instead of forcing the institution to work around the software.
Fix the process. Connect the systems. Build what's missing.
Where is your operation still being rebuilt by hand?
You do not need to know the technology answer. We can map the workflow with you and identify what is worth fixing first.