Questions buyers ask before starting a website, app or ERP project

CodeStan is a software development company in Egypt that designs and builds websites, e-commerce stores, mobile apps for iOS and Android, custom ERP and business systems, AI integrations and UI/UX design. One team handles discovery, design, development, launch and support after launch.

Our team is based in Sheikh Zayed City, Giza (Greater Cairo), Egypt. We serve businesses in Egypt, Saudi Arabia (Riyadh, Jeddah and other cities), the UAE (Dubai) and the wider GCC. Work with clients outside Egypt runs remotely: video calls, WhatsApp and a shared staging link where you see progress every week.

Yes. Arabic and English bilingual products are a core specialty. We design Arabic right-to-left (RTL) layouts properly — mirrored layouts, Arabic typography, Arabic search and Arabic content — not as an afterthought to an English site.

We quote each project after a short discovery call, because cost depends on scope: number of pages or screens, integrations (payments, shipping, ERP, government or tax systems), languages, content and design depth. The first consultation is free and you receive a written proposal with scope, timeline and price.

As a guide: a company website usually takes 3–8 weeks, an e-commerce store 6–12 weeks, a mobile app MVP 10–16 weeks and a custom ERP rolled out in phases over 3–9 months. We confirm the timeline in the proposal after discovery.

Yes. We follow seven phases: Discover, Research, Strategy, Design, Development, Launch and Growth. You approve a clickable prototype on a private staging link before the full build, then see a working demo every week during development.

You do. We publish to your own domain, hosting or cloud account and your own App Store and Google Play developer accounts, and hand over the source code and admin access at launch.

Yes. After launch we offer support with an agreed service level (SLA): monitoring, bug fixes, security and framework updates, analytics reviews and a roadmap of improvements. The support plan is agreed in the proposal.

We pick the stack for the project. Common choices are Laravel/PHP with MySQL or PostgreSQL for web platforms and systems, React or Next.js for rich front ends, Flutter for iOS and Android apps (Swift or Kotlin when native is needed), Odoo or a custom build for ERP, Python and LLM APIs for AI features, and AWS for cloud hosting.

Yes. Besides custom builds, we offer ready-to-deploy systems that are configured to your business: a clinic management system, an ordering and delivery platform, a real-estate management system and a learning management system (LMS).

Yes. We start with a technical and UX review of the current website, app or system, then recommend whether to improve, integrate or rebuild — and explain the trade-offs before you decide.

Message us on WhatsApp at +20 106 054 7671, send a short request at codestan.com/contact, or book a free consultation at codestan.com/consultation. We reply within one business day.

The price depends on scope, so we quote each project after a short discovery call. The main cost drivers are the number of pages and languages, custom design versus a simpler layout, the admin features you need, and integrations such as CRM, payments or e-invoicing. A focused landing page costs far less than a portal with logins and dashboards. We send a written scope with the quote so you can compare options.

A bilingual company website of 5 to 10 pages typically takes 3 to 6 weeks. A single landing page can be ready in 1 to 2 weeks, while a custom portal usually needs 8 to 16 weeks. The biggest factor is how quickly content and approvals come back, so we share a content checklist on day one.

Yes. Bilingual Arabic and English websites are our core specialty. We build true right-to-left Arabic layouts, separate SEO tags for each language, and a language switch that keeps visitors on the same page. Your team can edit both languages from one admin panel.

We quote each project after a short discovery call, because cost depends on scope. The main drivers are the number of pages and languages, custom design, admin features, and integrations such as payment gateways, booking, CRM or ZATCA-ready invoicing. A landing page costs far less than a portal. You receive a written scope with the quote so you know exactly what is included.

No. We serve Saudi clients remotely from our team in Sheikh Zayed, Egypt. Egypt matches Riyadh time in summer and is one hour behind in winter, so we hold video calls, reply on WhatsApp and run weekly demos within your working hours. You can review progress any time on a private staging link.

