Ahmed Al-HawajriLaravel & PHP Developer All work · Opsight

03 / 05Operations and business intelligence for Gulf businesses2026

Opsight

Your orders, stock and expenses in one place, and their figures against the period before.

  • Next.js 16
  • React 19
  • Tailwind 4
  • TanStack Query
  • Recharts
  • Laravel 12
  • PHP 8.2
  • Sanctum
  • MySQL
  • Pest
  • Vitest
  • Playwright
  • REST API
  • Larastan
42.4%▲ 2.9
Opsight

At a glance

01Who is it for?

  • The owner: sees everything, and sets up the business and its users.
  • The manager: runs orders, stock and expenses, and reads the analysis.
  • The analyst: reads the figures, costs and margins and exports them, and changes nothing.
  • Staff: record orders and customers and take payments, with no cost and no profit in sight.

Before the project

A small or mid-sized business does not lack data; it lacks one place for it. Orders live in one system, stock in a ledger and expenses in a spreadsheet, so "what did we make compared with last month, and why?" takes a day and ends in a figure no two people agree on.

The product

The product, as its users use it

Scroll to walk with the user one step at a time, each step on the screen where it actually happens.

  1. Try it as any role

    The sign-in page has a button per role: owner, manager, analyst and staff, and the owner of a second business. The data is invented, and it is put back every night.

    /login

    Opsight — Sign in with a demo account per role
  2. The month on one screen

    Revenue, orders, profit, margin and expenses, each beside the previous period and the change from it, and a period not yet over is marked incomplete.

    /dashboard

    Opsight — The owner's dashboard, against the previous period
  3. Why the figure moved

    Trends and breakdowns by category and product, compared with the previous period, last year, or the same Hijri dates, then insights from plain rules.

    /analytics

    Opsight — Analytics and comparisons
  4. One order, its whole history

    The lines at the prices they sold for, the payments and refunds, and when it was placed, confirmed and fulfilled.

    /orders

    Opsight — An order: its lines, payments and history
  5. The same screen, for staff

    Staff see orders and revenue, and no cost, profit or expenses, because the server never sends them.

    /dashboard

    Opsight — The staff dashboard: no cost, no profit
  6. A second business, same installation

    A Kuwaiti business in Kuwaiti dinars and its own time zone, which sees nothing of the first, and the first nothing of it.

    /orders

    Opsight — A second business in Kuwaiti dinars, with its own orders and numbering, isolated from the first
Opsight — Sign in with a demo account per role
Open the full page

How it was solved

Built to hold

The decisions that make the promises above true, rather than a look on the screen.

  1. Every metric defined exactly once

    Revenue, cost, margin, cancellation rate, new and returning customers all live in one file, aggregated in SQL over DECIMAL columns. Cost comes from the snapshot kept with the order line when it was confirmed, not from the product’s price today.

  2. Roles enforced on the server

    Some fifty abilities spread over four roles, checked by policies before every action. Staff record orders, follow them and take payment, but never see a cost, a margin or an expense, because those fields never reach them.

  3. The Gulf calendar is part of the arithmetic

    The working week and its weekend come from the business’s settings, a period in progress is marked incomplete, and when a period falls in Ramadan or Eid the analysis offers to compare it with the same Hijri dates last year.

  4. Insights by rule, not by guess

    Ten rules read the figures: a falling margin or revenue, a spike in cancellations or expenses, dependence on one customer, a stockout coming, products with no cost, customers who have gone quiet. None fires on a period still in progress or on a handful of orders, and a rule that involves cost is not even computed for a role that may not see cost.

Worth explaining

The outcome

What was delivered

17
screens in the product
46
real screenshots
831
automated tests
2
full languages
  • A live copy with demo accounts for four roles and a second business, put back every night.
  • Arabic and English, in the currencies of nine countries with their VAT.
  • 573 Pest tests, 188 Vitest tests and 70 Playwright browser tests, with PHPStan at level 6 on every push.
  • Ten insight rules, and an activity log of who changed what.
  • PASSStaff never receive a product’s cost, on the list or on its own pageopsight/tests/FieldRedactionTest.php

and 830 more in the repository

Every screen

Every screen, as it is

Real screenshots of the project running — not stock imagery.