Clear answers before a project begins.

No. It is a short qualification conversation — around 20 minutes — to understand your organisation, what you need built, your languages and your timing, and to establish honestly whether El-Sultan Web is the right fit. It is not a free audit or strategy session, and it carries no commitment on either side. If the practice is not the right fit, you will be told so directly.

Organisations that need real functionality, often in more than one language: charities and non-profits (alberr.org runs donations, Gift Aid and orphan sponsorship for a UK registered charity), cultural and events organisations (bestvoicebelgium.be handles applications and Stripe ticketing), and small businesses that need bookings, e-commerce or a back-office rather than a brochure (lubbadproduction.com, 961.be). If a simple template site would serve you well, you probably do not need this practice — and the fit call will say so.

No. AI coding agents write the code quickly — that is why the pace and pricing are possible — but generation is the start of the process, not the end. Abed specifies every feature, reviews every change, and ships through automated test suites (Playwright, Vitest) and staged dev→test→production pipelines. The method is AI-accelerated engineering with founder accountability, and it is documented in full on the How I Build page.

Claude Code, OpenAI Codex and Google Antigravity for engineering, Hostinger Horizons for rapid prototyping, and Claude Design for visual design work. They are named because you should know how your product is made. The How I Build page explains what each contributes and, more importantly, the review and testing discipline wrapped around all of them.

The projects are built on standard, widely used stacks — Next.js, React, Supabase, Stripe — so any competent developer can read, maintain and extend them. Discipline does the rest: automated test suites, versioned database migrations (the alberr.org database carries 38 of them), role-based access control and staged deployment pipelines. How the code is written has changed; what gets shipped is conventional, documented software.

You do. The code, the content, the domain, the hosting and the analytics accounts are the client's property, and handover at the end of a project is complete — repositories, credentials and documentation included. There is no lock-in: because the stack is standard, you are free to take the project to any developer at any time.

Yes — it is a core capability, not an add-on. Live client work runs in English, French, Dutch and Arabic, including full right-to-left interfaces: alberr.org in EN/AR, lubbadproduction.com in EN/FR/NL/AR, bestvoicebelgium.be with EN/NL/FR locale routing. One rule does not bend: a language ships only after professional translation review. Machine translation alone is never published.

Published price ranges are pending until delivery capacity and Belgian business costs are fully validated — publishing figures before they are dependable would break this site's own rule about honest claims. Every project is quoted individually against a fixed written scope. The AI-accelerated method is what keeps quotes below traditional agency levels for comparable functionality.

With Abed El-Sultan, directly — the person who specifies, reviews, tests and deploys your project. There are no account managers and no hand-offs. Where a project needs photography or video, that work is planned with trusted production partners and set out in the proposal; it is not an in-house service.

Launch includes complete handover: accounts, credentials, and documentation of how the project is built and deployed. Ongoing maintenance is available as an agreed, written arrangement, with updates released through the same tested, staged pipeline used to build the site. And if you would rather maintain the site elsewhere, the standard stack and full ownership make that straightforward.