Two years in Dubai

MVP Development for UAE Startups

I ran technical operations for a Dubai company for close to two years, which is where most of what is below comes from rather than from research. An MVP built for the UAE market has a few decisions baked in early that a generic build does not.

The timezone is also the easiest overlap of any market I build for: a UAE working day and mine line up almost entirely, so the weekly build review never needs an early or late call for either of us.

Book a 30-min call See pricing Contact Me

How this actually works

What is different about building an MVP for the UAE

Local payment rails, decided at scoping, not bolted on later

Stripe alone under-serves the Gulf market. If the MVP needs local card schemes, cash-on-delivery flows, or Emirates ID-based KYC, those get counted as their own screens at scoping so the total reflects the real build, not a Western-default assumption that gets expensive to unwind.

Arabic and RTL are a design decision, not a translation ticket

If the product needs right-to-left layout, that has to be decided before the design system is built, not patched into it. A UI built assuming left-to-right and retrofitted for RTL usually needs large parts of the frontend rebuilt.

The screens still cost $80 each, wherever they are built for

A UAE-market screen with local payment integration or RTL layout is priced the same as any other screen. What changes is the count and the build detail, not the rate.

Near-total timezone overlap

There is no asynchronous handoff to design around. The weekly build review happens inside a normal working day for both of us, which for a fast-moving MVP build matters more than it does for a slower retainer engagement.

Data residency questions come up early with government and enterprise buyers

If the MVP is aimed at a DIFC, ADGM, or government-adjacent buyer, where data physically sits becomes a real question sooner than most founders expect. Better to know the answer before the first pilot conversation than to discover the gap during it.

What you're actually buying

Scoping, the build, and launch

Week 0

Scoping: every screen counted and priced

We go through everything you think the MVP needs, screen by screen, and cut it down to what actually has to exist to test the thing you're testing. Every remaining screen gets counted and priced at $80, across whichever platform it needs — mobile, web, desktop, or Linux. You leave with a scope doc and a total, not an estimate that moves once we start.

The build

Design and development, with you seeing it every week

My Panicle Tech design and engineering team builds it, screen by screen; I own the architecture, the code review, and the calls that are expensive to get wrong. You get a working build to look at every week, not a status update. If a screen turns out to need more than was scoped once it's half-built, that gets priced honestly before it's fully built, never absorbed silently.

Launch

Handover, and two weeks of me still answering the phone

Deployed, monitored, and documented well enough that the next engineer who touches it isn't guessing. Two weeks of post-launch support are included, because the bugs that matter are the ones your first real users find, not the ones QA finds.

Why me, for this market specifically

Experience, not a capabilities deck

Plenty of teams can build screens. Fewer have shipped for UAE specifically, been wrong about it, and had to fix it with their own name on the commit. Here's what I'm bringing.

CTO at a Dubai-based commerce platform for close to two years
Built local payment and KYC integrations for the UAE market
Near-total timezone overlap with Gulf working hours
Same $80 per-screen rate, RTL and local integrations priced honestly, not padded

Pricing

from $80 a screen. Counted up front.

Design and build, screen by screen, across mobile, web, desktop, and Linux. My Panicle Tech team designs and builds it; I own the architecture and the technical decisions as advisor on the project. Added screens are priced at the same rate, never renegotiated after the fact.

MVP Design & Development

from $80

per screen

Scoping week: every screen counted and priced up front
UI/UX design and full-stack development, screen by screen
Built by my Panicle Tech design and engineering team
I own the architecture, code review, and technical direction
Mobile, web, desktop, and Linux apps, whichever the product needs
Deployment, monitoring, and handover documentation
Two weeks of post-launch support
Added screens priced at the same per-screen rate, never renegotiated after the fact
Option to continue on a fractional retainer

Full pricing and the scoping process →

Questions

UAE founders, specifically

Do you build RTL and Arabic-language interfaces?

Yes, and it has to be decided at scoping so the design system is built for it from the start rather than retrofitted. Retrofitting RTL onto a left-to-right build usually costs more than building it in from screen one would have.

Can the MVP use local payment methods instead of just Stripe?

Yes. Local card schemes, cash-on-delivery flows, and Emirates ID-based KYC are common gaps in a default Western integration set for this market, and they get scoped and priced like any other screen.

Have you actually shipped for this market before?

Yes. I led technical operations for a Dubai-based commerce platform operating across the UAE and regional markets, which is where the specifics on this page come from rather than general research.

More general questions about pricing, timeline, and what's included are answered on the main MVP development page.

Earned, Not Claimed

What the founders and teams I build with say

I had the pleasure of working with Kunal while building out my MVP and I have to say that it was pleasure to both interact and work with him and his team. As a first time founder, I had a lot of self doubt and internal ruptures, however Kunal's calm, never-say-die and never-panic attitude often helped bring me back to center. I can't vouch for him enough.

Anand Tahiliani

Founder, Debaser Technologies

I had the pleasure of working closely with Kunal during my time as a Product Manager at DhunGuru. As our CTO, Kunal and his team at Panicle Tech worked closely with me across the entire product journey, from building and launching our mobile apps to developing and maintaining our web platforms. His technical expertise, ownership, and willingness to collaborate made a real difference, and I genuinely enjoyed working with him throughout the journey.

Anirudh Joshi

Product Manager, DhunGuru

Kunal helped us architect Mosler's core platform, connecting smart lock hardware, our cloud dashboard, and PMS integrations into one reliable system. The foundation he helped design in those early days still scales with us today.

Pranav Kapoor

Co-Founder, Mosler

If you need more than a build