Brainforia Edwelltech FZC – Change Request Proposal SAL-QTN-2026-00008

Techno-Commercial Proposal · Change Request Bundle

Brainforia Edwelltech FZC
Platform — CR1, CR2 & CR3

Three change requests to extend the Brainforia Edwelltech FZC platform: new customer journey with feature management, Ivory services API integration with full attribution analytics, and a Communi community platform integration or custom build.

1

CR1 — New Customer Journey & Services / Feature Management by Super Admin

2

CR2 — Ivory Services API Integration (B2C & B2B2C)

3

CR3 — Communi Platform Integration or Build a Custom Community Platform

Prepared By

Bettroi FZE

Biji Thomas
CEO & Principal Consultant
admin@bettroi.com

Prepared For

Brainforia Edwelltech FZC

Sharjah, UAE

Reference

SAL-QTN-2026-00008

Change Request Bundle
Techno-Commercial

Date

10 Mar 2026

Valid 60 days
AED · UAE

01 — EXECUTIVE SUMMARY

Context & Scope of Change Requests

Bettroi FZE is currently executing the agreed scope of work for the Brainforia Edwelltech FZC for the Proposal number SAL-QTN-2025-00034 V2 dated 24 Oct 2025. During the engagement, three strategic change requests have been raised by LBL that fall outside the original scope. This proposal covers the technical approach and commercial terms for all three CRs, enabling LBL to evaluate and approve them independently or as a bundle.

CR1 and CR2 will be executed concurrently (Weeks 1–3) across dedicated development streams, reducing overall calendar delivery to 6 weeks. CR3 commences sequentially in Week 4 once CR1 and CR2 are signed off, as the community platform's subscription gating depends on the entitlement engine delivered in CR1.

02 — CR1: NEW CUSTOMER JOURNEY & SERVICES / FEATURE MANAGEMENT BY SUPER ADMIN

Change Request 1 3 Weeks · AED 6,000

Direct B2C Onboarding, Tiered Subscriptions & Feature Controls

1

Direct B2C User Registration & Onboarding Flow

New individual users register directly on the LBL platform — independent of clinic referrals. Onboarding journey includes account setup, profile completion, and automatic assignment of free-tier entitlements on registration.

2

Tiered Subscription & Entitlement Engine

Feature access is governed by subscription tier: Free community, Paid community, and premium subscription levels. Subscription definitions, upgrade/downgrade flows, and billing hooks are included. Paid features are accessible only after verified subscription or admin grant.

3

Super Admin Manual Override — User-Level Feature Control

Admin panel for manual override of individual user entitlements irrespective of subscription tier. Override log and audit trail maintained. Supports edge cases such as trial grants, complimentary access, and corrective adjustments.

4

Clinic Feature Dashboard — Enable / Disable Controls

Clinic portal extended with a feature visibility panel. Super admin controls which features are active per clinic. Disabled features remain visible to the clinic with a "Request Activation" prompt, signalling upgrade opportunity.

5

Request-to-Enable Workflow (Clinic to Super Admin)

Clinics submit feature activation requests with justification. Super admin reviews, approves or declines, and activates on approval. Payment-confirmation-gated activations supported, with notification to the clinic on status change.

03 — CR2: IVORY SERVICES API INTEGRATION

Change Request 2 3 Weeks · AED 6,000

B2C & B2B2C Ivory Service Consumption with Full Attribution Analytics

1

Ivory MagicLink API Integration

Full integration per Ivory's API documentation. The LBL platform generates and manages MagicLinks for both direct (B2C) users and clinic-referred (B2B2C) users to access Ivory assessments and services seamlessly.

2

User Attribution & Source Tagging Layer

Every MagicLink session is tagged with origin: LBL Direct or Partner Clinic, with partner clinic ID stored. Attribution metadata is linked to session and completion events, enabling downstream analytics to distinguish channels precisely.

3

Super Admin Analytics Dashboard

Backend analytics for Ivory consumption: total sessions by channel and date range, LBL Direct vs. partner-originated, and per-clinic drill-down. Individual user-level view available for support and audit purposes.

4

Ivory Partner Portal — Read-Only Login

Dedicated login for the Ivory team showing aggregate service consumption: total sessions, LBL-originated vs. partner-originated, and per-partner summaries. No LBL user PII is exposed in the partner view.

04 — CR3: COMMUNI PLATFORM INTEGRATION OR CUSTOM COMMUNITY BUILD

Change Request 3 3 Weeks · AED 6,000

Communi Integration or Standalone Community Module Build

1

Communi API Feasibility & Integration Assessment

Technical assessment of Communi's available integration packages for compatibility with the LBL tech stack. If a stable, tested integration path exists, it will be implemented directly using Communi's supported packages.

2

Custom Community Module (if Communi Integration Unavailable)

