WORKSHOP - Today

Aligning the team on validation, workflow, and the road to product readiness.

Three days into MVP 1 validation, this workshop brings every team to one table to surface high-risk findings, agree on the new feature-request workflow, and confirm the path from UAT to end-of-May go-live.

DATE

Saturday, 09 May 2026

ATTENDEES

Technical · Marketing · AR/UI Content

CONTEXT

MVP 1 received 05 May from Eastgate

SESSION 01

UAT Validation Q&A

Each team walks their findings.

High-risk & critical bugs

Surface every Critical and High severity defect found so far. Decide which block end-of-May go-live.

Workflow concerns

Flag any user journey, vendor flow, or admin flow that does not match the agreed scope or brand promise.

Open Q&A

Cross-team questions, clarifications, and dependencies. Capture anything that needs Eastgate input.

Scope vs. SOW gaps

Confirm any deliverable received that does not match the contracted Scope of Work.

EXPECTED OUTPUT

Blockers for go-live Open questions for Eastgate

SESSION 02

New Feature Request Workflow

How new features get raised, reviewed, approved.

Walk the 7-stage workflow

Idea capture → roadmap validation → field research → marketing review → CTO approval → feasibility → CR release.

Roles & ownership

Confirm who raises, who reviews (Marketing Head), who approves (CTO).

Scope-change vs. defect

Agree the rule: defect (Eastgate fixes under SOW) vs. new feature (separate CR with cost and timeline).

Excel request form & tracker

Walk the request form fields, scoring criteria, and the live tracker where requests are logged.

Prioritisation criteria

Agree how requests are ranked — impact on launch, vendor onboarding, customer experience.

EXPECTED OUTPUT

Approved workflow Live tracking sheet

SESSION 03

Progress & Deployment Plan

Where we stand, what comes next.

Overall progress review

Snapshot of MVP 1 deliverables: Public site, Vendor site, Customer app, Admin portal.

Roadmap to 13 May

Confirm the path: validation continues → Monday EOD final feedback → Wednesday 13 May share with Eastgate.

Pilot vendor onboarding

Marketing & Sales readiness to start vendor onboarding immediately after UAT closes.

Staging environment plan

Database cleanup, Coming Soon pages, distribution channels — what's needed to go live by end of May.

EXPECTED OUTPUT

Aligned roadmap Sign-off conditions

CLOSE · 10 MIN

Recap of decisions made and action items with owners. Reminder: every team submits final feedback by Monday 11 Mayconsolidated package goes to Eastgate on Wednesday 13 May.

MVP 1 RECEIVED

Where We Stand and the Path to Vendor Onboarding.

Eastgate delivered MVP 1 on 5 May. Three internal teams are validating the build, and we are on track to go live by end of May through the UAT link with cleaned database, pilot vendors onboarding

Surfaces delivered
Public · Vendor · Customer · Admin

Internal teams
running validation in parallel

End May

Platform goes live
via cleaned UAT environment

PHASE 01

Validate

Internal UAT against scope & documentation.

Three teams in parallel

Technical, Marketing, and AR/UI Content each test the full build against their assigned role.

workshop

90–120 min internal session on 9 May to consolidate findings before final feedback.

Feedback to Eastgate

Consolidated package shared with the development partner on 13 May.

DURATION

5–13 May

PHASE 02

Stabilise

Fixes, categorisation, database cleanup.

Eastgate categorisation

Findings sorted into defects vs. new feature requests. Estimates returned to us.

Bug fixes deployed

Critical and High severity issues resolved before any external user touches the platform.

Database cleanup

Full wipe of UAT test data to give vendors and customers a clean environment.

DURATION

14–30 May

PHASE 03

Go Live & Operate

Marketing team can begin onboarding vendors.

End of May — go live

Real vendors and real customers onboarded on the cleaned UAT environment. Mock payments only.

June – July — operate

Marketing team can onboard vendors and collect real feedback from vendors for continuous improvement. Customer support and platform iterations continue in parallel.

DURATION

End May → August

FROM MVP 1 RECEIPT TO LIVE PAYMENTS

The roadmap from 5 May to 30 May

A milestone-by-milestone view of every checkpoint. Two key moments: go-live by end of May on the cleaned UAT environment.

05 MAY 2026 DONE

MVP 1 received from Eastgate

Public website, Vendor web, Customer mobile (APK), and Admin portal handed over. Validation kicks off across all three internal teams the same day.

05–09 MAY 2026 IN PROGRESS

Internal UAT validation

Technical, Marketing, and AR/UI Content teams run end-to-end testing against scope, journey, and design. Findings logged daily by severity (Critical · High · Medium · Low).

09 MAY 2026 (SATURDAY) TODAY

UAT workshop

90–120 minute session covering UAT Q&A, the new feature-request workflow, and overall progress & deployment plan. Decisions and action items recorded.

11 MAY 2026 (MONDAY)

Final feedback from each team

Every team submits their final report by EOD: Individual Test Report, role-specific deliverables, and any open questions for Eastgate.

13 MAY 2026 (WEDNESDAY)

Consolidated feedback to Eastgate (ESG)

Single combined package sent to the development partner. UAT formally closes from our side.

14–25 MAY 2026

Eastgate categorisation & bug fixes

ESG sorts findings into defects vs. feature requests, estimates, and ships fixes for Critical/High items. We review and accept fixes as they land.

26–30 MAY 2026

Database cleanup & release prep

