Skip to content
Get in Touch

IT & Systems Specialist · Riyadh, Saudi Arabia

Get in Touch

Work

What I do, how I deliver it, and what it has produced

Four kinds of work, one way of delivering it, and ten projects you can open: nine live demos and one private beta.

What I do

Four areas, each described by what changes for the people using it.

  • IT Operations & Systems

    People sign in, devices work, access matches each role, and every request has a named owner.

    • User, endpoint and account support
    • Joining, moving and leaving as one checklist
    • Assets, subscriptions and who holds what
    Also included 5
    • Request intake with a named owner
    • Endpoint setup, moves and retirement
    • Onboarding and offboarding runbooks
    • Group and permission structure
    • Troubleshooting notes the next person can use

  • Business Applications & Workflow Improvement

    Microsoft 365, Google Workspace and business platforms configured to behave the same for everyone, with repeated steps removed.

    • Microsoft 365 and Google Workspace administration
    • Business-platform configuration and coordination
    • Workflow review that removes repeated steps and ends in a decision, not a report
    Also included 2
    • Zoho CRM, Projects and Books
    • Vendor coordination

  • Digital Products & Bilingual Experiences

    When a spreadsheet stops coping, the workflow becomes an application, with an Arabic interface designed in Arabic.

    • Requirement written as actor, action, result
    • Roles, permissions and an audit trail that holds
    • Right-to-left reviewed as its own interface
    Also included 4
    • Web applications and PWAs in PHP, JavaScript and Node.js
    • MySQL data models: roles, records and their relationships
    • API integration
    • Automated tests and production checks

  • Deployment, Domains & Digital Infrastructure

    Domains, DNS, certificates, hosting and backups with a tested restore, so a change can be made safely.

    • Domain, DNS, SSL and hosting setup
    • WordPress administration and hardening
    • Controlled releases with a tested way back
    Also included 4
    • Ubuntu servers with Nginx, hosting several live applications
    • Backups with a restore that has been tested
    • Checks that go past a 200 response
    • Operating notes written for the next person

How I deliver

The same six steps for a support process or a full product, from the operational problem to something running in front of real users.

  1. Discover

    Watch the handoff as it happens today, including the parts nobody documents.

    Leaves behindThe problem, stated plainly

  2. Define & design

    Write what will exist and how we will know it works, then shape the records, roles and screens in both languages.

    Leaves behindWorkflow, roles and constraints

  3. Build

    Configure the platform, change the process or build the missing tool: one complete path first, with its failure states.

    Leaves behindA working change

  4. Secure & test

    Decide what each role may do on the server, then test the clash, the double submit, the wrong role and the empty state.

    Leaves behindChecks that pass before release

  5. Launch

    A controlled release with a known starting point, a way back and documentation for whoever runs it next.

    Leaves behindRunbooks and handover notes

  6. Improve

    Watch it in real use, fix what the first weeks reveal, and keep it simple.

    Leaves behindA system that stays reliable

Selected Projects

Ten projects, each with a short case study: nine with a public demo and one in private beta.

Every project marked Live is open to try; a project marked Private Beta is invite-only. Demos run on sample data and internal screens appear only as screenshots of fictional data, so nothing private is on display.

Tell me what is not working

Describe the problem rather than the solution. I will tell you honestly whether this is something I should take on.

Discuss your project Book a call (opens in a new tab)