Skip to main content
Project Management

My Project Kickoff Process: What I Do Before Writing a Single Line of Code

5 min read

How a senior UAE full-stack dev preps for a project before code starts — real workflow, tools, and mistakes avoided.

Laravel Next.js app startupUAE web development agencyproject kickoff discovery phasedeveloper communication UAESarah Nasereldeen tech blog

Last June, I walked into a meeting with a logistics startup in Dubai that needed a Laravel and React Native app to track delivery vans. They showed up with a 30-page PDF of "features" and no priorities. By the end of the day, I had them walk out with a single sticky-note board of core needs. That’s what happens when you skip the discovery phase.

Defining "Ready to Build" Starts With the Client's Definition of Success

I don’t care how many Next.js 14 features you read about this week — if you don’t align on success metrics first, your project’s already behind. Early in my career (pre-PMP), I built a Laravel inventory app where 80% of the code got deleted because the client never clarified they needed barcode scanning integration until the end. Now, I make them write their goals in plain English: "Reduce warehouse errors by 30%" or "Cut checkout time to 90 seconds". If it’s not measurable, it doesn’t go in the spec.

For Tawasul Limo — that bilingual luxury booking platform — we spent two days mapping user flows in Figma before picking tech. Turns out, Arabic language support across push notifications (with Expo) wasn’t about right-to-left text, but how date formats broke on iOS. You don’t catch that unless you prototype translation mechanics early.

Communication Channels: No More 2 AM Email Chaos

Most developers hate project management until they’ve managed one client who replies to 5 bullet points with 27 paragraphs of non-technical stakeholders cc’d. On the Greeny Corner plant ID app, I tried Slack, email, and Notion. We ended up using Microsoft Teams with custom tabs per module — and I learned to schedule updates at 3 PM UAE time, not morning (spoiler: developers in Ajman aren’t early birds).

Now I create a communication plan template:

  • Code reviews every Monday 4 PM (blocked in everyone’s calendar)
  • UI/UX feedback turned into Figma comment threads
  • Client Q&A via Calendly for 15-minute slots Tuesdays/Thursdays
  • Use GitLab issues for technical blocking points only

Picking Tech That Won’t Haunt Me at 2 AM

I’ve lost sleep over Firebase Firestore quotas that spiked to $800/month for a UAE grocery app during Ramadan sales. That’s why today’s kickoff includes a tech stack meeting where we compare:

  • Laravel 10 with Filament vs. Supabase for Admin panels (depending on client dev team)
  • React Native 0.76 vs. Flutter for MVP cross-platform apps (Expo SDK 54 is still my default unless there’s heavy AR)
  • Laravel Horizon vs. Redis + Node workers for queue management (see: Laravel Queues in Production for UAE Clients)

One mistake? Building a Vue store API with Laravel Sanctum before knowing the client’s team had zero experience maintaining Vue JWT auth. Spent 3 weeks retooling it to Inertia.js post-launch.

Anticipating Roadblocks Before They Exist

The best kickoff includes preemptive damage control. For a Riyadh healthcare portal needing Emirati Arabic dialect support, I made 2 lists:

Client Risks

  • Potential last-minute feature addition (government compliance stuff)
  • Slow legal review for patient data fields

Tech Risks

We added 3 buffer days per sprint — and still ended up using 2 of them when the client’s IT director left mid-project.

FAQs About Web Project Kickoffs

How important is the discovery phase in avoiding project delays?

Critical. One Abu Dhabi fintech client skipped discovery, and we had to rework 4 API endpoints halfway through. Spending 5–7 days upfront on prototyping interfaces and reviewing legacy systems usually saves 50+ hours later.

How do you explain technical limitations to non-technical clients?

I show them production screenshots. Told a UAE hotel chain’s marketing team "Lottie animations won’t render smoothly on Safari without polyfills" — blank stares. Shared a TikTok of the glitch effect on an iPhone — immediate buy-in. For more: Communicating Progress to UAE Clients

What determines your choice between Next.js app/router and pages/router?

If it’s a bilingual corporate site like DAS Holding’s, app/router handles dynamic routing better with i18n in 2026. For quick UAE startups needing A/B testing, pages/router still works — see My Next.js App Router Migration Experience

When should you involve QA in the project kickoff?

Day 1. For the Reach Home Properties real estate site, our QA engineer found that Arabic property descriptions broke pagination on Android browsers during setup. Early QA saves way more time than fixing a month later.


I’ve shipped 40+ web projects in the UAE and GCC since 2016 — from Laravel-Expo logistics apps to bilingual React-WordPress portals. If you want a kickoff that avoids feature bloat and actually works with your team’s skills, get in touch, or book a free 30-minute call: Book Consultation.

S

Sarah

Senior Full-Stack Developer & PMP-Certified Project Lead — Abu Dhabi, UAE

7+ years building web applications for UAE & GCC businesses. Specialising in Laravel, Next.js, and Arabic RTL development.

Work with Sarah