Full wipe of UAT test data. iOS TestFlight build prepared, Android APK packaged, Vendor web UAT URL cleaned. Coming Soon pages added for any screen not yet ready.

END OF MAY 2026 GO LIVE

Platform goes live

Real vendors and real customers onboarded on the cleaned UAT environment. Customer mobile distributed via TestFlight (iOS) and APK (Android). Vendor web on the cleaned UAT URL. Mock payment UI in place until August.

HOW NEW FEATURES GET RAISED, REVIEWED, APPROVED

Feature Request Workflow.

A structured 7-stage process for handling every new feature idea — from capture to release. The same flow distinguishes defects (Eastgate fixes under SOW) from new features (separate CR with cost & timeline).

OWNER · INTAKE

Anyone can raise an idea. Marketing Head reviews. CTO approves.

FORM

All requests use the Excel request form with mandatory fields, evidence, scoring, and business need.

RELEASE

Approved features become CRs in the McNoon → Eastgate release cycle.

1STAGE 1 · IDEA CAPTURE

ANY SOURCE

Feature idea identified

Vendor meeting · field research · customer feedback · internal team observation

2STAGE 2 · ROADMAP VALIDATION

CHECK FIRST

Check roadmap / WBS

Is this feature already in our plan?

→

Already in roadmap?

Yes / No

→

Yes — already planned

If earlier milestone needed → flag · otherwise no action

3STAGE 3 · FIELD RESEARCH & DOCUMENTATION

EVIDENCE BUILDING

Conduct field research

Vendor interviews · pain points · market evidence · competitor refs

→

Complete Excel request form

All mandatory fields · evidence · scoring · business need

4STAGE 4 · INTERNAL MARKETING TEAM REVIEW

MARKETING HEAD

Marketing Head review

Validates completeness · evidence quality · strategic fit

→

Approved by Mktg Head?

Yes / No

→

No — returned for revision

Revise & resubmit with stronger evidence

5STAGE 5 · TECHNICAL TEAM REVIEW / CTO APPROVAL

CTO

CTO strategic review

Feasibility checked · CTO confirms strategic priority · forward decision

6STAGE 6 · TECHNICAL FEASIBILITY ASSESSMENT

EFFORT & COST

Feasibility assessment

Complexity rating · implementation recommendation · effort estimate

7STAGE 7 · FINAL APPROVAL & CR RELEASE

RELEASED

CR logged · McNoon → Eastgate release cycle

Feature prioritised · added to Eastgate sprint · tracker updated

→

Feature released · tracker updated

Live in next deployment cycle

Process step

Review / approval

Form / action

Decision point

Rejection / return

FROM UAT TO Product Readiness

How the platform reaches pilot vendors and users.

END OF MAY 2026 — GO LIVE

Platform live for pilot vendors & customers

We go live through the cleaned UAT environment.

Deployment timeline

✓

05–13 MAY

UAT validation

All teams test the build, log defects, consolidate feedback to Eastgate.

14–25 MAY

Categorisation & fixes

Eastgate categorises findings (defect vs. feature) and ships bug fixes.

26–30 MAY

DB cleanup & prep

Database wiped clean. Coming Soon pages added.

★

END OF MAY

Go live

Pilot vendors & customers on the platform.

AUGUST

Real payments workflow

Payment integration replaces the mock UI.

📱

Customer Mobile

iOS & ANDROID

iOS distribution

Public TestFlight link. Real customers install via Apple TestFlight app.

Android distribution

APK file shared directly with real customers.

Backend

Cleaned UAT environment after database wipe.

METHOD: TestFlight (iOS) + APK (Android)

🖥️

Vendor Web

VENDOR PORTAL

Distribution

Cleaned UAT URL — https://vendor.uat.evntous.com/ar/vendor/ — shared with onboarded vendors.

Backend

Same cleaned environment as the customer app. No test data carried over.

Onboarding

Marketing-led: welcome packs, walkthroughs, support during the first weeks live.

Payouts & wallet

Mock UI until August. Live payouts enabled with the production payment integration.

METHOD: UAT URL after database cleanup

⚙️

Super Admin Panel

INTERNAL CONTROL PLANE

Distribution

admin.uat.evntous.com — restricted to internal team and authorised admins.

Access

Authentication & access control already in scope. Super admin credentials managed by tech lead.

Used for

User & vendor management, policy config (commission, VAT, refund), audit logs.

Payments module

Mock UI until August. Goes live with the production payment integration.

METHOD: Internal-only UAT URL

DATABASE CLEANUP

Before any real vendor or customer touches the platform, the entire UAT database is wiped clean. Test accounts, mock bookings, dummy vendors — all gone. The environment that real users see is empty, fresh, and production-shaped.

"COMING SOON" STRATEGY

Any screen that is not ready at end-of-May ships behind a Coming Soon placeholder. This protects the user experience while letting us go live with what's done — instead of holding everything back for the last unfinished piece.

END-OF-MAY GO-LIVE

By end of May we are live through the cleaned UAT link. Marketing & Sales lead the first cohort of pilot vendors and real customers. Onboarding scripts and direct support are prepared during validation so day-one is smooth.

REAL PAYMENTS · AUGUST

Until August, every wallet, payout, refund, and payment screen runs on a mock UI. In August, real-money transactions go live in production as per the agreed plan, replacing the mock layer with the production payment integration.

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 ahead of end-of-May go-live.

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 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 real vendors to onboard at end-of-May go-live.

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 end-of-May 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