Building Mawared: An Egypt-Focused HR and Payroll Platform

Essam Abd Elmaboud — Sun, 01 Nov 2026 20:14:21 +0000

I recently completed Mawared, a cloud-based HR platform designed around the day-to-day needs of companies in Egypt.

The idea came from a common operational challenge: employee records, attendance, leave requests, approvals, expenses, and payroll calculations can easily end up spread across spreadsheets and disconnected processes. When information is separated, it becomes harder for HR teams and managers to track what is happening and understand how one process affects another.

Mawared brings these workflows together in one connected system.
A connected view of HR operations
The platform is designed around several core areas:

Command Center: A dashboard for tracking attendance, payroll readiness, and operational exceptions.
Employee profiles: A central employee record connected to the company’s branches, departments, job titles, financial details, and documents.
Attendance and shifts: Attendance tracking with shift rules, grace periods, and GPS-based geofencing.
Approvals and leave management: A unified workflow for leave requests and other employee approvals.
Finance and expenses: Tools for managing advances, installments, expenses, and company custody items.
Governance and audit history: Role-based permissions and an audit trail to make actions and changes traceable. The goal is to make these modules work together instead of treating each one as a separate tool. Payroll designed for the Egyptian context Payroll was one of the most important parts of the project. The system’s payroll workflow accounts for items such as salary components, attendance-related deductions, advances, insurance, and income tax.

A payroll simulation helps make the calculation easier to follow by showing how the final net salary is reached. The design also includes a payroll readiness check to help identify missing or unresolved data before processing a payroll run.

Once a payroll period is locked, its records are protected from direct changes. Later adjustments can be handled as recorded settlements, keeping a clear history of what changed and when.

The platform also includes export formats for salary transfers to Egyptian banks, including CIB, QNB, National Bank of Egypt, and Banque Misr.
What I learned
Building Mawared pushed me to think beyond individual screens and features. The bigger challenge was connecting the workflows:

How can attendance exceptions affect payroll?
How can an HR manager spot missing information before payroll is processed?
How can approvals, expenses, and employee records remain traceable?
How should the product support companies with multiple branches? Working through these questions helped me think about the product from the perspectives of employees, HR teams, finance teams, and company managers.

Mawared is a project about bringing everyday HR operations into one clearer workflow, with the needs of the Egyptian market in mind.

If you were building an HR platform for your market, which manual process would you automate first
demo: https://mawared-alpha.vercel.app/

SaaS vs Traditional Software: Which One Should You Actually Build?

Essam Abd Elmaboud — Tue, 25 Aug 2026 13:14:00 +0000

If you're starting a new project, this question will hit you sooner or later:

Should I build a SaaS product, or a traditional (on-premise) system?

It's not just a technical choice — it shapes your revenue model, your infrastructure, and how much flexibility you'll have as the product grows.

Let's break it down.

Traditional Software (On-Premise)

The client owns the system outright. It's installed and run on their own infrastructure, and they're responsible for hosting, maintenance, and updates.

Pros:

Full control over data — critical for industries with strict compliance requirements (banking, government, healthcare)
No dependency on a third-party's uptime or pricing changes
Can be deeply customized for a single client's exact workflow

Cons:

Higher upfront development cost
Every update or bug fix has to be deployed per client — no single source of truth
Scaling to more clients means duplicating infrastructure, not just usage

SaaS (Software as a Service)

The system runs on your infrastructure (usually cloud-based), and clients access it through subscriptions — no installation, no local maintenance.

Pros:

Lower barrier to entry for clients — no big upfront investment
One codebase, one deployment pipeline, updates reach everyone instantly
Recurring revenue instead of one-time payments
Usage-based scaling — you grow infrastructure as demand grows, not per client

Cons:

Requires solid architecture from day one: multi-tenancy, scalability, and security aren't optional
You're now responsible for uptime, data protection, and infrastructure costs
Harder to justify for clients with strict data-residency or compliance needs

What actually decides it

There's no universally "better" option. The right call depends on:

Client type — regulated industries often need on-premise; startups and SMBs usually prefer SaaS
*Budget *— SaaS lowers the client's entry cost but raises your own operational overhead
Growth plan — are you building one solution for one client, or a product meant to scale to thousands of users?
Technical readiness — SaaS demands proper architecture (tenant isolation, horizontal scaling, monitoring) before you even onboard your first paying customer

My take

Most modern products — especially those built with a stack like Next.js, React, and MongoDB — lean naturally toward SaaS, since the ecosystem is built for fast iteration and cloud-native scaling. But that doesn't mean it's always the right call. I've seen teams over-engineer a multi-tenant SaaS when a simple, well-built on-premise solution would've shipped faster and served the client better.

The real skill isn't picking a side — it's knowing which one solves the actual problem in front of you.

What's your default — SaaS or traditional? Curious to hear how others make this call

DEV Community: Essam Abd Elmaboud

Building Mawared: An Egypt-Focused HR and Payroll Platform

SaaS vs Traditional Software: Which One Should You Actually Build?