← Case Studies [ Case Study · Internal System · 2026 ]

IGBS Portal.
One database. Twenty years of trademarks.

A bilingual internal operating system for Egypt's #1 trademark agency — replacing two decades of spreadsheets, paper files and disconnected tools with a single role-based dashboard for 17,000+ trademark records, 4,500+ clients, payroll, vault, and loan disbursements.

Client
IGBS · International Group for Business Solutions
Sector
Intellectual Property Law
Type
Internal Web App (PWA)
Year
2026
IGBS Portal Executive Overview dashboard showing vault balance, payroll, trademark counts and live ledger
Demo data shown — all figures, employee names, client records, and ledger entries in these screenshots are illustrative. The live portal is private to IGBS staff and clients only.
[ 01 — The problem ]

After 20 years and 17,000 trademarks,
the firm was running on memory.

IGBS has been Egypt's leading trademark-registration firm since the mid-2000s — they've filed and protected over 17,000 trademarks for 4,500+ clients across Egypt, the Gulf, and globally. Every filing has a status, a class, a renewal date, a logo file, a client owner, a fee schedule, and a paper trail with the Egyptian Trademark Office.

None of that lived anywhere structured. Trademark records were spread across Excel workbooks, physical files, WhatsApp threads with clients, and a few decade-old Word documents nobody trusted. Salary calculations happened on a separate sheet by the HR coordinator. Loan requests bounced between HR, the CEO, and Finance via printed forms and email forwards. The vault — the cash account that funds payroll and disbursements — was reconciled by hand every Thursday.

When a client called to ask "what's the status of my filing?", finding the answer took 15 minutes and a phone call to the right person. When the CEO wanted a snapshot of monthly cash flow, it took a finance analyst half a day to produce one. Nothing was searchable. Nothing was bilingual. Nothing was role-aware. Nothing surfaced what mattered.

The firm needed a single source of truth — but it had to look like IGBS, work in Arabic and English, run on the phones their staff already used, and be operable by people who'd never touched a CRM in their lives.

"We don't need software. We need our software — the way we already work, just without the chaos."
[ 02 — Before vs after ]

Twenty years of process,
encoded once.

Before
Memory, paper, and 12 Excel sheets
  • Trademark records in 12+ Excel workbooks, last unified version unknown
  • Client portfolios reconstructed from email threads on request
  • Renewal deadlines tracked manually — late filings happened
  • HR coordinator owned salary calculations on a private sheet
  • Loan approvals required physical signatures and three-day routing
  • Vault reconciliation done weekly by hand from receipts
  • No client self-service — every filing question was a phone call
  • English only, despite a 60% Arabic-speaking client base
After
One portal. Five roles. Two languages.
  • Single trademark database — searchable, filterable, status-tracked
  • Client portfolios with one-click trademark history per company
  • Automated renewal alerts surfaced on the Executive Overview
  • HR enters once — Finance disburses, Payroll auto-calculates
  • Loan workflow: HR → CEO approval → Finance disbursement, all in-app
  • Vault sheet with daily snapshots and live ledger
  • Client Portal: clients sign in with a Portal ID, see their filing status live
  • Bilingual EN/AR with full RTL — every label, every form, every receipt
[ 03 — The system ]

Twelve modules,
one operating system.

The portal is a single-page web application that staff sign into from any device — desktop in the office, phone on a client visit, tablet at the Trademark Office. It installs as a Progressive Web App, works offline for read-only views, and ships with bilingual EN/AR including full right-to-left layout flipping on every screen.

Access is role-based — Admin, CEO, HR, Finance, Employee, Client — and each role sees a different home screen with only the modules they need. Below are the twelve modules that make up the system.

01

Executive Overview

CEO landing page. Live KPIs — vault balance, monthly payroll, active trademark count, items awaiting action. Payroll snapshot and 5-row vault ledger surfaced inline.

02

Inbox

Cross-role approval workflow — leave requests, loan approvals, quarterly budget signatures, new-hire approvals — routed to the right person, in the right order.

03

Trademark Database

Every trademark, every status, every class. Logo-first grid view, full-text search, class filters, renewal-date sort, timeline of filing progress per mark.

04

Clients

4,500+ client portfolios — domestic and international. One-click view of every trademark filed for a client, with split between Egyptian and international filings.

