Milestone Progress

Two milestones complete. Three to go, then October launch.

Our roadmap is split into 5 feature milestones based on the project gantt. Milestones 1 & 2 deliver MVP 1 (now in UAT). Milestones 3, 4 & 5 deliver MVP 2. Final UAT and production go-live happen in October 2026.

Overall Project Progress

2 of 5 milestones complete

MVP 1 (Milestones 1 & 2) has been delivered and is moving into UAT. Three milestones remain to complete MVP 2 — followed by final UAT and production launch in October.

40%

Complete

Jan 2026 · Start Now · 05 May Oct 2026 · Launch

M1 · MVP 1

Core Platform & Onboarding

Completed

M2 · MVP 1

Booking, Wallet & UAT

Completed

M3 · MVP 2

Initiate Payment Integration & Messaging

Upcoming

M4 · MVP 2

Customer Web & Vendor Mobile & Complete Payment int.

Upcoming

M5 · MVP 2

Final Features, UAT & Go-Live

Upcoming

What we have delivered (MVP 1)

Core Platform & Onboarding

JAN — MAR 2026

Project setup: Infrastructure, codebase, architecture
Vendor Web: Onboarding & verification, Services & Catalog
Customer Mobile: Onboarding & access, Payment (mock UI)
Admin Portal: Authentication & access control
Public Website: Landing page, Vendors & Services page, Dark/Light mode, SEO

Booking, Wallet & UAT

MAR — MAY 2026

Vendor Web: Booking Mgmt, Wallet/Payouts (mock), Availability, Settings, Dashboard
Customer Mobile: Multi-step Booking, Wallet, Account Mgmt, Notifications
Admin Portal: User & Vendor Mgmt, Policies, Payment Mgmt (mock), Audit Log
04 May: MVP 1 deliverables received
05 May: Staging / UAT live · Android APK · iOS build shared

What's coming next (MVP 2 → October Launch)

nitiate Payment Integration & MessagingReal payment integration across Vendor, Customer & Admin. Messaging with customers, KPI dashboards, reviews.

May — Jun 2026

Customer Web & Vendor Mobile & Complete payment Int.Full Customer Web experience. Full Vendor Mobile App. Booking collaboration, planning tools, real wallet.

Jun — Aug 2026

Final Features, UAT & Go-LiveMarketing & CMS, Analytics, PWA. Final UAT in October. Production go-live and 2-week hypercare.

Sep — Oct 2026

Deployment Plan

Approach, environments, scope & safety.

A phased deployment in two clear stages — staging now, production in October.

Approach

Stage 1 — Staging / UAT

Internal team and selected business users only. Mobile shared as Android APK and iOS build. Goes live 5 May 2026.

Stage 2 — Production

Open to real vendors and customers. Apps published to Apple App Store & Google Play. October 2026.

Safe-switch deployment — rollback in under 15 minutes if needed.
Feature flags — turn features on/off without releasing new code.
Phased vendor onboarding — pilot vendors first, broader rollout after.
Go / No-Go meeting before each deployment.

Environments

Dev

Used by developers to build and integrate features.

Ready

Staging / UAT

Business team tests MVP 1 — web, APK, iOS.

05 May

Pre-Prod

Final dress rehearsal before customer release.

Before October

Production

Live, customer-facing environment.

October 2026

Scope — MVP 1 vs. MVP 2

Module	In MVP 1 (UAT now)	Coming in MVP 2 (by October)
Vendor Web	Onboarding, Services & Catalog, Booking Mgmt, Calendar, Settings, Dashboard, Wallet (mock)	Real payment integration, Messaging, KPI Dashboard, Reviews, Analytics
Customer Mobile Android + iOS	Onboarding, Multi-step Booking, Booking Mgmt, Account, Notifications, Payment (mock)	Real payments, Guest view, Messaging, Planning Tools, Real Wallet, Collaboration
Admin Portal	Login, User & Vendor Mgmt, Policies, Audit Log, Payment Mgmt (mock)	Real payments, KPI Dashboard, Vendor Performance, Marketing & CMS, Analytics
Public Website	Landing, Vendors page, Dark/Light mode, SEO & Analytics	No major changes planned.
Customer Web	Not in MVP 1.	Full Customer Web: Onboarding, Booking, Payments, Wallet, Account
Vendor Mobile	Not in MVP 1.	Full Vendor Mobile: Onboarding, Dashboard, Calendar, Booking, Promotions

