Statement of Work (SOW) — Showprima November Launch
Date: 9 September 2025
 Prepared by: Charlie Middleton (Contractor)
 Client: Showprima / GlobalGala (Mohamed)

1) Summary
We will prepare the Showprima ticketing website for November on‑sale and the December event, focusing on reliability at checkout, smooth seat selection, and clear communications to customers and door staff. This is a pragmatic, time‑boxed engagement aimed at launching confidently without a risky rebuild.
2) Objectives (what success looks like)
Customers can choose seats, pay securely, and receive ticket emails that arrive in inbox.


No overselling: the system prevents double‑booking even during busy moments.


Door staff can quickly scan tickets (or use a printable list) and resolve issues.


Admin can create events, see orders/attendees, resend tickets, and process refunds.


The site looks tidy and modern, especially on mobile, without a deep redesign.


3) Scope of Work (this cycle)
Reliability & Checkout
Harden payment flow so each payment is processed once (duplicate protection).


Ensure seat and general admission stock cannot be oversold under load.


Add light cart timeout or recovery so abandoned seats return to availability.


Tickets & Email
Send tickets via a reliable mail service, with domain authentication (SPF/DKIM/DMARC).


Add resend ticket and a printable door list as a backup.


Seat Picker & UI Polish (light)
Improve seat map clarity (legend/contrast/selected states) and helpful copy.


Tidy key screens (buttons, forms, messages) so the site feels premium.


Door Operations
Ensure the check‑in page records who scanned what and when (simple audit log).


Confirm refunds reopen seats correctly.


Monitoring & Process
Add basic alerts if payments or emails fail.


Prepare a short rollback plan and backup routine for launch week.


4) Not in Scope (deferred)
Full visual rebrand or deep design‑system rollout.


Framework changes (React/Vite) or large Laravel upgrades.


Advanced offers (promos, vouchers) or settlement/accounting modules.


Multi‑language and complex reporting.


(These can be scheduled after the event.)
5) Timeline & Milestones
Duration: ~13 days of work across September–October (we have two months total runway; work will be batched sensibly).
Kick‑off & Discovery (3 days): confirm scope, access, and first fixes; test plan.


Build & Hardening (8–9 days): payments, seats/stock, email, door ops, UI polish (light).


Testing & Launch Prep (1–2 days): pilot purchases, parallel seat tests, deliverability, checklist.


On‑sale support (optional): remote standby during the opening window.


We will agree exact calendar dates after access is confirmed.
6) Pricing & Payment
Fixed MVP price: £5,850 (13 days @ £450/day).


Contingency: 10% (£585) held aside and only used if needed; unused portion is not billed.


Optional polish block: +2–3 days (UI refinements) £900–£1,350.


On‑sale standby (optional): remote half‑day £225 / full‑day £450.


Payment schedule: 40% at start, 40% at staging sign‑off, 20% 10 business days after go‑live (or after the on‑sale window if standby is used).
All amounts tax‑inclusive. Third‑party service fees (e.g., email provider) are billed at cost with prior approval.
7) Client Responsibilities
Provide timely access: cPanel/SSH, database, payment gateway dashboard (test mode), and sender email/domain (for SPF/DKIM).


Nominate a single decision‑maker for quick approvals during the sprint.


Supply or approve event details (dates, pricing, policies) and copy.


8) Acceptance Criteria
Checkout: test purchase succeeds; 3‑D Secure handled; duplicate payment is ignored safely.


Seats: parallel attempts on the same seats result in no oversells.


Tickets: confirmation email delivered to inbox with QR/lookup; resend works.


Door: scan marks ticket as used; printable list available.


Refunds: processing a refund reopens seats.


Mobile: seat selection and checkout usable on common devices.


9) Change Control
Any work outside this scope is quoted and approved in writing before starting. We can add small items using the contingency or the optional polish block.

10) Risks & Mitigation
Seat selection under load → We add protections so only one buyer gets a seat.


Email deliverability → We use a reputable sender and authenticate the domain.


Third‑party hiccups (Stripe/PayPal) → We add retries and clear error messages.


Timeline → We keep a small buffer and stage work so the November date is protected.


11) Warranty & Support
Bug‑fix window: 14 days after go‑live (for items covered in this scope).


Optional care plan can be added post‑launch for updates and monitoring.


Signatures
Client: _________________________ Date: ____________
 Contractor: ______________________ Date: ____________