Skip to content
Selected project

Case study · Education & publishing

ClimaxPrime

Connecting schools, publishing teams and business operations.

Category
Business management platform
Industry
Education & publishing
Platforms
School & customer portal · Staff workspace · Writer & editor portals
Technology
Laravel · Vue · Inertia · MySQL · M-Pesa

01 · Project overview

What was built, and for whom.

ClimaxPrime is a business management and education publishing platform built by CodeWave for Climax Prime. Schools can browse books, request custom exam papers, pay through M-Pesa and access their orders. Behind the portal, staff manage sales, customer relationships, exam production, warehouse fulfilment and finance, while writers and editors work through dedicated role-based portals.

Built for
Climax Prime, an educational books and exam publishing business
Type
Selected project
Platforms
School & customer portal, Staff workspace, Writer & editor portals
Focus
education erp ecommerce payments web

02 · Business challenge

The problem, as the business experienced it.

Book sales and custom exam production involve schools, sales staff, writers, editors, warehouse teams and finance, each needing a clear view of their part of the order.

A book order and a custom exam request take different paths. The platform needs to support both: stock and fulfilment for books, and writing, marking schemes and editorial review for exams, with the right access for each team.

  • Schools need one place to order books and request custom exam papers
  • Writers and editors need a coordinated exam production workflow
  • Sales and warehouse teams need order visibility appropriate to their roles
  • Customer payments and finance records need to stay connected to operations

03 · Our approach

How we got from the problem to the system.

CodeWave built a Laravel and Vue platform joining a school-facing shop and exam request portal with order management, ExamFlow publishing workflows, CRM, warehouse operations and finance.

  1. 01

    Separate roles and responsibilities

    Structured access around customers, sales staff, managers, writers, editors, warehouse staff and accountants.

  2. 02

    Build the school portal

    Connected the book catalogue, basket, exam requests, customer orders, M-Pesa payments and downloadable documents.

  3. 03

    Connect the publishing workflow

    Built ExamFlow tools for exam orders, writer assignments, paper preparation, marking schemes and editorial work.

  4. 04

    Bring operations together

    Linked order management with CRM, warehouse fulfilment, payment records, finance and management dashboards.

04 · Solution architecture

Layers of the system.

Clients at the top, the core application in the middle, integrations and data underneath. Green marks the integration layer where the system meets the outside world.

05 · Key features

What the system does.

School & customer portal

Browse books, request exams and follow orders through a dedicated account.

ExamFlow publishing

Coordinate exam papers, marking schemes, writer assignments and editorial review.

Customer & sales management

Keep customer relationships, sales activity and order records in the staff workspace.

Warehouse & fulfilment

Manage book stock and fulfilment with access for warehouse managers and assistants.

Payments & finance

Connect M-Pesa payments, customer documents and finance workflows to business operations.

Role-based workspaces

Give schools, writers, editors and internal teams access appropriate to their responsibilities.

06 · Technology

The stack behind it.

Chosen for the job — mature, supportable and straightforward to host and staff for in Kenya.

Backend
PHP Laravel
Frontend
Vue Inertia Tailwind CSS
Data
MySQL
Integrations
M-Pesa PDF generation Spreadsheet import & export

07 · Business impact

What changed for the business.

Outcomes are described qualitatively. Figures are published only when verified by the client and approved for release.

  1. 01

    Schools can access book orders and custom exam requests through one portal

  2. 02

    Writers and editors have dedicated publishing workspaces

  3. 03

    Sales, warehouse and finance work from connected business records

  4. 04

    Permissions reflect each team's operational responsibilities

08 · Screens

Interface illustration.

A representative illustration of the interface, not a live screenshot — no client data is shown.

Similar problem?

Have a process that looks like this one?

Tell us how it runs today. We will tell you what a system built for your operation would involve.