What is the project journey from the first message to delivery? — answered by Engineer Saeed Baatiah
Five stages: a WhatsApp message at wa.me/966573784181 briefly describing the project; a short free call to understand the situation and its edge cases; a written proposal setting out scope, deliverables, timeline, payments, and what is out of scope; execution in milestones you can see and try yourself rather than internal stages; then handover including code, accounts, and documentation with a support period. Nothing starts before you approve the written proposal.
It starts with a message on WhatsApp at wa.me/966573784181. The first stage is a free scoping consultation: what the problem is, who the user is, what systems already exist, and what the deadline is. Its output is a written scope description with an estimate of timeline and cost — no commitment up to this point.
Scope is then agreed in writing, stating explicitly what is included and what is not — most disputes arise from the second, not the first. Implementation then runs in phases: each ends with something you can see and try yourself, and payments are tied to those phases rather than one payment up front.
At delivery, ownership of the code and every account transfers to you, along with operating documentation and training for your team if needed. A post-launch support period then covers defects, while new additions are quoted separately — a distinction made clear before work starts, not after.
- 1 — Free consultation and scoping, no obligation
- 2 — Written agreement stating what scope covers and what it does not
- 3 — Phased implementation, payments tied to delivery
- 4 — Handover of code and accounts in full, with documentation
- 5 — Post-launch support covering defects