Technical Proposal
Technical Proposal

New Qsas Website
Development

Prepared by Bhr Solutions for the National Interactive Entertainment Company (Qsas). A modern, headless, bilingual website designed for performance, security, and editorial agility.

Client: Qsas (NIEC) Prepared by: Bhr Solutions Date: 2026-04-25
01

Executive Summary

After reviewing the requirements document submitted by Qsas, Bhr Solutions presents this proposal for the development and implementation of the website, following best practices in software engineering and adopting modern, flexible methodologies in project management and delivery. In this document, you will find the proposed design and the technical offer for the system that will be developed for you by Bhr.

Bhr Solutions Company is a Saudi limited liability company, with commercial registration number 4030459162. Mobile 0507979869, email [email protected].

We look forward to our partnership with you on this project to be the beginning of a fruitful collaboration.

02

Scope of Work

After reviewing the Statement of Work shared by Qsas, the work has been organized into ten primary streams. Each stream below details the proposed approach.

2.1 Design Implementation & Front-End Development

Framework and Design System Adoption

The front-end will be developed using Next.js with TailwindCSS, one of the most powerful modern stacks for high-performance, highly-interactive web experiences with full control over design fidelity. Bhr will join the two scheduled sessions with the Qsas design team to walk through the Figma system, prototype, and page flow. The full design system (tokens, components, typography, spacing, color, iconography) will be codified into a reusable Tailwind-based component library so every page is built from the same primitives.

Pixel-Perfect Implementation

Every page will be implemented to match the approved Figma design precisely — layout, spacing, typography scale, color system, imagery, and micro-interactions — with design-review checkpoints for sign-off.

Responsive Design Across Devices

Fully responsive across Desktop, Tablet, and Mobile using TailwindCSS Grid, Flexbox, and media queries. Touch-friendly targets, swipe gestures, and optimized form inputs are implemented for mobile and tablet, with both portrait and landscape support.

Bilingual (Arabic / English) and RTL Support

Native Right-to-Left support for Arabic, including mirrored layouts, CSS logical properties, localized typography, localized date/number formatting, and language-aware routing. Language switching is fully content-managed from the CMS.

Animations and Micro-Interactions

All animations and scroll-triggered behaviors defined in the Figma prototype implemented using Framer Motion and GSAP, respecting prefers-reduced-motion.

Brand System Fidelity

Typography, color palette, and the complete visual system implemented exactly per Qsas brand guidelines, enforced through design tokens at the code level.

Cross-Browser Compatibility

Tested across Chrome, Safari, Edge, and Firefox on desktop and mobile, covering recent major versions and operating systems.

2.2 Back-End Development & Secure Architecture

A headless architecture powered by a modern CMS, exposing data through well-documented APIs consumed by the Next.js front-end. This separation of concerns delivers flexibility, scalability, and a significantly better editing experience than traditional monolithic CMSs.

Reusable Page Templates

A library of reusable, composable templates — hero sections, feature grids, content blocks, CTAs, media galleries, team cards, insight cards. Marketing can assemble new landing pages without engineering involvement.

Bilingual Content Model

All content modeled with first-class Arabic and English fields. Admins add, remove, or modify content in either language independently.

Secure and Scalable Architecture

Cloud-ready, container-based architecture with horizontal scalability, stateless app nodes, managed database with read replicas, and clear separation between application, CMS, and storage layers. Secrets handled via a managed vault.

User-Friendly Admin Interface

Designed for marketers, not developers. Live preview, visual composition, rich-text WYSIWYG editing, and guardrails that prevent broken layouts.

Performance Engineering and CI/CD

Static generation (SSG), incremental static regeneration (ISR), edge rendering, automated image and font optimization, lazy loading, code splitting, and aggressive caching. Full CI/CD pipeline (GitHub Actions or Azure DevOps) running automated linting, type-checking, unit tests, build verification, staging on every merge, production on tagged release, and automated rollback.

