Bilingual website or simple portal
A website in Arabic and English of 5 to 7 pages, or a simple portal, with WhatsApp and a request or booking that your team confirms.
- Duration
- 14–21 days
- Price
- Starting from 3,000 SAR
We build websites and portals for clients and employees in Arabic and English, so your clients and your team can complete repeat requests online instead of by phone and chat. You review a working version before you pay the next stage.
A website is where a client first checks who you are. A portal is where that same client, or an employee, comes back to do a specific job: send a document, follow an order, read an invoice, or request leave. We build both, and we treat each as separate work.
A company website needs correct Arabic and English side by side. Right-to-left and left-to-right layout, forms, tables and notification messages must work in both languages, not just the headings. We choose the technical structure to fit the need. Pages that rarely change can be static, so they load fast and have fewer parts that can fail or be attacked. Pages where a user signs in and sees their own records need an application with accounts, permissions and a database.
Portals cut repeat questions because clients and staff can see the status and send a request themselves. Payments appear in a portal as a status view only, because we do not process payments ourselves. The content and the accounts are yours, and the handover explains how to edit them. If you already have a website, we can improve it instead of replacing it.
We build secure, organised portals that let clients or employees deal with the organisation online.
For example:
Some sites are built for English and then mirrored, leaving misaligned tables, icons in the wrong place and text with mixed direction. Arabic readers notice immediately.
Every call asking where an order is takes a staff member away from their work. A client with nowhere to see the status keeps phoning.
If every text change needs the original developer, the content goes stale. You should edit your own content, or know exactly who does.
A contact form that ends in one mailbox with no CRM record makes follow-up depend on one person's memory.
A portal that shows one client's documents to another is worse than no portal. Access must follow roles and be tested before handover.
Every deliverable is written into the offer with an acceptance criterion you can check.
Pages in Arabic and English with a language switch, right-to-left and left-to-right layout, and content you can edit. The page list and scope are written down before work starts.
Sign-in, roles and permissions, so each client or employee sees only their own records. It includes document upload and download, order tracking and notifications.
A back-end area where your team manages requests, users, content and approvals, with permissions by role.
A booking or order is submitted as a request, your team confirms or declines it, and the client receives a notification. You control which options can be requested.
Enquiries, accounts and requests move from the site into your CRM or internal system, and each link is tested before handover.
Written test results, a guide to editing content and managing users, and a list of the accounts opened in your name.
Every step ends with evidence you can check before the next payment.
After a free call we define the purpose, users and languages. Simple websites and portals proceed to a written offer. Complex portals with permissions and integrations require a paid diagnostic before implementation is priced.
Your part: You review the report and the offer and decide whether to continue.
The offer lists the pages or screens, the user roles, the languages, the links with other systems and the phases, each with a written acceptance criterion. Anything outside it is priced before it is built.
Your part: You approve the scope and phases, then pay 40% at the start.
We design the Arabic and English versions together, not one after the other, and show you a working version you can browse yourself.
Your part: You review it on your phone and your computer and send comments. The 30% instalment is paid when it is previewed.
We test both languages, the forms, the roles and permissions, and every link to your CRM or internal systems, and write down the results.
Your part: You compare the results with the acceptance criteria and sign the acceptance in writing.
After the last payment, which is 30% on acceptance and approval, we hand over the final files, the editing guide and the accounts in your name. We fix defects free for 14 days from handover, then an optional monthly maintenance plan is available.
Your part: You confirm that you can edit the content and sign in to your own accounts.
A bilingual site or simple portal of 5–7 pages has a starting price and a 14–21 day duration, after a free call and a written offer. A complex portal, such as the full Mutqan demo workflow, needs assessment and a custom quote; it is outside the simple-site price.
A website in Arabic and English of 5 to 7 pages, or a simple portal, with WhatsApp and a request or booking that your team confirms.
For complex work that needs assessment before implementation can be priced. Deliverables are agreed before the start; simple services begin with a free call and a written offer.
Yes. We review the current site first and write down what must be fixed, what stays and what should be rebuilt. The structure and content may stay while language support, layout, forms or the CRM link change. You decide after reading the report, and the work is priced before it starts.
We design both languages together. Before acceptance we test right-to-left and left-to-right layout, forms, tables, e-mail messages and notifications in both languages. If you prefer to start with one language and add the second later, the scope can be set that way, and the offer lists any page that will exist in one language only.
A portal shows invoices and the status of each, meaning payment status only, and we do not process payments ourselves. If you want customers to pay by card online, we connect your own payment-gateway account under the conditions for large work: a paid diagnostic first, a written scope, and your keys, not ours. We never hold keys or card data.
You do. Hosting, the domain and subscriptions are priced separately and opened in your name. We work with temporary access and leave the accounts after handover. Final files are delivered after the last payment, with a guide to editing content, so you do not depend on us for routine edits to texts and images.
Each user sees only their own records, roles decide what staff see, and we test this before acceptance. Your customers' personal data stays in your accounts and is not entered in any external tool without your written consent. If the portal holds health, financial or other sensitive personal data, we accept it only after a paid diagnostic, working inside your environment with temporary permissions and a data-processing agreement.
We fix defects in the work we delivered free for 14 days from handover. After that you can subscribe to the optional monthly maintenance plan. New features are not defects and are priced before we start. Before we do anything, we tell you in writing which requests we treat as defects and which as additions.
Write to us about your business and the first job you want your clients or team to complete online. We reply with the next step, and the introductory conversation is free.