How we run the engagement, what we commit to, and the few things we need from your side to keep the 16 weeks on track.
All milestones start as Not Started; statuses are updated as delivery progresses, with a formal progress update shared every week.
Product phases run sequentially and do not overlap, for a total of exactly 16 weeks — with the final week (Week 16) dedicated entirely to platform-wide testing and finalization. The final 2–3 days of every phase are reserved for defect fixes, your acceptance testing and formal sign-off. If a phase-end gate is at risk, we re-prioritize scope together — deferring agreed lower-priority items — rather than extending the 16-week timeline.
Each phase ends with a named customer acceptance window: at least 3 business days for your team to test before the phase-end milestone, with a same-day defect-triage commitment from our side, plus training and handover sessions for the staff affected by that phase's delivery.
The Brixfund Engine's new investment and wallet domain is built and completed within Phase 1 (Weeks 1–7); later phases simply connect to it as part of their own scope. Every existing Brixfund Engine capability — assistants, lead intake, notifications, payments and rewards — remains intact and is regression-verified through the merge and rebrand.
Third-party services (payment provider, identity verification and similar) depend on provider contracts and account provisioning. Wallet payments are demonstrated on a sandbox payment gateway in Week 5; the live provider connection is completed within Phase 1 provided the provider account is live by the end of Week 2 — we flag every required provider action at kickoff and at the start of each phase.
Regulatory licensing, KYC/AML policy and compliance sign-off for the investment and wallet product are your responsibility as the operator; the platform implements the verification and record-keeping controls your compliance advisors specify. We need those requirements by the end of the Phase 1 design window (Week 2).
All administration and moderation screens for the Brix Fund Portal live inside the unified internal portal — the direct evolution of today's Main System — with no separate admin application introduced.
The merge of the Main System and the Operations System preserves every existing capability of both, tracked and verified on a module-by-module migration checklist; nothing is retired or lost, and all current roles and permissions carry across. On merge day staff experience one seamless switch to the unified portal, protected by a rollback safety net throughout a defined stabilization window.
The internal investment team workspace is an existing internal capability preserved in the merge; it is separate and distinct from the new customer-facing Brix Fund investor portal.
The existing website and public content tools remain fully available inside the merged portal through Phases 1–2; in Phase 3 the new content management system supersedes them, with all existing content and subscriber data migrated across.
Phase 3 depends on your team supplying final website content, imagery and Arabic copy by the end of Week 11; anything not final by then launches with approved placeholder content your editors swap post-launch through the CMS.
App-store review by Apple and Google typically takes several days and occasionally requires resubmission; we submit in Week 15 and support the review cycle through to approval during the Week 16 finalization window.
Third-party integrations run as their own separate phases outside this 16-week development scope; each first needs a contract with the provider.
Exact calendar dates for each week are fixed at the kickoff meeting.