Engineering partner: Norrvek, Swedenالعربية

Custom software, built to last

Software built around how you actually work

Web apps, internal tools, dashboards, customer portals and APIs, designed for Arabic and English from the first screen. You own the code and the data.

Sound familiar?

Off-the-shelf software forces your team to work around it.

01

Arabic is an afterthought: broken layouts, wrongly mirrored icons and jumbled mixed-direction text.

02

Past projects left you with code you can’t change and a vendor you can’t leave.

03

What we build

Capabilities

01

Web apps and internal tools

Operational tools, approval flows and back-office systems that fit your processes instead of bending them.

02

Dashboards and customer portals

Clear views of your data for managers, and self-service portals for customers and partners.

03

APIs and integrations

Clean, documented APIs that connect your systems today and leave room for AI agents tomorrow.

04

Bilingual right-to-left interfaces

Arabic and English designed together: proper RTL layouts, careful Arabic typography and mixed-direction text that reads correctly.

05

Architecture and technical advice

Independent advice on architecture, technology choices, security and vendor proposals, so you decide with confidence.

Illustrative scenario

A bilingual portal for parent requests

A fictional school group in Qatar handles parent requests through email and spreadsheets, and wants one place to submit, track and answer them in Arabic and English.

  1. 01

    A short scoping phase defines the request types, roles and systems to connect.

  2. 02

    Clickable prototypes in both languages are tested with staff and a few parents.

  3. 03

    The portal is built in stages, with a demo at the end of each cycle.

  4. 04

    A staff dashboard shows open requests, waiting times and bottlenecks.

  5. 05

    The code, documentation and data are handed over to the school group’s own repository.

You receive

  • Working software, delivered in stages
  • Full source code in your own repository
  • Technical documentation and an architecture overview
  • Automated tests and a deployment setup
  • Handover and training for your team

What we measure together

  • Time to complete key tasks in the new tool
  • Adoption by the intended users
  • Defects found after each release
  • Requests handled without manual workarounds

Measures and baselines are agreed with you before work starts. We do not promise numbers in advance.

How an engagement runs

  1. 01

    Scope and architecture

    We clarify goals, users and constraints, then propose an architecture and a staged plan.

  2. 02

    Design together

    Wireframes and prototypes in Arabic and English, tested with real users.

  3. 03

    Build in stages

    Short cycles with regular demos, so you see progress and steer priorities.

  4. 04

    Launch and handover

    We deploy, document and hand over, or keep running it for you under Run & Improve.

Questions

Straight answers.

Who owns the code?

You do. The source code lives in your repository and your data stays yours. No lock-in, by design.

How do you work with our IT team?

Closely. We agree standards, environments and reviews with them upfront, and can build alongside your developers.

How long does a project take?

It depends on scope. We plan in stages, so you get working software early and see progress at every demo instead of waiting for one big launch.

Can you review another vendor’s proposal or architecture?

Yes. Independent technical review is part of our consulting work, and you get a clear written assessment of risks, gaps and options.

Let’s talk

Start with one workflow.

Tell us about a process that slows your team down. In a 45-minute discovery session we show what an agent team could do with it, and what it would take.