MVP1 - Testing & Sign-off

UAT Process

UAT begins 5 May, right after staging deploy.
Test cases cover every screen and journey.
Issues graded Critical · High · Medium · Low.
Daily 15-minute triage call.

Sign-off Criteria

All Critical & High issues fixed or accepted.
End-to-end journeys work without failure.
Performance & security checks pass.
Written sign-off from business stakeholders.

Data Migration & Vendor Onboarding

EVNTOUS is a new product, so there is no migration. The work is about getting vendor data and platform settings ready.

Pilot vendors onboarded during MVP 1 UAT to test the real flow.
Vendor catalog loaded in UAT first, then in production.
Platform settings (commission, VAT, refund) configured by Admin and validated in UAT.
A single Vendor Onboarding Owner tracks readiness daily.

Key Risks & Mitigation

Risk	Likelihood	Impact	Mitigation
UAT defects exceed fix capacity	Medium	High	Daily triage. Engineers on standby. Defer Medium/Low to later release.
Real payment integration delays	Medium	High	Start in early MVP 2. Dedicated owner. Backup provider identified.
Vendor data not ready by go-live	Medium	High	Pilot onboarding during UAT. Onboarding Owner. Staged loading.
App store approval delays	Medium	Medium	Submit apps 3–4 weeks before launch. Assets prepared early.
Performance under real load	Low	High	Load test in pre-prod. Auto-scaling and CDN in design.
Last-minute scope changes	Medium	Medium	Scope locked at end of each sprint. New asks routed to next phase.

Rollback & Go-Live Readiness

Rollback & Contingency

Switch to previous version in under 15 min.
Full DB backup before every deploy.
Engineering + Product Lead hold rollback authority.
Backup go-live: 2 weeks later if October aborts.

Go-Live Checklist

Technical: servers, SSL, monitoring, backups, smoke tests.
Apps: approved on Play & App Store.
UAT: sign-off received in writing.
Operations: support briefed, on-call team in place.
Final Go / No-Go meeting held and recorded.

MVP 2 Testing Framework — Before October Go-Live

Once MVP 2 is built, Eastgate runs a comprehensive 4-quadrant testing framework before final UAT and production go-live. This validates both functional (business) and non-functional (performance & security) requirements of the platform.

Quadrant 01

Automation & Manual Functional Testing

Focused on business requirements — validating the application behaves as expected.

BDD framework used to gather and implement evolving requirements.
Daily automation runs on every deployment with dashboards for live monitoring.
Functional regression suites across DEV and QA environments.
End-to-end (E2E) regression for full user journeys.
Manual testing for scenarios not yet automated.

BDD Automation Jira / Xray Regression

Quadrant 02

Exploratory, Usability & UAT

Manual testing to evaluate the app from a real user's perspective and build confidence in usability.

Exploratory testing by experienced testers using logical thinking.
Usability validation against user requirements and journeys.
UAT scenarios guided with the business team.
Feedback loop — issues collected, analysed, and fed back to development for final adjustments.

Exploratory Usability UAT

Quadrant 03

Performance & Stress Testing

Validates non-functional requirements — speed, capacity, and stability under load.

Client performance test — ensures the app efficiently renders heavy data and UI.
Stress testing — simulates large concurrent user loads (e.g. 1500 simultaneous bookings).
Server monitoring — captures CPU, memory, and throughput before / during / after each test.
Performance reports — response time, error rate, throughput per transaction.
Capacity planning — informs autoscaling and infrastructure sizing for October.

