PROCESS

One process. No surprises.

Two families, the same four steps. A site runs through them in 24 to 48 hours; a product in 4 to 16 weeks. You always know which step you are on — and nothing starts before the scope, the price and the date are in writing.

  1. 01WRITTEN SCOPETell us what you want to build and it becomes a written technical scope.
  2. 02PRICE AND DATE CLOSEDOne fixed price and a delivery date, agreed before we start.
  3. 03BUILDStructured development, with a build you can open — not a slide about progress.
  4. 04DEPLOYLive on the agreed date. Code, documentation and credentials under your accounts.

WEBSITES · 48 HOURS

The hour-by-hour breakdown.

The full published sequence. Nothing about the build happens outside these hours.

  • SCOPE LOCKED
  • DEVICE QA
  • ONE REVIEW ROUND
  1. H00 – H02BLOCK 01/06 · 2 H

    Brief confirmed

    The scope is checked against the published list for your tier. Nothing is discovered later — if it isn't on the list, it's scoped and quoted separately before the clock starts.

  2. H02 – H06BLOCK 02/06 · 4 H

    Structure & direction

    Pages, sections and copy direction are set. Brand assets and existing copy are migrated in; anything missing is flagged immediately, not on day three.

  3. H06 – H30BLOCK 03/06 · 24 H · LONGEST

    Build

    Pages, components and motion are built against the confirmed structure. This is the longest block because it's the only one doing the actual work.

    • PAGES
    • COMPONENTS
    • MOTION
  4. H30 – H36BLOCK 04/06 · 6 H

    Internal QA

    Every page checked on real devices and browsers — forms, links, load times, spelling. Nothing goes to review broken.

    • REAL DEVICES
    • FORMS
    • LINKS
    • LOAD TIMES
    • SPELLING
  5. H36 – H44BLOCK 05/06 · 8 H

    Review round

    The build is sent for one consolidated round of changes. Feedback is collected once, not dripped in over days.

  6. H44 – H48BLOCK 06/06 · 4 H

    Revisions & launch

    Changes from the review round are applied, checked again, and the site goes live. Handover includes what you need to keep running it.

Where the tiers differ

A One Page typically clears the whole sequence toward the 24-hour end. A Signature build uses closer to the full 48. The sequence is the same either way — only the size of the build block changes.

THE CLOCK · H00 → H48
  • One PageAED 2.900around hour 24
  • PremiumAED 4.900around hour 36
  • Signaturefrom AED 7.900at hour 48

PRODUCT · W00 → DELIVERY

From first message to a product in production.

Eight steps, the same at every level. You always know which step you are on.

  1. 01

    Brief

    Tell us what you want to build — through the ten questions, a message or a call.

  2. 02

    Scope

    Your idea becomes a written technical scope with a fixed price and delivery window.

  3. 03

    Design

    UX flows and UI design for every screen that will be built.

  4. 04

    Build

    Development in structured sprints — with a staging build you can open, not a slide about progress.

  5. 05

    QA

    Testing across devices, browsers and edge cases before anyone else sees it.

  6. 06

    Launch

    Deployment, app-store submission where applicable, production hardening.

  7. 07

    Handover

    Source code, documentation and credentials — all under your accounts.

  8. 08

    Growth

    Optional: ongoing development, maintenance and new features.

W00 → Delivery. The same rhythm, every level.

Every project runs the same structured phases. The windows stretch or compress with your complexity level — pick one to see how.

TYPICAL DELIVERY WINDOW 6–10 WEEKS · PRICE from AED 45.000

  1. W00Brief confirmedScope, fixed price and delivery window signed off.
  2. W01Product structureUser flows, requirements and technical architecture defined.
  3. W02UX / UIInterface design and a working design system.
  4. W03–06DevelopmentStructured sprints — with a staging build you can open.
  5. W06–07QATesting, bug fixing and device / browser validation.
  6. W07–08LaunchDeployment, store submission where applicable, handover.
  7. W08Delivery

Windows shown are typical for each level, not guarantees — your proposal states your exact delivery window before anything is signed.

THE PROPOSAL

What you sign before we start.

Every project gets the same document before any money moves. This is the shape of it.

  • One fixed price — a number, not an hourly guess
  • A delivery date — in hours for a site, in calendar weeks for a product — signed
  • Itemized scope: screens, features, integrations
  • Two payment milestones: 50% on award, 50% on delivery
  • What's excluded, in writing — no ambiguity
  • Change-order terms agreed up front
  • You keep 100% of the code
DEPLOY STUDIO — FIXED PROPOSALBLANK TEMPLATE
FIXED PRICE
to be filled in
DELIVERY DATE
to be filled in
ITEMIZED SCOPE
SCREENS · FEATURES · INTEGRATIONSto be filled in
OUT OF SCOPE
to be filled in
PAYMENTS
50%ON AWARD50%ON DELIVERY
CODE
100% YOURS
SIGNATUREto be filled inSIGNED BEFORE WORK STARTS
The shape of the proposal: the blank fields are filled in with your project.

TEN QUESTIONS · NO EMAIL

Find out what it costs in two minutes.

It returns complexity, delivery window and investment range. We only ask for an email if you want the written scope.

Entry prices: WEBSITES from AED 2.900PRODUCT from AED 25.000