Global CDN, Cookie Consent, WAF and HTTPS

Served through a global CDN (Cloudflare recommended). Compliant cookie consent banner with category-level controls. WAF layer (OWASP Top 10), bot mitigation, rate limiting. HTTPS site-wide with TLS 1.2+, HSTS, modern cipher suites, and auto-renewing certificates.

2.3 Content Management System (CMS) Implementation

The platform will be built on a headless CMS approach. Every page can be composed and customized fully without being constrained by a fixed theme — content remains cleanly separated from presentation.

Content the CMS Will Manage

  • Page content — add, remove, and modify text, images, and layout blocks
  • Experience listings — templated content type with filtering and tagging
  • Media assets — managed media library
  • Insights and articles — full editorial content type with categories, tags, authors, SEO
  • Team profiles — structured team-member records
  • Events and updates — time-bounded content with scheduling

Marketing Empowerment

The Marketing team can update pages, upload content, manage banners, and create new landing pages entirely through the CMS, with no technical dependency.

CMS Capabilities

  • Role-based access control (Super Admin, Editor, Contributor, Viewer + custom roles)
  • Centralized media library with tagging, search, cropping, and optimization
  • Content scheduling — future-dated publishing and expiry
  • Per-page SEO fields (meta, OG, Twitter card, canonical, robots, structured data)
  • Multi-format content blocks — video, infographics, statistics, embeds, rich media
  • Automated sitemap, robots.txt, structured data; server-rendered metadata
  • No-dev visual edits across every page
  • Future scalability — microsites and modules without architectural rework

Content Workflow

Workflows configured for Draft → Under Review → Approved → Published, with role-based permissions at each stage and email/in-app notifications. Custom workflows per content type.

2.4 Key Website Sections

Development will cover all website pages defined in the approved Figma, including indicative sections:

Homepage About Qsas Experiences (listing + detail) Services Qsas Labs Insights / Knowledge Team / Leadership Contact / Work With Us

Each section is implemented both as a public-facing page and as a CMS-manageable content area, so Qsas can continue to evolve the content independently post-launch.

2.5 Integrations
  • Analytics — Google Analytics 4, Google Tag Manager, Hotjar (or equivalent); event taxonomy agreed with Marketing
  • SEO tools — Google Search Console (verification + sitemap), Bing Webmaster Tools; optional Semrush / Ahrefs
  • Social media — sharing components, OG / Twitter card metadata, embedded feeds where required
  • External booking / platform — REST APIs, webhooks, or embedded flows with any platform Qsas specifies
  • Contact forms — secure handling, validation, reCAPTCHA, confirmation emails, optional file uploads
  • CRM — leads pushed to HubSpot / Salesforce / Zoho or other in real time, with field mapping, deduplication, retry

All integrations use secure authentication (OAuth 2.0, API keys, or token-based), with robust error handling, retry logic, and activity logging.

2.6 Performance, Optimization & Accessibility
< 2.5s
LCP target
< 200ms
INP target
< 0.1
CLS target
99.9%
Uptime
WCAG 2.1 AA
Accessibility

Core Web Vitals. Full Google Core Web Vitals compliance — LCP < 2.5s, INP < 200ms, CLS < 0.1. Target page load under 2 seconds on a good 4G connection.

Fast loading. Lazy loading, modern image formats (WebP / AVIF) with fallbacks, font subsetting, code splitting, tree shaking, CSS / JS minification.

Mobile optimization. Mobile-first implementation, validated on real mid-range mobile devices.

SEO readiness. SSR/SSG, semantic HTML, canonical URLs, sitemap, robots.txt, structured data, clean URL taxonomy.

Accessibility compliance. WCAG 2.1 AA — semantic HTML, heading hierarchy, color contrast, keyboard navigability, visible focus, ARIA, alt text, screen-reader support in both languages.

