ElSultanWeb

The flagship — web applications

02

Platform Build

Web applications that take payments, manage people and run operations: donation systems, ticketing, bookings, portals and the admin back-offices behind them. AI coding agents make builds like this economical for a founder-led practice; automated tests, staged deployments and versioned migrations make them dependable.

Discuss this project

What is Platform Build?

A Platform Build is a custom web application: donation systems, ticketing, bookings, member portals and the admin back-offices behind them. It is for organisations whose website has to do work — take money, hold records, run a process — rather than describe what the organisation does.

Choose this if

  • Your workflow is specific enough that off-the-shelf tools have stopped fitting
  • The site must take payments, manage people, or run an internal process
  • Your data is currently scattered across several subscriptions and owned by nobody
  • You need the accounts, the data and the codebase to stay in your organisation’s name

Choose something else if

  • Launch Build — when the site needs to present the business well, not operate it.
  • Website Rebuild — when the existing site is the problem and no new application logic is needed.

Designed for

Charities, event organisers, production companies and any organisation whose website must do work — take money, hold records, run a process — rather than just describe it.

The problem

Off-the-shelf tools stop fitting the moment your workflow is specific. A charity needs Gift Aid and a unit-tested Zakat calculator; a competition needs an applications CRM; a rental brand needs a second storefront on the same backend. Stitching subscriptions together leaves your data in six places and your process owned by nobody.

The intended outcome

A live, tested, multilingual web application — payments, portals and back-office included — running on accounts and infrastructure you own.

Integrated scope

What the engagement can cover.

  • 01Donation and checkout systems: one-off and recurring payments, Apple Pay and Google Pay, Gift Aid (Stripe)
  • 02Ticketing and booking flows, from application form to confirmation email
  • 03Member, sponsor and volunteer portals with role-based authentication
  • 04Custom admin back-offices: CMS, CRM, campaign and booking management
  • 05Transactional email for receipts, confirmations and account flows
  • 06Multilingual delivery — English, French, Dutch, Arabic — with full right-to-left support
  • 07Supabase backends: schema design, versioned migrations, edge functions, shared backends serving more than one storefront

Deliverables

Concrete outputs, agreed before work begins.

  • A production application live on your domain, in your accounts
  • Automated test suites (Playwright, Vitest) on the flows that move money and data
  • Dev, test and production environments with CI/CD between them
  • Versioned database migrations — every schema change recorded and repeatable
  • An admin back-office your team can run without us
  • Written handover documentation and an administrator walkthrough

Service process

Four stages with one decision trail.

There is no menu price for a platform: each one is scoped through discovery, which ends in a written scope and a fixed estimate. Duration depends on payment complexity, integrations and languages — the estimate states it before the build begins.

01

Discovery

We map workflows, data, payment logic and languages before anything is built. Discovery ends with a written scope and a fixed estimate: you know the boundary of the build before committing to it.

02

Foundations

Schema, authentication, roles and the deployment pipeline come first. From this point every change ships through versioned migrations and staged environments — the pattern behind alberr.org's 38 recorded migrations.

03

Build and verify

Features are built with AI coding agents and checked twice: by hand, and by Playwright and Vitest suites. Payment flows run in Stripe test mode until the evidence says they are ready for real money.

04

Launch and handover

A staged cutover to production, admin training, and a defined support window. You keep the keys — your accounts, your data, your codebase.

The practice owns

  • Architecture, build quality and test coverage across every scoped flow
  • Stripe integration and webhook reliability, in test mode and live
  • WCAG accessibility work and GDPR-conscious analytics
  • All four languages, including Arabic RTL layout and tooling
  • CI/CD configuration with migration gates on deployment

You provide

  • Stripe, domain and hosting accounts in your organisation's name — we work in them, we do not own them
  • A named decision-maker who can approve scope and sign off flows
  • Source content, and final say on translated copy
  • Prompt answers on business rules: refunds, roles, edge cases
  • Legal texts — privacy policy, terms, regulator wording — approved by your adviser; we implement them

Not included by default

  • Native iOS or Android apps. These are responsive web applications, not App Store products.
  • Guaranteed business results. We commit to working, tested software — never to donation totals, ticket sales or sign-ups.
  • Unscoped replacement of third-party systems. Migrating off an existing CRM, ERP or booking tool is its own project, estimated separately.
  • In-house photography and video. Where a platform needs original visual material, we plan it with trusted production partners.
  • Ongoing content operations. We build the admin tools; your team runs them.

Relevant proof

The proof is live, not promised.

Five live client properties are linked from the work page—open them, click through them and inspect them. El-Sultan Web does not attach invented outcomes or borrowed metrics to any service.

See live client work

Common questions

Platform Build, answered directly.

Every answer states a boundary as well as a capability. Broader questions about timelines, ownership and what happens after launch are on the FAQ page.

What does a web application cost in Belgium?

There is no menu price. Each platform is scoped through a paid discovery phase that ends in a written scope and a fixed estimate, so the boundary of the build is known before anyone commits to it. Payment complexity, integrations and the number of languages are what move the figure.

Who owns the code and the Stripe account?

You do. Stripe, domain and hosting accounts are opened in your organisation’s name and worked in, never owned. At handover you receive the codebase, written documentation and an administrator walkthrough.

How are payment flows tested before real money moves?

Payment flows run in Stripe test mode until the evidence says they are ready. Playwright and Vitest suites cover the flows that move money and data, and every schema change ships as a versioned migration through dev, test and production environments.

Can you build a native mobile app?

No. These are responsive web applications, not App Store products. They work on phones, but there is no native iOS or Android build and none is implied.

Project fit

Could Platform Build fit the challenge?

Twenty focused minutes: what you need built, in which languages, and what a prototype-first timeline looks like for it. If the project is not a fit for this practice, you will hear that plainly.

Book a project fit call

Initial qualification only. Not a free audit or commitment to purchase.