Skip to content

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 engineer 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, 30 for medium and 60 for large. 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 Scale, 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 sizeFree warranty
Small14 days
Medium30 days
Large60 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.

NawahExample

Week 5 update

A sample 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

Four ways to work with us

Way to workWhat you getWho it suits
DiscoveryThe written requirements, the key screens and a fixed written quote. The documents are yours even if you don't continue with us.For any project beyond a small one, and any idea that isn't clear yet.
A fixed-scope buildEverything on the agreed list, with working software every two weeks and a written warranty.When the scope is clear and written down.
Days on demandDays of engineering, booked in packs, for whatever comes up.For changes, small tasks and open-ended work.
Care plansMonitoring, security updates and fixes after the warranty, with set response times.After every project: Run, Grow or Scale.

What shapes a project

Five things shape the scope and the time of a project more than anything else. Discovery weighs each one for yours.

  • Platforms: web, iOS and Android apps, an admin dashboardEach adds its own screens and tests, and the apps rely on the web side and the dashboard.
  • The number of user rolesMore roles mean more screens, more permissions and more to test.
  • Connections to existing systemsEach one is built and checked against the other system, so it depends on how open that system is.
  • A fully custom designEvery screen is designed from scratch, where our design system already has the parts, in your brand.
  • Moving old dataOld data is mapped, cleaned and checked before launch.

How you get a quote

Your blueprint shows the modules and the weeks. The quote comes from discovery, written for your project.

  1. A free 30-minute call

    With the person who'd lead your project. You leave with clear next steps, even if we don't work together.

  2. Discovery

    We learn your business, write the requirements and design the key screens. The documents are yours even if you don't continue with us.

  3. A fixed written quote

    Discovery ends with a fixed written quote: the scope, the timeline and the warranty, before the first line of code.

Let's sketch your project.

Thirty minutes with the person who'd lead your project, no commitment. You leave with clear next steps, even if we don't work together.