Uptime & availability. 99.9% application-level uptime via multi-AZ deployment, managed DB with auto-failover, CDN edge delivery, health-check-driven auto-recovery.

2.7 Security & Compliance

Security is addressed by design and continuously verified during operation. The implementation follows the standards of the National Cybersecurity Authority (NCA) and international standards including OWASP Top 10 and W3C.

  • Hardened OS images, least-privilege IAM, network segmentation, private DB subnets, minimized attack surface
  • HTTPS enforced with TLS 1.2+, HSTS, modern cipher suites, auto-renewing certificates
  • OWASP Top 10 protections — input validation, parameterized queries, output encoding, CSRF tokens, secure HTTP headers (CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy)
  • Automated daily DB backups, point-in-time recovery, media backups, tested restore procedure
  • RBAC enforced at CMS and infrastructure layers
  • Secrets managed in a vault (AWS Secrets Manager, Azure Key Vault, or equivalent)
  • Activity logging and admin audit trails — user, timestamp, before/after, tamper-protected
2.8 Testing & Quality Assurance

Quality assurance is embedded throughout the build, not reserved for the end of the project.

  • Functional testing (UAT) — formal UAT with Qsas stakeholders in staging, against agreed test cases
  • Cross-browser — Chrome, Safari, Edge, Firefox (last 2 major versions, desktop & mobile)
  • Mobile — real iOS / Android devices for responsiveness, performance, interaction quality
  • Performance — load testing and Core Web Vitals validation
  • Bug fixing — all P1 and P2 defects resolved before go-live
  • VAPT — Vulnerability Assessment and Penetration Testing on staging by qualified engineers; formal VA Assessment Report delivered
  • SAST / DAST — SAST in CI on every commit; DAST on staging before release
  • Go-live readiness checklist — signed-off, covering performance, security, functionality, content, SEO, backups, monitoring, rollback
2.9 Deployment & Go-Live
  • Cloud-ready architecture — Docker-based deployment targeting any major cloud (AWS, Azure, GCP, DigitalOcean) or on-prem; IaC via Terraform or equivalent
  • Environment separation — distinct Development, Staging, Production with network isolation
  • Configurable settings — env vars and CMS settings; behavior changes without code changes
  • Clear ownership model — RACI matrix agreed before kickoff (domain, DNS, third-party credentials, content)
  • Domain configuration — DNS, domain pointing, email records (SPF / DKIM / DMARC), final cutover plan
  • Final performance optimization — pre-launch pass on Core Web Vitals, bundle size, image weights, cache config
  • Favicons and app icons — complete set including Apple touch icons and maskable variants
  • Sitemap submission — XML sitemap submitted to Google Search Console and Bing Webmaster Tools on go-live
  • Go-live hyper-support — dedicated engineering standby through launch week
2.10 Documentation, Training & Post-Launch Support

Documentation

Full documentation package: CMS user guide, solution architecture document, functional design document, integration design document, configuration and admin guides, go-live plan, rollback plan, and support and escalation matrix.

Training

Two live training sessions for Qsas team members to operate the CMS confidently. Sessions are recorded and accompanied by the CMS user guide.

Post-launch support

  • Bug fixing per the Service Level Agreement
  • Technical support during the agreed period
  • Minor updates and adjustments
  • A ticketing portal for issues and change requests

Maintenance terms beyond the initial support window will be agreed separately as a managed-service arrangement.

03

Systems & Technologies

Software systems are technically divided into the following layers — each chosen to deliver a sustainable system with room for future expansion.

3.1
User Interfaces (UIs)
The interfaces and graphics the user interacts with — designed to be clear, responsive, and satisfying.
3.2
Application Programmable Interfaces (APIs)
The mastermind of the system — business rules, workflows, data access policies, and integration logic.
3.3
Content & Database Management
The layer that lets administrators easily control and change data, persisted in a reliable database.

3.4 Proposed Technology Stack