05

Employees

Active staff roster with role, department, join date, base salary, contact, and live clock-in/out. Aggregated monthly payroll calculated automatically.

06

Attendance

Daily clock-in/clock-out per employee. Feeds directly into payroll deductions and bonuses without any manual recalculation.

07

Salary Adjustments

HR logs deductions and bonuses with reasons. Net salary auto-calculates and feeds into Payroll. CEO sees adjustments in real time — no end-of-month surprises.

08

Loan Requests

Three-stage workflow — HR submits, CEO approves with note, Finance disburses from vault. Auto-deducted from the requester's salary the same month.

09

Loan Disbursements

Finance's queue of CEO-approved loans ready to pay out from the vault. Confirmation modal shows the impact on vault balance and salary before disbursement.

10

Vault Sheet

The firm's cash ledger. Daily snapshots saved locally and to account. Every inflow and outflow logged with reason, source, and approver.

11

Payroll & Adjustments

Monthly payroll run with HR adjustments baked in. Base + bonuses − deductions = net. One click to mark paid; vault auto-debited.

12

Portal IDs & Client Portal

Admin issues a Portal ID to a client. Client signs in and sees a stripped-down "My Trademark" view — live status, documents, progress timeline. Zero phone calls.

[ 04 — How a loan moves through the firm ]

From request to vault,
without paper.

An example of how the system replaces a paper-and-signature workflow. A junior associate asks HR for a 5,000 EGP advance:

  1. HR logs the request

    HR opens Loan Requests, picks the employee, enters amount and reason. Submits to CEO with one tap. Status: Pending CEO approval.

  2. CEO sees it in the Inbox

    The request appears in the CEO's Inbox with employee history, prior loans, current salary. CEO approves with an optional note. Status: CEO approved — ready to disburse.

  3. Finance disburses

    Finance opens Loan Disbursements, sees the approved loan in the queue. Confirmation modal: "Disburse EGP 5,000 to Karim? Vault outflow added. Auto-deducted from Karim's salary this month." One tap.

  4. System auto-propagates

    Vault Sheet logs the outflow. Karim's payroll deduction is queued for month-end. Karim sees the new balance in his Employee view. CEO's Executive Overview reflects the new vault balance instantly.

[ Detail · Sign-in ]

One door,
two audiences.

A single sign-in screen routes clients and staff to completely different experiences. Clients enter a 7-character Portal ID — no email, no password — and land on their own filing's live status page. Staff sign in with their work credentials and land on the role-specific dashboard they expect.

IGBS Portal sign-in screen with Client Portal and Staff tabs
Sign-in · Portal ID-based access · EN/AR toggle in top corner Portal ID shown is illustrative only.
[ 05 — Stack & engineering ]

Built to outlast
any framework cycle.

The portal is deliberately framework-light. No build step, no npm install, no transpiler watcher — just a single HTML file with inline React via Babel-standalone, runnable from any static host or even from a USB stick. The firm's IT person can open it in a text editor and read every line of code, and it will run identically in 10 years on whatever browser ships then.

State persists to sessionStorage per role, with daily vault snapshots auto-backed-up. Bilingualism is handled with a single i18n object — Arabic translations sit alongside English keys, and RTL flipping happens via html[dir="rtl"] CSS rules rather than a separate stylesheet. The whole thing installs as a Progressive Web App from the browser's address bar.

React 18 + Babel Vanilla CSS Manrope · Tajawal PWA + Service Worker sessionStorage Auth Role-based ACL EN/AR · RTL Offline-first
[ 06 — Outcomes ]

What changed,
measurably.

15 min → 5 sec

Average time to answer "What's the status of my filing?". Client Portal removed the phone call entirely.

Half a day → instant

Executive Overview replaces the half-day finance analyst report. CEO opens the portal and sees the firm's cash flow live.

3 days → same day

Loan request cycle time. No printing, no signatures, no walking files between offices.

Zero missed renewals

Renewal alerts surface 90 days, 30 days, and 7 days out. The Executive Overview makes them impossible to ignore.

EN/AR parity

Arabic-first clients and staff finally have the same experience as English ones. Every form, every receipt, every label.

One source of truth

Twelve disconnected workflows, one portal. Twenty years of process — finally encoded in software the firm owns.