Skip to content
Nawah
Build your blueprint

Our working charter.

These are our rules, written into every proposal and contract.

From the idea to long after launch

  1. Before the first line of code

    A signed contract, a list of everything you'll receive, written requirements, designs of the key screens, what we need from you (domain, hosting, payment and store accounts, content), and the first payment.

  2. While we build

    Two-week cycles, working software shown at the end of each, a short weekly update, and replies within one working day.

    Quality: A second partner reviews every change before it's merged, automated checks test it, and AI tools read it as a third reviewer. A native reader checks the Arabic and English before delivery.

  3. Testing and acceptance

    Ten working days to test everything against the list. We fix what you find. The project is accepted when you sign, or when the period ends without reported issues.

  4. Warranty

    Any defect within the agreed scope is fixed free: 14 days for small projects (up to 20 engineer-days), 30 days for large (21–80), 60 days beyond. Same-day response if the system is down, two working days otherwise.

  5. Care

    Our work doesn't end at handover.

    A care plan of your choice: Run, Grow or Partner, monthly or yearly.

    Care plans

Two free small changes

Two per project, each up to one engineer-day, asked for before testing ends. Anything larger we write up as a change request with its time, cost and effect on the date, and you approve it before we start.

Your answers

Our dates assume you reply within one working day. Each extra day of waiting moves delivery by one working day.

The warranty by project size

Any defect within the agreed scope is fixed free.

Project sizeEffortFree warranty
SmallUp to 20 engineer-days14 days
Large21–80 engineer-days30 days
HugeOver 80 engineer-days60 days

Same-day response if the system is down, two working days otherwise.

A short weekly update

This is an example of what reaches you each week: what's done, what's next, what we need from you, the risks, and the demo link.

Week 5 update

Example

A made-up project: a booking platform for a clinic

Done
  • Sign-in by mobile number works on the test link.
  • You can now try the doctors' schedule and appointment booking.
Next
  • Payment online or at the visit, then appointment reminders on WhatsApp.
  • The next demo is at the end of next week.
Needs from you
  • The payment gateway account and the wording of the reminder.
Risks
  • If the payment gateway account comes late, delivery moves by one working day for each day of waiting.
Demo link
demo.example

Handover

With the final payment you get:

  • The code
  • A deployment guide
  • Passwords through a password manager (never in chat)
  • A recorded training session for your team
  • The warranty certificate

Let's sketch your project.

Thirty minutes with a founder, no commitment. You leave with clear next steps, even if we don't work together.

Book a 30-minute callMessage us on WhatsApp