User Interfaces (UIs)

  • Next.js — pages, routing, SSR/SSG
  • TailwindCSS — styling and design-system fidelity
  • Framer Motion / GSAP — animations and transitions

Next.js is one of the most powerful front-end frameworks for delivering fast, SEO-friendly, highly interactive UIs. TailwindCSS gives fine-grained control to implement the Figma design exactly and adapt elegantly across devices.

APIs

  • Directus — API development and business logic
  • Node.js runtime — custom hooks and extensions

Directus exposes clean, permissioned REST and GraphQL APIs out of the box, supports custom business logic, and integrates smoothly with external systems (CRM, analytics, booking) at scale.

CMS & Database

  • Directus — headless CMS
  • PostgreSQL — primary database

Directus delivers a marketing-friendly admin UI, role-based access, media library, scheduling, and editorial workflows. PostgreSQL is the most reliable open-source relational database.

Deployment & Infrastructure

  • Docker — reproducible environments
  • CI/CD via GitHub Actions or Azure DevOps
  • Cloudflare — global CDN and WAF
  • Cloud-ready (AWS / Azure / GCP / DO)

Containerization guarantees environment parity; CI/CD guarantees safe, repeatable releases; Cloudflare delivers global performance and an application firewall in a single managed layer.

Monitoring & Observability

  • Structured application logs and admin audit trails
  • Uptime monitoring and health checks
  • Error tracking (e.g., Sentry)
  • Analytics — GA4, GTM, Hotjar

Proactive observability is how we sustain the 99.9% application-level uptime target and detect issues before they affect users.

04

Deliverables

4.1

Technical Deliverables

  • Fully functional website (AR/EN, responsive — Desktop, Tablet, Mobile)
  • Complete CMS backend with RBAC, media library, scheduling, SEO editing, workflows
  • All codebases (front-end, CMS extensions, integration code) with full commit history
  • Reusable page templates and component library
  • All required integrations (Analytics, SEO, Social, Forms, CRM, booking)
  • Security hardening (WAF, HTTPS, OWASP, backups, RBAC)
  • Configured environments (Production / Non-Production) with CI/CD pipelines
  • Favicons and application icons applied
  • Sitemap submitted to Google Search Console
4.2

Documents

  • Solution Architecture Document
  • Functional Design Document
  • Integration Design Document
  • Configuration & Admin Guides
  • CMS User Guide
  • Go-Live Plan and Rollback Plan
  • Support & Escalation Matrix
  • VA Assessment Report
  • Go-Live Readiness Checklist (signed-off)
4.3

Service Management & Changes

A ticketing portal will be provided to receive requests and change items. All requests are handled per the Service Level Agreement, with first-response times mapped to the severity tiers (Critical / High / Medium / Low) defined in the Qsas SOW.

4.4

Knowledge Transfer

  • Two live CMS training sessions for the Qsas team
  • Recorded versions of both training sessions
  • A knowledge-transfer handover session to the Qsas technical stakeholder
05

Project Management

5.1 Methodology

Bhr's team is a group of specialists with broad expertise in programming, development, and project management. Several of our specialists hold multiple certifications including PMP from PMI, and SAFe certifications including SAFe Product Manager / Product Owner and SAFe Scrum Master, in addition to the Scrum Developer Certificate.

Accordingly, the Agile methodology is followed in project management — short development stages ("Sprints") with continuous improvement of the product, presenting real initial products, evaluating them, and incorporating feedback.

The following software and techniques will be used to manage the project:

  • Azure DevOps to follow the workflow with developers
  • Git for saving software files with their development history
  • SharePoint File Management Site
  • Teams for communication and meetings

5.2 Team during the development period

