A 45-module business OS
for an elevator company.

A custom ERP replacing a legacy accounting system. Built for a 24-person team in Alexandria. Production since 2026.

CLIENT
Sigma for Elevators
DISCIPLINE
Custom Software
TIMELINE
8 months
STATUS
Production
Sigma ERP main dashboard — Arabic RTL interface showing financial KPIs, operations counters, and quick links
THE BRIEF

Replace the legacy.
Keep nothing.

Sigma had outgrown its legacy accounting software. The system was server-only, ran on a single PC, and couldn't model the business honestly: separate finance from operations, track maintenance contracts vs new installations, manage a technician fleet, reconcile inter-property bills with the building owners.

The brief was simple: rebuild the entire business OS, multi-user, web-first, in Arabic, modeled on how Sigma actually operates — not on what off-the-shelf software allows.

SCOPE

Forty-five modules.
One coherent system.

Each module shipped as a distinct phase. Each phase had its own QA workflow, screenshot record, and team-onboarding session before the next began.

01

Customers

544 customer records imported from legacy. Active vs inactive segmentation.

02

Contracts

Maintenance contracts with auto-renewal logic, fee escalation, and payment tracking.

03

Maintenance

Recurring schedule per elevator, technician assignment, completion logging.

04

Breakdowns (Aging)

Open ticket queue with priority, age, and SLA tracking. Auto-escalation rules.

05

Work orders

WIP tracker per technician. Daily route sheets. Parts requisitions.

06

Quotations

New install pricing engine. Standard component codes. Auto-generated PDFs.

07

Quality workflow

QA checklist enforcement before any quotation, work order, or contract closes.

08

Treasury

Daily cash ledger. Inter-property settlements. Bank reconciliation.

09

Collections

2.14M EGP outstanding tracking. Aging buckets. Payment reminders.

10

Payroll

13-sheet payroll engine. Variable × evaluation %. Disciplinary deductions.

11

Profit & Loss

Monthly P&L per division. Owner cockpit dashboard.

12

And 33 more

Inventory, suppliers, projects, attendance, technician evaluation, commissions, reports …

CONSTRAINTS

Every constraint became a design tool.

Arabic RTL throughout. Not a translation layer — the system was designed RTL-first, including charts, tables, and date formats.

Owner-only at first. Then accountant, then ops manager, then technicians. Each role saw only what they needed.

No data loss. 544 customers, 200+ active contracts, 7 years of payment history migrated from legacy with zero gaps.

Owner self-evident. The system explains itself. The owner doesn't need a manual to use it.

STACK

Modern, considered, boring.

Boring tech is a gift. We chose stable, proven tools that we'll still want to maintain in five years.

Next.js 16 TypeScript Supabase Postgres Tailwind CSS React Server Components Vercel deployment RTL Arabic Multi-user RBAC
"What used to take three hours of paperwork takes ten clicks now. The owner sees yesterday's numbers at sunrise." — Internal Sigma feedback, 2026 Q2
BUILD WITH US

Have a system that should exist?

If you're rebuilding business operations and want a partner who treats your domain like ours — start with a paid Discovery phase. We'll give you a written spec and a fixed quote within a week.

Begin a project →