← Back to all projects

ShuleYetu — WhatsApp-First School Management

A multi-school Django platform that brings school-fee enquiries, M-Pesa payments, receipts and announcements into WhatsApp. School teams manage students, parents, enrollments, fee structures and payment records from a role-aware admin dashboard. Parents don't need to install another app.

Client
Own product
What I did
Product design, Django application architecture, admin workflows, WhatsApp automation, M-Pesa integration, payment and receipt processing, debugging and testing.
Year
2026
Status
Core product complete, additional development and piloting in progress
ShuleYetu admin dashboard

The problem

Fee enquiries, statements, payment confirmations and school announcements can create a steady stream of manual work. Staff need to identify the right student, confirm what has been paid, allocate money correctly and get the information back to the parent without losing track of conversations or receipts.

The same issue also arises with sending payment receipts, annouceents, fee changes, and other important information. Parents also have to reach out to staff if they want to know whats happening in the school.

In Kenya, WhatsApp is a familiar communication channel and M-Pesa is a familiar way to pay. ShuleYetu connects those everyday tools to a school's underlying student, billing and payment records, reducing the need to move between disconnected manual processes.

What I built

A school inside WhatsApp

Parents message their school's WhatsApp number and get a simple menu, using list and reply buttons as well as typed options. They can identify themselves, link their children, check a fee balance, request a fee statement, information or school announcement without leaving the chat.

M-Pesa fee payments

Paying fees triggers an M-Pesa STK push straight to the parent's phone through Safaricom's Daraja API. Once the payment is confirmed, the parent gets a receipt on WhatsApp and the school sees the payment recorded against the right student.

Parents also have the option of paying via M-pesa paybill with debit and credit card payments coming soon. The management system uses the parent's phone number and student's admission number to align and allocate payments.

Multi-school by design

Many schools run on one system. Each school has its own WhatsApp number, so the number a message arrives on identifies the school. Staff accounts are tied to a school through memberships with roles such as admin, finance and staff, so people only see and edit their own school's data. Only a super admin sees across schools.

Student and parent management

Students, parents, enrollments, grades, terms and academic years are managed in the admin. A parent can be linked to several children, and parents can be selected right from the student form.

Conversations and enquiries

Every conversation and message is recorded. Messages from numbers that aren't registered are stored as prospects for the receiving school, since they are often new parents looking for a place.

Announcements and support

Schools can send announcements to all parents, specific parents, or parent whose children are in a specific grade on WhatsApp, a channel they already read, and parents can ask questions or request help without phoning the office.

School admin dashboard

Built on Django Unfold, giving school staff a modern admin for fees, payment tracking, parent communication and basic reports without a custom back office.

Grade-based fee structures

Fee structures are associated with a grade and academic period. The admin workflow makes the structure visible alongside grade details and enrolled students, while billing services apply charges to eligible enrollments with duplicate-charge prevention as a key invariant.

Payment records and receipts

The payment workflow connects a confirmed M-Pesa transaction to the relevant student account and allocation, then creates a PDF receipt and tracks receipt notification separately from the payment.

Webhook and transaction handling

WhatsApp events and Daraja callbacks are handled as distinct integration paths. Development has covered cancelled STK requests and failed payment states, while idempotency, reconciliation and recovery from interrupted processing remain part of hardening.

ShuleYetu WhatsApp menu
WhatsApp parent interaction
ShuleYetu fees admin
School fees flow

How it's built

Why WhatsApp and M-Pesa first

A new app asks parents to install software, remember credentials and learn another interface. WhatsApp provides a familiar entry point, while M-Pesa supports the payment step. ShuleYetu connects these channels to structured school records rather than treating messages and payments as isolated events.

This version of the software is intentionally focused on the operational journey tht includes identify the parent and student, retrieve fee information, initiate payment, process the provider's result, record the payment and issue a receipt. That creates a testable foundation before expanding into a broader school ERP.

Multi-school architecture

ShuleYetu is a Django project organized around school, student, academic, billing, payment, document and WhatsApp responsibilities. A custom email-based user model can be linked to schools through memberships and roles. Admin querysets are scoped to the staff member's school, and school ownership is populated by the application where appropriate. A super administrator can work across school boundaries.

WhatsApp and payments

The bot receives WhatsApp Cloud API webhook events and uses conversation state to track the current step and selected student. It can respond with numbered options, interactive lists and reply buttons. Conversations and individual messages are persisted, and unregistered senders can be retained as prospects instead of disappearing as unmatched inbound traffic.

Fee payments use Safaricom Daraja STK Push to prompt the parent's phone. The callback is the provider's result signal since the application records success or failure and links confirmed payments to the appropriate allocation.

A receipt document and a receipt-notification record are separate concerns, so a WhatsApp delivery problem should not undo a confirmed payment.

Billing and payment lifecycle

The payment path is designed as a sequence of explicit records, with the path including an initiated transaction, a provider callback, a confirmed payment, a student-account allocation, a PDF receipt and a WhatsApp delivery attempt.

This separation makes it possible to investigate where a flow stopped without confusing a successful payment with a failed notification.

The project also includes a shared confirmed-payment service so STK and Paybill/C2B payments can reuse the same allocation and receipt logic.

Admin workflows that reflect school operations

Django Unfold provides the operational interface. Grade pages bring together enrolled students and fee structures.

