This page is the whole engagement, written down and drawn out: the four stages every project moves through, a week-by-week timeline, what is always included, how updates work after launch — and the full terms we sign. Read it before the first call, so the call is about your product.
Each stage ends with something you can hold — a document, a prototype, a working release — and your written sign-off before the next one starts. Nothing moves forward on assumption.
We learn your business before we touch a design: who your customers are, how money flows through the company, which systems you already run, and what "done" must look like. Everything we agree becomes the written scope the whole project is measured against.
| Brokerage website — 14 pages, Buy / Rent / Off-plan search | Included |
| Bayut · Dubizzle · Property Finder listing feeds | Included |
| WhatsApp enquiry routing to CRM | Included |
| Arabic language version | Included |
| Fixed price · 50 / 25 / 25 milestones | AED — |
| Timeline | 8 weeks |
Brand system first, then real screens with your real content. You click through an interactive prototype of the product on your own phone and desktop before any engineering starts — so design decisions are made on the actual experience, not on a static picture.


Engineering runs in weekly releases on a private staging link — you watch the product come together rather than waiting for a reveal. Integrations, data migration, payment flows and testing happen alongside the build, not after it.
We handle go-live end to end — DNS, SSL, hosting, analytics, search indexing, store submissions — and stay on afterwards. Every product on our portfolio page is still running because the relationship did not end at launch.
Illustrative — a typical brokerage website with portal feeds and CRM routing. Your proposal carries the real dates, but the shape is always this: short Discovery, design you sign off, then weekly releases until launch.
These are not add-ons. If a proposal from anyone leaves them out, ask why.
Most clients start with a fixed-scope project and move to a retainer once the product is live and growing.
A website, platform, app or brand with a written scope, fixed price and dated timeline. The most common way to start.
A monthly allocation of design and engineering for products that keep evolving — new features, campaigns, integrations, growth work and support.
Run our real-estate CRM and portal engine under your own brand — the same platform behind Propfusion — deployed in days, not months.
"What happens when I need a change?" is the question every client asks. Here is exactly what happens — every time, whether it's a new listing page or a new payment flow.
A sentence is enough. We reply the same working day with what it involves, whether it's covered by your retainer or warranty, and when it will be on staging.
Nothing touches your live product. You review the change on staging on your phone or desktop — with your real content — and ask for tweaks.
A written "approved" from you is the trigger. We deploy outside your busy hours, watch analytics and errors for 24 hours, and send you the confirmation.
| Type of request | First reply | On staging | Covered by |
|---|---|---|---|
| Something is broken — a page down, a form not sending | Within hours, any day | Same day | Warranty · Retainer |
| Content change — text, images, a new listing or offer | Same working day | 1–2 working days | Retainer · or you, via the admin |
| New feature — a page, an integration, a flow | Same working day, with a quote or hours estimate | Scheduled on the roadmap | Retainer · or a change request |
| Third-party change — a portal or API update | We usually notice first | As soon as the provider ships | Retainer |
Fifteen plain-language clauses — scope, fees, revisions, IP, confidentiality, warranty, retainers, termination, liability, governing law. Written to be read before the first call.
You now know exactly how a project runs with us. The first call is about your business — what it needs, what it should cost, and when it can be live.