Web Applications & Portals in Kuwait

Web application development in Kuwait

Requests that arrive by email, documents sent over WhatsApp, approvals waiting for one signature: many Kuwait organisations still run on these. We handle custom web app development for them, building portals for customers, members or staff one module at a time, in Arabic and English. Each module is listed in the quote, signed off on its own and tested by your users before it goes live.

  • Modules you choose, one by one
  • Screens limited by role
  • Arabic and English screens and PDFs
  • Exports managers run themselves
Get a portal quote
Portal dashboard on a big screen, checked by a team of three, with code on a laptop in front

Who will log in: customers, members or staff?

Customers
A portal where they submit requests, upload documents and follow the status without calling. Tell us what they do today and we quote for it.

Quote a customer portal

Your own staff
An internal system for requests, approvals and records, replacing forms and email chains. Tell us which process hurts most and we quote for that module first.

Quote a staff system

Modules

Each module priced and approved on its own

AR + EN

Screens, emails and PDFs in the user’s language

17 services

Portals alongside web, marketing and design work

Since 2012

Websites and digital marketing for over a decade

Portal modules we build, one by one

A portal is built from modules. You choose which ones, and each is quoted, built and signed off separately.

Customer or member portal

Requests, documents and status behind one login

Staff requests and approvals

Leave, purchases or maintenance routed for approval by role

Document archive

Uploads with type, owner and expiry date

Dashboards

Counts, delays and exports for managers

What the portal must do for Arabic and English users

Bilingual portals fail on small details: a name spelled two ways, a date format that flips, a PDF that prints left to right. These are the seven we design for from the first screen.
Your users test each one in both languages.

Staircase of floating web and security icons, climbed by a woman in an abaya

Build stages, module by module, with sign-off

Each module runs through the same six steps and has its own sign-off, so one module can be live while the next is still being designed.
Nothing goes live without a signed user test.

STEP 01. Module list and order

We agree which modules the portal needs and which goes live first. Each module gets a short requirements page, written in plain language, which your approver signs.

STEP 02. Screens in both languages

The main screens of the module are drawn in Arabic and in English, with real field names. Your approver signs them off before any code is written.

STEP 03. Build on a test link

The module is built on a test link that your team can open at any time. Other modules wait until this one works as agreed.

STEP 04. Data import test

Records from your spreadsheets are imported into the test link, and Arabic names, dates and amounts are checked. Anything that does not match is listed for your team to correct.

STEP 05. User test and sign-off

A handful of real users work through their everyday tasks in both languages. We fix what they find, and the module is signed off only when they can finish their tasks.

STEP 06. Go live, then the next module

The module goes live with a short training session, and the next module begins its own cycle. Support after launch and the handling of change requests are set out in the proposal.

Signs your paperwork needs a portal

Three patterns we hear when organisations describe how requests move today.

Approvals wait for one signature

Everything stops when one manager travels.

  • What you see: requests stuck for days, mostly in summer
  • Usual cause: approval by paper or email to one person
  • The fix: approval by role, with delegation

Documents arrive by WhatsApp

Copies scattered across phones.

  • What you see: ID copies and forms lost in chats
  • Usual cause: no single shared place to upload documents
  • The fix: uploads with type and expiry date

Two languages, two spreadsheets

Arabic and English records disagree.

  • What you see: the same person spelled three ways
  • Usual cause: names typed again for each language
  • The fix: one record holding both spellings

Code, hosting and data ownership

Before a line of code is written, the proposal says who owns the code, whose account the server sits in and how the data can be exported.

The answers are written down, not assumed.

  • Ownership or licence terms in the contract
  • Repository access as the proposal states
  • Third-party libraries listed with licences
  • Technical notes for any future developer

  • Hosting account in your organisation’s name
  • Server details documented
  • Backup schedule and retention in writing
  • Domain and certificate renewals listed

  • Exports in spreadsheet-friendly formats
  • Your data goes with you if you change supplier
  • Personal details visible only by role
  • Deletion handled as your policy requires

Technology, payments and Arabic support

Build

  • Established open technologies, named in the proposal
  • Code kept in a repository you can access
  • Runs in the browser, no install for users

Payments

  • Your own payment provider, connected by its API
  • Card details handled on the provider’s side
  • Receipts in the user’s language

Arabic support

  • Right-to-left screens and PDFs
  • Arabic search normalised for spelling variants
  • Arabic fonts that render on every device