Student enrollment views show admission numbers in read-only form and fee structures are managed against the relevant grade and term.

Applying a new fee structure is handled through billing services, with duplicate-charge prevention treated as an important invariant.

  • Python
  • Django
  • Django Unfold
  • WhatsApp Cloud API
  • M-Pesa Daraja
  • PostgreSQL / SQLite development
  • PDF receipt generation
  • Webhook processing
  • Structured logging

Where it stands

Piloting stageCore parent journey built and tested against the Daraja sandbox and deployed to one school
Fees → Payments → CommunicationThe order the product is being built and validated in
1 → 5 → 20 → 100+The target path from one pilot school to a network of schools
Parents don't need another app. We bring the school to the parent through WhatsApp, with M-Pesa integrated into the experience.The idea behind ShuleYetu

Need a similar website, platform or tool for your business?

Tell me what you're building and I'll reply with next steps.

Start a project

Frequently Asked Questions

Getting started
What information do you need from me to get started on a project?

I typically need a clear description of your project goals, target audience, any design preferences, technical requirements, and timeline expectations.

The more details you can provide, the better I can tailor my approach.

For larger projects, I'll provide a detailed questionnaire to help you articulate your vision.

I'm also happy to schedule an initial consultation call to discuss your needs more thoroughly.

Schedule a Consultation
Have you worked with businesses in my industry before?

I've worked with clients across diverse industries including healthcare, real estate, digital marketing, and others.

While each industry has unique requirements, my experience has taught me how to quickly adapt to different business domains.

For industries new to me, I invest time in research to understand your specific challenges and standards.

My portfolio includes examples of past work that demonstrate my versatility across sectors.

Contact Me
Project Planning and Execution
How do you prioritize features when working within budget constraints?

I use a value-driven approach to feature prioritization.

We'll collaborate to identify "must-have" versus "nice-to-have" features based on your business goals and user needs.

I will then implement core functionality first, then add enhancements as the budget allows. This approach ensures you get a functional product that delivers value, even with limited resources.

I'm transparent about what's achievable within your budget and can suggest phased implementations if needed. Please contact me to discuss this further

Contact Me
How long does a typical project take from start to finish?

Project timelines vary based on complexity and scope.

Simple websites typically take 1-2 weeks, while more complex web applications may require 1-3 months. E-commerce solutions generally take 1.5-3 months depending on customization needs.

After our initial consultation, I'll provide a detailed timeline with key milestones. I'm committed to meeting agreed-upon deadlines while maintaining quality standards.

How do you communicate progress throughout the development process?

I believe in transparent, consistent communication.

You'll receive weekly progress updates for longer projects and daily progress updates for shorter ones via email, and we'll have scheduled check-in calls at key milestones.

I also use project management tools that give you visibility into task completion and upcoming work. This approach ensures you're always in the loop.

For day-to-day communication, I'm available through your preferred channel (email, Discord, Slack, etc.). My goal is to keep you informed without overwhelming you with technical details unless neccessary.

Contact Me
Timelines and pricing
What is your pricing structure? Do you charge hourly, fixed-price, or use another model?

Add your typical timelines here, for example a custom theme in 3 to 5 weeks and a web application in 6 to 12.

How is pricing set?

I offer flexible pricing options tailored to your project needs:

  • Fixed-price contracts for well-defined projects with clear requirements
  • Hourly rates for exploratory work or projects with evolving scopes
  • Retainer arrangements for ongoing development needs

For most client projects, I prefer fixed-price agreements as they provide budget certainty.

After our initial consultation, I'll recommend the most appropriate pricing model and provide a detailed proposal.

All pricing options include regular milestones and deliverables to ensure transparency.

How do you handle change requests during a project?

I understand requirements can and do evolve as projects progress and minor adjustments are accommodated within the original agreement.

For substantial changes, I'll assess the impact on timeline and budget, then provide you with options before proceeding.

I document all change requests and maintain a change log that's accessible to you. This approach ensures transparency while allowing flexibility for your evolving needs.

Support and Maintenance
What is your availability for ongoing maintenance and support after project completion?

I offer several post-launch support options:

  • A 30-day warranty period for all projects to address any immediate issues
  • Monthly maintenance packages for regular updates and minor improvements
  • Priority support agreements for business-critical applications
  • Ad-hoc support at my standard hourly rate

I recommend discussing maintenance needs early in the project planning phase so we can build with long-term support in mind. My goal is to ensure your solution remains secure, performant, and up-to-date.

What's your process for handling urgent issues or emergency fixes?

For clients with support agreements, I provide a dedicated channel for reporting urgent issues with guaranteed response times (typically within 1-4 hours depending on your support tier).

For clients without support agreements, you can contact me at anytime and we will schedule a time to discuss the issue. My availability is flexible and I'll do my best to respond within one business day.

Do you offer any guarantees or warranties on your work?

Yes, all my work comes with a 30-day warranty period after project completion. During this time, I'll fix any bugs or issues at no additional cost.

I also guarantee:

  • Code that follows industry best practices
  • Cross-browser compatibility as specified in our agreement
  • Responsive design for mobile devices
  • Adherence to accessibility guidelines
  • Secure coding practices

My contracts clearly outline what's covered under warranty and what would constitute billable changes or enhancements. Contact me if you need further clarification or have a question about these guarantees.

Contact Me

Let's work together

Tell me what you're building and I'll reply with next steps.