Load Test Stress Test Server Monitoring

Quadrant 04

Security Testing

Identifies and resolves vulnerabilities before customer-facing launch.

OWASP Top 10 (2021) coverage — both manual testing and automated scanning.
Dependency Track — scans third-party libraries for known component vulnerabilities (CVEs).
Penetration testing — executed based on contract requirements; outputs a vulnerability report.
ZAP Scanner for automated web application security testing.
Vulnerability remediation — all Critical and High findings resolved before go-live.

OWASP Top 10 Dependency Track Pen Testing ZAP Scanner

Project Closure & Post-Go-Live Support

Eastgate's standard project closure follows a 6-step process leading to formal sign-off. After go-live, Eastgate provides a structured warranty support model with tiered escalation, SLAs by severity, and continuous improvement reviews.

Project Closure — 6 Steps to Sign-Off

Final System Testing

Final round of QA regression and performance testing (security audits if required). Resolve all critical and high-priority bugs.

User Acceptance Testing (UAT)

Eastgate guides the client through UAT scenarios. Feedback is collected and analysed for final adjustments.

Documentation Delivery

User manuals, operation guides, technical documentation, codebase documentation, and handover documents finalised.

Training Sessions Optional

Functional training for end-users. Transferred materials, videos, and support channels provided.

Go-Live Readiness & Handover

Detailed go-live checklist (backup, monitoring, contingency). Infra setup, credentials, and access rights handed over securely.

Post-Go-Live Support Plan Agreement

Define and confirm SLAs, support channels, and escalation procedures for the post-deployment phase.

Months Warranty

Warranty Period

Eastgate provides a standard post-go-live warranty of 6 months (based on contract scope). Defects related to the delivered solution are addressed at no additional cost during this phase, ensuring a stable transition to steady-state operations.

Support Structure

4-Tier Support & Escalation Path

Support is staffed by key members from the original development team — guaranteeing deep domain expertise, eliminating ramp-up time, and leading to faster resolutions.

L1 · Service Desk

CSR L1 Support

First point of contact. Logs all incidents in Jira, provides initial troubleshooting, escalates unresolved issues to L2.

L2 · Core Tech

CSR L2 Support

Original developers & QA. Performs in-depth investigation, root cause analysis, and develops fixes. Assesses minor change requests.

Escalation Lead

Project Manager

Oversees the support process and ensures SLA adherence. Primary escalation point for high-priority issues. Manages fix deployment.

Strategic

Business Owner

Final escalation point for issues requiring strategic or commercial decisions — including out-of-warranty change requests.

Service Levels

SLA & Severity Matrix

Severity	Definition	Examples	Initial Response	Resolution / Workaround	Escalation Path
Critical	Complete loss of service or significant impact	Platform outage, data loss, major security breach	Within 30 min	Within 4 hours	L1 → L2 → L3 → PM → Business Owner
Major	Substantial impact with no immediate workaround	Significant performance degradation, partial system failures	Within 1 hour	Within 8 hours	L1 → L2 → PM
Minor	Minor impact on functionality or user experience	Minor bugs, cosmetic issues, non-critical requests	Within 4 hours	Within 48 hours	L1 → L2

Support Scope

What's covered during the warranty period

Included Support

Incident Management: Triaging, logging, and resolving production bugs by severity.
Technical Inquiries: Answering questions on architecture, functionality, or behaviour.
Change Request Assessment: Effort estimates for minor change requests.
Hotfix Deployment: Managing urgent fix releases to production.

Tools & Process

Jira — formal ticketing system for tracking, prioritising, and resolving every issue.
Confluence — shared wiki housing troubleshooting guides, hotfix release notes, and runbooks.
SLA enforcement — defined per severity level (Critical, Major, Minor).
Continuous Improvement

Internal Hypercare

Our internal launch-week activities