A bilingual company website of 5 to 10 pages typically takes 4 to 7 weeks, including the Arabic content planning step. A campaign landing page can be ready in 1 to 2 weeks. Portals with logins and dashboards usually take 10 to 18 weeks, depending on integrations and approvals.

We quote each project after a short discovery call, because cost depends on scope. The main drivers are the number of pages and languages, the level of custom design and motion, admin features, and integrations such as bookings, CRM or payment gateways. A landing page costs far less than a client portal. You get a written scope with the quote so options are easy to compare.

No. We serve UAE clients remotely from our team in Sheikh Zayed, Egypt. Egypt is one to two hours behind Dubai depending on the season, so video calls, WhatsApp replies and weekly demos happen within your business day, and you can check progress any time on a private staging link.

It depends on who buys from you. Many Dubai businesses lead in English and add full Arabic for Emirati, Gulf and government-linked clients, while consumer brands often need both equally. We review your audience in discovery and design both languages together, each with its own SEO.

The cost depends on scope, not on a fixed price list. The main drivers are the number of user types (customer, driver, vendor, admin), payment and map features, integrations with existing systems, and whether you need native code. We quote a fixed project price after a short discovery call, and we often suggest an MVP first so you spend less before the idea is proven.

For most Egyptian businesses Flutter is the better choice because one codebase serves Android and iOS, which lowers cost and speeds up updates. Native Kotlin or Swift makes sense for apps that depend heavily on device hardware, complex background work or very specific platform features. We recommend one or the other after we see your feature list.

We integrate gateways such as Paymob, Fawry, Kashier and valU instalments, covering cards, mobile wallets and reference-code payments, and we can add cash on delivery. The final choice depends on your merchant agreement and fees. You open the merchant account in your company name, and we connect it to the app and the admin panel.

The cost depends on the scope of your app rather than a fixed rate. The biggest drivers are the number of user roles, payment and BNPL integrations, identity or ERP connections, the design level, and whether you need native code. We send a fixed quote after a short discovery call, and we can split the project into phases so the first release goes live sooner.

Yes. We integrate Mada and credit cards, Apple Pay and STC Pay through Saudi gateways such as Moyasar, HyperPay or PayTabs, and add Tabby or Tamara for instalments. Your company signs the merchant agreements, and we connect them to the app, the admin panel and your refund and reconciliation flow.

We build apps with the Saudi Personal Data Protection Law in mind: consent screens, a clear privacy policy, minimal data collection, access controls and secure storage. We can host data in a region you approve, including Saudi-based cloud options. Formal legal compliance is your company's responsibility, so we recommend reviewing the final policy with your legal adviser.

The cost depends on your scope, not a fixed package. The main drivers are the number of apps (customer, staff, driver, vendor), payment and booking logic, integrations with UAE Pass, CRM or POS, the number of languages and the level of design polish. We send a fixed quote after a short discovery call and can phase the work so the first version launches sooner.

Yes. We build English and Arabic as standard, with layouts that switch correctly between left-to-right and right-to-left, and we can add other languages your customers use. Each language gets its own reviewed copy rather than machine translation, and store listings can be published in several languages.

We integrate Apple Pay, Google Pay and card payments through gateways such as Network International, Telr and Checkout.com, and add Tabby or Tamara for buy-now-pay-later. Your company holds the merchant account, and we connect it to the app, the admin panel, refunds and reporting.

The cost depends on the number of modules, branches and users, how custom your workflow is, the ETA integration, and how much data needs migrating. Odoo-based projects usually start lower than fully custom ones. We do not publish fixed prices because two ERPs are rarely alike; we quote per project after a short discovery call, and we can split the build into phases so you pay for what you use first.

Choose Odoo when your processes are close to standard accounting, inventory and sales, and you want a faster start. Choose custom when your workflow is unusual, you need very simple screens for non-technical staff, or licence and customisation costs would grow over time. We review your workflow during discovery and give a written recommendation with the reasons.

