Most of my work starts with a spreadsheet nobody trusts.

What this has looked like

Three systems I built for TTE Engineering, part of Dubai's Easa Saleh Al Gurg Group. Each started as a problem someone was living with every month.

1. 4–5 days → daily

   Management reports that arrived days late

   Eight business lines waited 4–5 days after month-end for a pack built by hand in Excel and PowerPoint, an estimated 576–768 hours of work a year. I wrote down the 450 or so rules behind the numbers, reconciled the results to Finance totals within agreed tolerances, and replaced the pack with reporting that refreshes daily. In August 2026, 36 of the 43 people it was built for were using it.

   How long: 18 days from usable access to the company data to people signing in, and 54 days to the first full management review run on it.

2. 331 requisitions

   Hiring approvals lost in inboxes

   Three business units ran hiring over email and spreadsheets, so nobody could say where a request was stuck. One approval workflow now covers all three and has handled 331 requisitions. Overdue steps reach the accountable VP by themselves. AI reads incoming CVs, which cut each candidate record from about 10 minutes to 1–2, and people still make every hiring decision.

   How long: 101 days from the first meeting with HR to rollout in three business units.

3. Order → invoice

   A factory that couldn’t see its margin

   In a duct factory producing about 1,200 m² a day, orders, nesting software, material movements, dispatch and SAP each told a different story. I linked them with tag-level tracking, so each piece can be followed from order to invoice with its material, variance and margin. Factory users tested it on real engineering data before launch.

   How long: 75 days from the first line of code to launch on the factory floor.

Smaller ones matter too. Quotations now go from the customer's email to a costed, review-ready file, saving 30 minutes to several hours each. Delivery paperwork that took hours takes seconds.

Is this for you?

• A report, approval or handover runs on spreadsheets and email, and someone rebuilds it by hand every week or month.
• Your numbers come from SAP, Zoho or Excel exports, and different teams get different answers.
• The process lives in one or two people's heads, and it stalls when they are away.
• You want a system your own team can run and change, not a black box.

If you need a marketing website or a mobile app, I'm not the right person, and I'll say so.

How we'll work

Five steps, each leaving you with something you can hold me to. Where AI helps, it works inside fixed rules and a person makes the final call.

1. 1

   Understand

   I spend time with the people who do the work, not only the people who manage it, and map the process as it really runs, including the workarounds.

   You get: process map

2. 2

   Agree

   We write down what finished means in numbers you can check: days to close, hours saved, errors caught. That is how we both know the work is done.

   You get: success metric

3. 3

   Build

   You see working pieces early and can push back on them. I build around what you already run, such as SAP, Zoho CRM, Microsoft 365 or Smartsheet, and your data stays where you keep it.

   You get: working increment

4. 4

   Prove

   The system is checked against your real data before anyone relies on it. For reporting, that means it reconciles to Finance.

   You get: acceptance evidence

5. 5

   Hand over

   Your team gets written runbooks and training, so the system keeps running without me.

   You get: runbook and training

Who you'd be working with

Based in

Dubai, UAE (UTC+4). I work with teams in the Gulf and remotely.

Track record

Finance, HR and factory systems for TTE Engineering, part of the Easa Saleh Al Gurg Group.

Background

Mechanical engineer (NUST) with a minor in computer science.

Fits into

Whatever you already run: SAP, Zoho, Microsoft 365, Excel and the like.

Speaks

English, Urdu, Punjabi.

The full work history is on LinkedIn.