4-week hypercare — close watch immediately after go-live, with our team on standby every day.
Live dashboards tracking errors, response times, bookings, payments, and vendor activity.
Daily reports for the first 2 weeks, then weekly for one month.
Coordination with Eastgate for any defect escalations during warranty.

Internal Validation After Eastgate Handover

What our internal teams do now that MVP 1 is in our hands.

Eastgate has delivered MVP 1. Three internal teams now validate the build against our agreed scope, prepare for vendor onboarding, and produce individual reports that feed the technical sign-off.

The mandate: every team independently tests the application end-to-end, validates against the agreed scope, and submits a written report. Reports converge into the final technical sign-off before staging deployment moves forward.

TEAM 01

Technical

Validates deliverables against scope & documentation.

Scope & SOW validation

Verify every deliverable received against the agreed Scope of Work and contract.

Documentation review

Validate technical documentation, API specs, architecture docs, and handover notes.

Test case & UAT doc validation

Review the test cases and UAT documents provided by Eastgate; confirm coverage.

End-to-end testing

Run full functional, integration, and regression testing on every surface.

Defect logging

Log every issue with severity (Critical · High · Medium · Low) and reproduction steps.

Sign-off package

Compile the technical sign-off sheet, defect register, and acceptance evidence.

Reports to submit

Individual Test Report Gap, Risk & Issue Log in detail WBS Feature Acceptance Tracker SOW Deliverables Checklist Technical Sign-off report

TEAM 02

Marketing

Validates end-to-end journey & prepares vendor onboarding.

End-to-end journey validation

Walk every user flow as a vendor and as a customer. Confirm the experience matches the brand promise.

Vendor onboarding readiness

Prepare onboarding scripts, vendor welcome packs, and pilot vendor outreach.

Pilot vendor coordination

Identify and coordinate the first cohort of vendors to onboard during UAT.

Brand voice & copy review

Audit all in-app copy, error messages, emails, and notifications for tone and clarity.

Launch readiness assessment

Identify what is launch-ready vs. what needs polish before October go-live.

Marketing collateral plan

Plan content, assets, and campaigns that will run from now to launch.

Reports to submit

Individual Test Report Journey Validation Report Vendor Onboarding Plan Brand & Copy Audit Launch Readiness Assessment

TEAM 03

AR / UI Content Validation

Validates UI accuracy, content, and visual fidelity.

UI vs. design validation

Compare every screen against the approved Figma designs. Flag every visual deviation.

Content & copy validation

Verify all on-screen content, labels, placeholders, and microcopy match the approved source.

Arabic / RTL validation

Test Arabic language rendering, right-to-left layout, and translation accuracy.

Cross-platform consistency

Validate consistency across Vendor Web, Customer Mobile (Android & iOS), Admin, and Public Website.

Accessibility & readability

Check font sizes, contrast, tap targets, and overall readability.

Asset & image audit

Verify all images, icons, and brand assets are correct, optimised, and on-brand.

Reports to submit

Individual Test Report UI Validation Report Content & Copy Audit Arabic / RTL Validation Visual Defects List

From a shipped MVP to a live product.

Five feature milestones, then the October launch.

Two milestones complete. Three to go, then October launch.

2 of 5 milestones complete

What's coming next (MVP 2 → October Launch)

Approach, environments, scope & safety.

Approach

Stage 1 — Staging / UAT

Stage 2 — Production

Environments

Scope — MVP 1 vs. MVP 2

MVP1 - Testing & Sign-off

UAT Process

Sign-off Criteria

Data Migration & Vendor Onboarding

Key Risks & Mitigation

Rollback & Go-Live Readiness

Rollback & Contingency

Go-Live Checklist

MVP 2 Testing Framework — Before October Go-Live

Project Closure & Post-Go-Live Support

Project Closure — 6 Steps to Sign-Off

Warranty Period

4-Tier Support & Escalation Path

SLA & Severity Matrix

What's covered during the warranty period

Included Support

Tools & Process

Our internal launch-week activities

What our internal teams do now that MVP 1 is in our hands.

What we need from the CEO.