Built around one question: can you prove what was agreed?
WASL — وصل, “to connect” — is a Saudi platform for weddings, events and multi-party projects. It exists because the coordination problem in this market is not a scheduling problem. It is an evidence problem.
Six commitments the product is held to.
These are not values on a wall. Each one is testable against the running application, and each is enforced somewhere in the codebase.
The record lives inside the platform
Email, SMS and WhatsApp may notify. They are never the system of record. Every stakeholder holds an authenticated account, a dashboard and an internal inbox, because a forwarded message cannot be audited.
AI recommends; people commit
The planner drafts, estimates, compares and warns. It does not book, pay or contract. Every commercial commitment passes through a named human inside a delegated limit, and the refusal of an over-limit approval is itself recorded.
Arabic is not a translation layer
The interface is bilingual by construction, right-to-left throughout, with Saudi conventions for dates, phone formats and commercial terminology — not an English product with Arabic strings bolted on.
Culture is configuration, not assumption
Separate, combined and custom arrangements are equal first-class options. WASL does not assume that every family observes the same traditions, and no workflow forces one interpretation on another.
Claim nothing that is not evidenced
No customers, partnerships, certifications, revenue or valuation are asserted anywhere in this product or its documentation. Where a number is an estimate, it is labelled an estimate and the method is published.
Privacy is a design constraint
Guest lists, family arrangements and event media are among the most sensitive data a family shares. Access follows role and project isolation; auditors see evidence without excessive exposure of personal data.
What stage this is, stated plainly.
What exists
A complete business and product package — market study, competitor analysis, feasibility and financial model, PRD, architecture, RBAC matrix, SOPs, academy design and roadmap — plus this working, deployable application implementing the core journey end to end.
What does not exist yet
Paying customers, signed partners, live payment settlement, a completed security audit, or production operational gates. None of these is claimed anywhere, and the product does not describe itself as production-ready.
What comes next
Validation: customer-discovery interviews across demand and supply, a Riyadh/Jeddah pilot with high-touch support, and the founder decisions listed opposite. Scale follows evidence, not the other way round.
Six open decisions, ranked by urgency.
Rather than guess, WASL records these as open decisions and proceeds on labelled provisional assumptions.
- 01Launch scope — Riyadh only, Riyadh and Jeddah, or wider Saudi Arabia
- 02Commercial model — membership, commission, or a phased hybrid
- 03Payment handling — record-only, gateway collection, or future escrow subject to legal feasibility
- 04Partner verification — required documents and verifying authority per category
- 05MVP boundary — which modules must launch and which are post-MVP
- 06Hosting and data strategy — Saudi-region managed cloud, private cloud, or hybrid