Services you can connect to your portal

  • Content only: if you mainly publish pages and news, a WordPress site may be all you need.
  • Phone app: if users need an app from the stores, add mobile app development.
  • Automation: routine replies and data entry can be automated with our AI agents and automation service, quoted separately.
  • Hosting: run the portal on a server sized for its users with web hosting.
  • Public website: give the portal a front door that explains it with web design and development.
  • Product sales: if customers buy goods rather than services, compare e-commerce development.

Pick only what the portal needs; each service is quoted separately.

Phones, a tablet and a desktop showing one Arabic site
Woman in an abaya holding flowers beside a phone showing marketing screens

What to prepare, and who approves each module

Bring examples, not a specification. Real forms and real records tell us more than a long brief.

  • Current forms: paper, PDF or online forms people fill in today, in both languages.
  • User groups: customers, members, staff and managers, and roughly how many of each.
  • Sample records: a spreadsheet extract with Arabic and English names, personal details removed.
  • Approvers: who signs off each module, and who covers when they travel.
  • Connections: accounting, HR or payment systems the portal must talk to.

No written brief? A short call walking through one request from start to finish is enough to begin.

Where portals help, by organisation type

Organisations that handle many requests and documents gain most from a portal. These are examples of modules we plan, not names of Kuwait clients.

Training institutes: registration, attendance and certificates

Clinics: appointment requests and patient forms

Cooperative societies and clubs: member records and renewals

Contractors: site reports, variations and approvals

Property managers: tenant requests and lease renewals

Distributors: dealer orders and price lists

Schools: admission documents and parent requests

Service companies: job cards and customer sign-off

What sets the price, and how modules are quoted

A portal is priced module by module. Two quotes are only comparable when they list the same modules, the same user groups and the same yearly running costs.

Three lines to look for in a proposal:

  • Modules: each module named, with its screens and the roles that use it.
  • Running costs: hosting, domain, email sending and any provider fees, per year.
  • Changes: how new requests after sign-off are estimated and approved.

Send your module list and user numbers with a quote request, and we reply with a first view of the scope.

User roles

Each extra role means more screens, permissions and testing.

Connections

Each system the portal talks to adds set-up, tests and upkeep.

Two languages

Arabic and English screens, emails and PDFs add work to each module.

First module first

A first module live early lets you test before committing to the rest.

Request a quote for your portal

Use the quote form to tell us who will log in and what they need to do, for example: “about 400 members renew each year, upload two documents and pay online, and staff approve each file”. We reply by email with the questions we need answered before a proposal.

One module first, or the whole portal at once?

Building every module at once looks efficient on paper, but it delays the first useful screen by months and fixes requirements before anyone has used the portal. Starting with the module that removes the most manual work puts real users in the system early, and their feedback shapes the rest. If a standard tool already covers part of the job, check our ready business systems before building that part.

When starting with one module makes sense

  • One process causes most of the manual work
  • Users have never worked in a portal before
  • Later modules are still loosely defined
  • Budget is approved in stages
  • Spreadsheet data needs cleaning first

What Kuwait organisations ask about portals

Direct answers on languages, roles, code, payments, hosting and timing.

Yes. The language is saved for each user, and screens, emails and PDFs follow it. Arabic screens run right to left.

Yes. Access is set by role: a customer sees their own requests, a clerk sees the queue, a manager sees approvals and reports. The roles are listed in the proposal.

That is settled in writing before work starts: the proposal states whether you own the code outright or hold a licence, and how the repository is handed over. Data exports are yours either way.

Yes, through your own payment provider, connected by its plugin or API. Card details are handled on the provider’s side, and the provider’s fees are separate from ours.

On a server sized for your users, with backups and a known location. Some organisations have rules on where data may be stored, so check yours first. You can host through our web hosting service or with any provider that meets your requirements.

Yes. The portal is planned so modules can be added, and each new one is quoted and signed off like the first.

No. The portal opens in any phone or desktop browser and adjusts to the screen. If you also want an app in the stores, see mobile app development as a separate project.

Usually the one that removes the most manual work or the most complaints. We suggest an order in the proposal, together with the first module’s timeline.

When your process is standard and needs few changes, a ready-made system starts faster. If that is your case, our reply says so.

Through the quote form on this page. We reply by email with questions about users and modules, then a proposal.

No. Workshops and user tests run by video call, and documents travel by email. Requests come through the quote form on this page.

From our blog: planning a portal module by module

Articles on moving forms, approvals and records online, to read before you list your modules.