Yes. We integrate the ERP with the Egyptian Tax Authority e-invoice system, and with the e-receipt system for retail sales where it applies to you. Invoices are issued once in the ERP and submitted electronically, and the accountant sees which documents were accepted or rejected and why. Registration and signing setup are done together with your accountant.

Our ERPs are built ready for ZATCA Phase 2 integration: they produce invoices in the required XML format with QR code and cryptographic stamp, support clearance and reporting flows, and are tested on the ZATCA sandbox. Final onboarding is done with your team using your ZATCA account, and your tax advisor confirms your wave date and any rules specific to your activity.

No. We serve Saudi clients remotely from our team in Sheikh Zayed, Egypt. Workshops run over video calls, day-to-day questions go through WhatsApp, and you can open the staging environment at any time to see progress. Because Egypt is at most one hour behind Riyadh, our working hours overlap with yours almost completely. An on-site visit can be arranged when the project needs it.

Yes. If PDPL or your own policy requires data to stay in the Kingdom, we deploy on a cloud provider region or data centre inside Saudi Arabia, or on your company servers. We set up backups, monitoring and access control there, and the accounts remain in your company name.

Use a hosted platform if you have a simple catalogue and want to launch quickly with low running effort. Choose a custom store when you need branch stock, B2B prices, your own delivery rules, ERP sync or full control of data and fees. We compare both for your case during the free consultation and recommend the cheaper route that still fits.

Your store can accept bank cards, Meeza cards and mobile wallets through gateways such as Paymob or Kashier, Fawry payment codes, instalments such as valU where your provider supports them, and cash on delivery. You open the merchant accounts in your company name, and we handle the technical integration and testing with real orders.

Yes, mainly with confirmation and rules. We can send an automatic WhatsApp confirmation before shipping, block COD for certain areas or order values, ask for a small online deposit, and flag customers with repeated refused deliveries in the admin dashboard.

Stay on Salla or Zid if your catalogue is standard and the built-in apps cover your payments and shipping. Move to a custom store when you need special pricing, several warehouses, a B2B channel, deep ERP sync or full control over data and fees. We review your current store in the free consultation and give a clear recommendation.

Your store can support Mada, Visa, Mastercard, Apple Pay and STC Pay through gateways such as Moyasar, HyperPay or Tap, plus Tabby and Tamara instalments. You sign the merchant agreements in your company name, and we handle integration, testing and the payment status logic in your dashboard.

Yes, the store is built to be ready. Each order keeps the VAT and buyer data a tax invoice needs, and we integrate with your ERP or an approved e-invoicing solution provider that issues and reports invoices to ZATCA (Fatoora). Your accountant confirms which phase and requirements apply to your company.

UX design decides how the product works: user research, flows, structure and what happens at each step. UI design decides how it looks: layout, colours, type, icons and components. We deliver both together, because a beautiful screen with a confusing flow still loses users.

Both. You can hire us for design only and hand our Figma files and design system to your developers, or let our team build the website, app or system too. Design-only clients get a developer walkthrough and support questions during build.

Yes. We usually start with a UX audit: analytics, heuristic review and a few user sessions. You get a prioritised list of problems and quick wins, then we redesign the flows that hurt conversion or productivity the most, without forcing a full rebuild if it is not needed.

The best first use case is a repetitive task with a lot of volume and a clear owner, such as answering common customer questions on WhatsApp, extracting data from supplier invoices, or helping staff search internal policies. These are easy to measure and low risk when a person reviews edge cases. We help you choose during a free consultation based on your volume and data.

Yes, current models handle Saudi and Gulf dialects reasonably well, but quality varies by model and topic. We test on real messages from your customers before launch, tune prompts and content for local wording, and route unclear or sensitive conversations to a person. Replies can follow your preferred tone, formal or friendly.

It depends on how the integration is built. We use business API terms rather than consumer chat apps, send only the data a task needs, mask personal details where possible, and log every request. For highly sensitive data we recommend a private or self-hosted model so the data never leaves infrastructure you control.