Member Function Number Group
Project Supervisor General supervision; ensuring progress according to plan and timely deliveries 1 NIEC (Qsas)
Project & Development Manager Manage project, tasks, resources; design system architecture; link development teams; ensure work is received and tested 1 Bhr
Developer of User Interfaces Develop UIs and ensure integration with CMS 2 Bhr
CMS Developer Prepare infrastructure; launch and update systems; ensure stability through changes 2 Bhr
Integration Developer Develop and implement integrations with external services; secure API connections; data synchronization 2 Bhr
Administrative & Documentation Coordinator Coordinate teams, prepare reports, manage documentation 1 Bhr
5.3

Project Schedule

Note on the timeline: Per the Qsas Statement of Work (Section 10), the final development timeline will be agreed upon following the review of the Figma files and final scope confirmation. The schedule below is presented as an estimated, indicative project timeline based on the scope outlined in this proposal. The exact plan and milestone dates will be confirmed jointly with Qsas during project kickoff after the project is awarded.

Based on our experience delivering similarly scoped website projects on Next.js with a headless CMS, Bhr estimates that development can be completed within 3 to 4 weeks from kickoff to go-live, assuming the design files, content, and stakeholder availability are in place as outlined in the assumptions section.

Milestone Week 1 Week 2 Week 3 Week 4
Kickoff, design handover & environment setup
Front-end development & component library
CMS configuration & content modeling
Integrations (Analytics, SEO, CRM, Forms)
Performance, security & accessibility hardening
Testing (UAT, cross-browser, VAPT)
Training, documentation & Go-Live

Activities run in parallel where possible — for example, front-end development and CMS configuration overlap during weeks 2 and 3. A weekly progress update is shared with Qsas, and any change to the timeline is raised through the agreed change-management approach.

06

Service Level Agreement

6.1 Goal

An SLA is an agreement between the service provider and the beneficiary that defines services, expected service grade, and the metrics by which it is measured — including response times, availability, and uptime.

6.2 Communication and Escalations

First-level service is via the ticketing portal. Delays or errors are escalated through three levels of administrators agreed at kickoff.

6.3.1 Main Location

Service Completion Availability
Edit content on a page 3 hours Sun–Thu, 8 am – 5 pm
Simple page-design modification 2 days Sun–Thu, 8 am – 5 pm
Radical page-design change 3 days Sun–Thu, 8 am – 5 pm
Develop new page (no DB / API) 5 days Sun–Thu, 8 am – 5 pm
Extract data from website 1 day Sun–Thu, 8 am – 5 pm
Fix S1 critical issues 2 hours 24/7
Fix S2 urgent issues 6 hours 24/7
Fix S3 important issues 12 hours 24/7
Fix S4 incident issues 1 day 24/7

6.3.2 Content Management System

Service Completion Availability
Add a new user 3 hours Sun–Thu, 8 am – 5 pm
Modify user permissions 3 hours Sun–Thu, 8 am – 5 pm
Delete a user 3 hours Sun–Thu, 8 am – 5 pm
Add a new integration 5 days Sun–Thu, 8 am – 5 pm
Fix S1 critical issues 2 hours 24/7
Fix S2 urgent issues 6 hours 24/7
Fix S3 important issues 12 hours 24/7
Fix S4 incident issues 1 day 24/7

6.4 Critical Problems Breakdown

S1 Critical Service is not available to all users
S2 Urgent Service unavailable to some users; inability to sign in
S3 Important Service is slower than usual
S4 Incident Design errors or bugs

6.5 Security Restrictions and Obligations

Restrictions. The agreement guarantees 5 change requests per month (not including issues), non-transferable to the following month. Radical amendments are studied and quoted separately.

Security Commitments. All service data must be saved inside Saudi Arabia.

07

Assumptions

This proposal is based on several assumptions, including:

Visual Identity Directory Website design presence Content and images presence Stakeholders available

Let's build something exceptional

Bhr Solutions for Information Technology — a trusted technology partner for prominent SMEs across the region, delivering enterprise-grade software with the personalised service of a focused team.

CR 4030459162 · VAT 311208039700003