Standalone community microservice built as a reusable product: discussion threads, topic categories, member directory, moderation tools, announcement board, and in-platform notifications. Architected for reuse across other Bettroi client projects.

3

SSO & Profile Sync with LBL Platform

Community platform shares authentication with LBL. User profiles, roles, and subscription tiers synchronise automatically so community access gates reflect the entitlements defined in CR1.

4

Subscription-Gated Community Access

Free-tier users access public community spaces. Paid community tier members access private groups and premium content channels. Premium subscribers access direct messaging and exclusive content. Access levels driven by CR1 entitlement engine.

05 — DELIVERY TIMELINE

Total Effort: 45 Working Days · 6 Calendar Weeks

WEEKS 1–3 PARALLEL

Phase 1 — CR1 + CR2 Concurrent

CR1 and CR2 executed simultaneously across dedicated streams. Backend API, database schema, and frontend components developed in parallel. Shared sprint planning and daily standups to align integration points.

END OF WEEK 3

CR1 & CR2 UAT & Sign-Off

User Acceptance Testing for both CRs. Feedback addressed within agreed revision cycle. Written sign-off obtained before Phase 2 begins.

WEEKS 4–6 SEQUENTIAL

Phase 2 — CR3 Community Platform

CR3 begins after CR1/CR2 sign-off. Sequential execution required: community subscription gating depends on the entitlement engine delivered in CR1. Frontend and UX resources transition from Phase 1.

END OF WEEK 6

Full Delivery, UAT & Go-Live

All three CRs active in production. Final handover documentation and knowledge transfer completed.

Note: Timeline assumes UAT feedback within 2 business days per phase and timely environment access. CR3 path (Communi vs. custom build) confirmed in Week 4, Day 1–2 via feasibility assessment — fixed price applies to either path.

EFFORT

CR1	21 days
CR2	21 days
CR3	21 days
Total	45 days

CR1 + CR2 run in
parallel (3 weeks).
CR3 sequential after.
Total calendar: 6 weeks.

06 — COMMERCIAL PROPOSAL

Pricing — Change Request Bundle

#	Change Request	Scope Summary	Duration	Amount
CR1	User Journey & Subscription Management	Direct B2C onboarding, tiered subscriptions, feature enable/disable, admin overrides, clinic request workflow	3 weeks	AED 6,000
CR2	Ivory Services API Integration	MagicLink API, B2C + B2B2C attribution tagging, super admin analytics dashboard, Ivory partner portal	3 weeks	AED 6,000
CR3	Community Platform Integration	Communi integration or custom standalone community module (reusable), SSO sync, subscription-gated tiers	3 weeks	AED 6,000
TOTAL — ALL THREE CHANGE REQUESTS (6 CALENDAR WEEKS)			45 days	AED 18,000

50%

AED 9,000

On signing & commencement
of Phase 1 (CR1 + CR2)

50%

AED 9,000

On delivery & sign-off
of all three CRs

07 — TERMS & CONDITIONS

Governing Terms for This Proposal

This proposal covers three discrete change requests (CR1, CR2, CR3) outside the original agreed scope of work. Each CR may be approved independently or as a bundle.
Work commences on receipt of 50% advance payment (AED 9,000) and written approval of this proposal referencing SAL-QTN-2026-00008, via email to admin@bettroi.com.
CR1 and CR2 will be executed concurrently during Weeks 1–3. CR3 commences in Week 4 following successful UAT sign-off of CR1 and CR2. Sequential dependency exists between CR1 and CR3 due to the entitlement engine integration.
Timeline is contingent on timely access to LBL staging and production environments and on UAT feedback being provided within 2 business days of each delivery milestone.
CR3 scope — Communi integration vs. custom community build — will be confirmed within the first 2 days of Phase 2 following a feasibility assessment. The fixed price of AED 6,000 applies to either path.
Each CR includes one round of revisions based on UAT feedback. Additional scope beyond CR1–CR3 will be quoted separately under a new change request.
The community module developed under CR3 (if custom-built) is architected as a reusable standalone microservice. Bettroi reserves the right to use the base framework for other client engagements; all LBL-specific configurations remain exclusive to LBL.
All pricing excludes third-party API costs, platform licences, or cloud infrastructure charges (e.g., Communi subscription fees, hosting). These are borne directly by LBL.
VAT (5%) will be applied on Tax Invoices as per UAE Federal Tax Law.
Full intellectual property of all deliverables transfers to Brainforia Edwelltech FZC upon receipt of final payment.
This proposal is governed by the laws of the UAE. Disputes shall be resolved through the Dubai International Arbitration Centre (DIAC).

To Accept: Reply to admin@bettroi.com with written approval referencing SAL-QTN-2026-00008 and confirm the advance payment of AED 9,000 to initiate Phase 1. We look forward to continuing to build the LBL platform together.