SMS GROUP — PROJECT DELIVERY PLAN

Reference: SMS-TYN-2025-001
Version: 1.0
Date: 22 May 2026
PM: Product Manager Agent
Parent Issue: SMS-4

---

PROJECT SUMMARY

SMS Group will build the TYNDILL Business Management System — a purpose-built fintech platform for TYNDILL Agent & Money Transfer (Kigali, Rwanda) automating the full money transfer workflow from WhatsApp client intake to Irembo payment dispatch. The system covers 11 core features including AI receipt analysis, fraud detection, multi-branch architecture, and offline mode with auto-sync. Delivery target: 17 August 2026 (3 months). Fixed price: $6,500.

---

VALIDATION NOTES

All PM validation checklist items assessed. Key flags:

• Irembo API: Merchant approval is PENDING — 2–3 weeks from Day 1 submission. Sprint 4 has a contingency plan.
• WhatsApp Web.js: Unofficial API — session instability risk acknowledged. Auto-reconnect and manual fallback built in.
• Client sign-off SLA: Not specified in brief — assumed 48 hours per milestone. Must be confirmed with Hazem at contract signing.
• $3,900 deposit: Not yet received. Development does NOT start until payment is confirmed.

---

ASSUMPTIONS & DEPENDENCIES

1. Irembo API merchant application submitted Day 1 — estimated 2–3 weeks for approval. Sprint 4 Irembo tasks contingent on approval by Week 6.
2. Client (Hazem) provides WhatsApp business SIM by Day 5 (29 May). Sprint 2 is blocked without it.
3. Client provides all bank account details by Day 5 (29 May).
4. Google Vision API account activated and billing enabled by end of Sprint 1 (7 Jun).
5. Anthropic API key (Claude Haiku 4.5) secured before Sprint 2 begins (8 Jun).
6. Contabo VPS provisioned and accessible from Day 1.
7. Supabase project created with appropriate regional data residency before Sprint 1 ends.
8. Client sign-off turnaround: 48 hours max per milestone — to be confirmed at signing.
9. NCSA certification process begins Week 1; targeted completion by end of Sprint 5 (2 Aug).
10. WhatsApp Web.js used as integration layer — unofficial API, session instability is a known risk.
11. Synology NAS DS925+ hardware is client's responsibility — assumed available by 6 Jul.
12. The $3,900 (60%) upfront payment must be received before Sprint 1 begins.

---

USER STORIES

Feature 1: WhatsApp AI Agent

As a TYNDILL client
I want to initiate a money transfer via WhatsApp
So that I can complete full transaction intake without visiting a branch

Acceptance criteria: - [ ] Client scans QR code or messages the WhatsApp number to initiate - [ ] AI collects: amount, currency, destination, transaction type, recipient details - [ ] AI cross-checks if client is registered; prompts new clients to register - [ ] Conversation logged to DB with timestamps - [ ] Transaction draft created and approval workflow triggered on confirmation - [ ] Session persists across reconnections

Definition of Done: End-to-end WhatsApp conversation test — new client intake completes without human intervention, transaction created in DB, approval workflow triggered.
Assigned to: Backend Developer
Estimated hours: 40h
Dependencies: Supabase DB schema, Claude Haiku 4.5 API key, WhatsApp business SIM (client)
Priority: Core

---

Feature 2: Smart Bank Account Management

As a TYNDILL admin
I want to enter up to 10 bank accounts with daily limits and have the system auto-select the right account
So that accounts never exceed daily limits and large transactions are automatically split

Acceptance criteria: - [ ] Admin can add/edit/delete up to 10 bank accounts with: bank name, account number, daily limit - [ ] System tracks daily usage per account and resets at midnight - [ ] Auto-selection picks account with sufficient remaining limit - [ ] Transactions above single-account capacity split across two accounts automatically - [ ] Admin sees real-time account balance/limit status on dashboard - [ ] Accounts are branch-specific

Definition of Done: Test transaction of $5,000 against two accounts each with $3,000 remaining — system correctly splits and confirms.
Assigned to: Backend Developer
Estimated hours: 20h
Dependencies: Multi-branch architecture, dashboard UI wireframes
Priority: Core

---

Feature 3: AI Receipt Analysis

As a TYNDILL employee
I want to upload a proof-of-payment image and have AI extract the transaction details automatically
So that I don't manually read and enter receipt data

Acceptance criteria: - [ ] Employee uploads image via dashboard or receives via WhatsApp - [ ] Google Vision API extracts: sender name, receiver name, amount, transaction number, date - [ ] Extracted data auto-populated in the transaction form - [ ] Employee can review and correct before saving - [ ] Extraction confidence score displayed - [ ] Original image saved to DB alongside extracted data

Definition of Done: 10 test receipts processed — 9/10 produce correct amount and transaction number without manual correction.
Assigned to: Backend Developer
Estimated hours: 25h
Dependencies: Google Vision API key, transaction DB schema
Priority: Core

---

Feature 4: Fraud Detection

As a TYNDILL admin
I want the system to automatically flag suspicious or manipulated receipts
So that fraudulent transactions are caught before funds are released

Acceptance criteria: - [ ] System detects image manipulation (metadata inconsistency, editing artifacts) - [ ] Amount mismatch between WhatsApp message and receipt triggers alert - [ ] Suspicious patterns (duplicate transaction numbers, known flagged senders) trigger review - [ ] Flagged transactions held in "pending review" queue — not auto-approved - [ ] Admin notified of flagged transactions - [ ] Full audit log of fraud flags maintained

Definition of Done: Three test cases pass — (1) manipulated image flagged, (2) amount mismatch flagged, (3) legitimate receipt passes clean.
Assigned to: Backend Developer
Estimated hours: 30h
Dependencies: Feature 3 (AI Receipt Analysis), Security Auditor requirements checklist
Priority: Core

---

Feature 5: Multi-Level Approval Workflow

As a TYNDILL admin
I want to define a transaction threshold above which only I can approve
So that high-value transfers require senior authorization

Acceptance criteria: - [ ] Admin configures approval threshold - [ ] Below threshold: any employee can approve - [ ] Above threshold: admin-only; employee attempt is blocked with clear message - [ ] Approval/rejection logged with approver ID and timestamp - [ ] Rejected transactions returned to queue with reason - [ ] Workflow enforced in both online and offline mode

Definition of Done: Two transactions tested — one below threshold approved by employee, one above threshold blocked for employee and approved by admin.
Assigned to: Backend Developer
Estimated hours: 15h
Dependencies: Auth/roles system (multi-branch from day 1), transaction DB schema
Priority: Core

---

Feature 6: Irembo Payment Gateway

As a TYNDILL employee
I want the system to automatically trigger an Irembo payment when a transfer is approved
So that I don't manually execute the Irembo step

Acceptance criteria: - [ ] On transaction approval, Irembo API called automatically - [ ] Success: client receives WhatsApp confirmation with Irembo reference within 30 seconds - [ ] Failure: employee notified, transaction status updated to "Irembo failed" - [ ] Retry logic handles transient API failures (3 retries with backoff) - [ ] All Irembo API calls logged for audit

Definition of Done: Approved test transaction triggers Irembo API call in staging and returns confirmation; WhatsApp message delivered within 30 seconds.
Assigned to: Backend Developer
Estimated hours: 25h
Dependencies: Irembo merchant API approval (EXTERNAL — submit Day 1), Feature 5, WhatsApp messaging
Priority: Core

---

Feature 7: Cash Exchange Denomination Module

As a TYNDILL employee at a walk-in counter
I want to enter denomination quantities and instantly get the exact RWF exchange value
So that I can serve walk-in clients accurately and quickly

Acceptance criteria: - [ ] Admin defines exchange rates per banknote denomination (e.g., $100, $50, $20) - [ ] Employee enters quantities of each denomination - [ ] System calculates and displays total RWF value in real time - [ ] Transaction logged to history - [ ] Screen optimized for counter use (large inputs, fast interaction)

Definition of Done: Walk-in test — 3x $100 and 2x $50, system shows correct RWF total based on admin rates. Transaction logged.
Assigned to: UI/UX Designer (screen) + Backend Developer (logic)
Estimated hours: 20h total (UI: 8h, Backend: 12h)
Dependencies: Feature 8 (rate management), UI wireframes
Priority: Core

---

Feature 8: Multi-Currency Rate Dashboard

As a TYNDILL admin
I want to set manual daily exchange rates and see live market rates as reference
So that I can price services accurately each day

Acceptance criteria: - [ ] Admin sets manual rates for all supported currencies (USD primary) - [ ] Live market rates displayed as read-only reference - [ ] Rate changes take effect immediately across all active sessions - [ ] Rate history logged — admin views past rates by date - [ ] Dashboard accessible from both branches

Definition of Done: Admin sets USD/RWF rate — rate appears in Cash Exchange Module within 5 seconds. 30 days of rate history visible.
Assigned to: Backend Developer + UI/UX Designer
Estimated hours: 20h total (Backend: 12h, UI: 8h)
Dependencies: UI wireframes, multi-branch architecture
Priority: Core

---

Feature 9: Transaction History and Reporting

As a TYNDILL manager
I want a searchable, offline-accessible history of all transactions
So that I can audit, reconcile, and report on business activity at any time

Acceptance criteria: - [ ] All transactions searchable by: date range, client name, amount, status, branch, employee - [ ] Export to CSV and PDF - [ ] Accessible in offline mode (reads from local SQLite) - [ ] Branch-specific and combined views available - [ ] Transaction detail shows: receipt image, AI extraction, approval chain, Irembo reference

Definition of Done: 50 test transactions loaded — search by date range and client name returns results in under 2 seconds in online and offline mode.
Assigned to: Backend Developer + UI/UX Designer
Estimated hours: 25h total (Backend: 15h, UI: 10h)
Dependencies: Feature 10 (offline mode), transaction DB schema
Priority: Core

---

Feature 10: Offline Mode and Auto-Sync

As a TYNDILL employee
I want the system to continue working during outages and sync automatically on reconnect
So that operations are never interrupted by connectivity issues

Acceptance criteria: - [ ] System detects internet outage within 30 seconds - [ ] Core operations (new transactions, approvals, cash exchange) work in offline mode - [ ] Data written to local SQLite during outage - [ ] On reconnection, data auto-syncs to Supabase with conflict resolution (no duplicates) - [ ] Sync status visible to user at all times - [ ] Automated daily VPS backup runs on schedule

Definition of Done: Simulated outage — 3 transactions created offline, connection restored, all 3 appear in Supabase within 60 seconds with correct data and no duplicates.
Assigned to: Backend Developer
Estimated hours: 35h
Dependencies: Supabase schema, SQLite schema (must mirror Supabase exactly)
Priority: Core

---

Feature 11: Multi-Branch Architecture

As a TYNDILL admin
I want each branch to have isolated staff, accounts, and data while I have a combined admin view
So that I can manage Kigali and Kimironko independently and together

Acceptance criteria: - [ ] All DB tables include branch_id field from schema v1 - [ ] Staff accounts assigned to specific branches at creation - [ ] Bank accounts and transactions are branch-specific - [ ] Reports filterable by branch or combined - [ ] Admin sees all branches; employee sees only their own branch - [ ] New branches addable via admin UI without redeploy

Definition of Done: Two branches configured — Branch A employee cannot view Branch B transactions. Admin views both. Third branch added via admin UI in under 5 minutes.
Assigned to: Backend Developer
Estimated hours: 20h
Dependencies: Auth/roles system (must be built branch-aware from Day 1)
Priority: Core

---

SPRINT PLAN

Sprint 1 — Foundation and Infrastructure

Dates: 25 May – 7 Jun 2026 (Weeks 1–2)
Goal: VPS live, DB schema finalized, auth system working, rate management running, wireframes delivered.

Tasks: - [ ] Provision Contabo VPS, install Node.js/Nginx/PM2 — Backend Developer — 6h — None - [ ] Design full Supabase DB schema (all 11 features + multi-branch from day 1) — Backend Developer — 16h — None - [ ] Mirror SQLite schema for offline mode — Backend Developer — 8h — Supabase schema - [ ] Auth system: role-based (admin/employee), multi-branch, JWT — Backend Developer — 16h — DB schema - [ ] Multi-currency rate dashboard backend (CRUD + rate history) — Backend Developer — 12h — DB schema, auth - [ ] UI/UX Designer: wireframes for all 11 core feature screens — UI/UX Designer — 32h — Feature specs (this brief) - [ ] Security Auditor: NCSA compliance checklist + auth/data/payment security requirements — Security Auditor — 12h — None - [ ] Submit Irembo merchant application — Account Manager — 2h — None (Day 1 action) - [ ] Initiate NCSA certification process — Security Auditor — 4h — None - [ ] CLIENT: Provide all bank account details — Hazem — by 29 May - [ ] CLIENT: Confirm WhatsApp business SIM ready — Hazem — by 29 May

Acceptance criteria: - Auth login works for admin and employee roles with branch isolation - Rate management CRUD works and logs history - DB schema reviewed and signed off before Sprint 2 begins - Wireframes delivered by end of Week 2

Definition of Done: VPS running, Supabase + SQLite schemas migrated, auth passes login/role tests, rate dashboard functional, wireframes delivered.

---

Sprint 2 — WhatsApp AI and Receipt Intelligence

Dates: 8 Jun – 21 Jun 2026 (Weeks 3–4)
Goal: WhatsApp client intake and AI receipt analysis working end-to-end.

Tasks: - [ ] WhatsApp Web.js: QR session, session persistence, auto-reconnect — Backend Developer — 16h — WhatsApp SIM (from client) - [ ] Claude Haiku 4.5 conversational intake: amount, currency, destination, recipient — Backend Developer — 24h — WhatsApp integration, Anthropic API key - [ ] Client registration cross-check in AI flow — Backend Developer — 8h — DB schema, Claude integration - [ ] Google Vision API: receipt image upload + field extraction — Backend Developer — 16h — Google Vision API key - [ ] Auto-populate transaction form from extracted receipt data — Backend Developer — 8h — Vision API - [ ] Fraud detection: image manipulation + amount mismatch detection — Backend Developer — 20h — Vision API, Security Auditor checklist - [ ] Frontend: transaction intake form with receipt upload (from approved wireframes) — Backend Developer — 12h — Sprint 1 wireframes

Acceptance criteria: - WhatsApp conversation completes new client intake without error - Receipt extraction produces correct amount in 9/10 test cases - Manipulated receipt flagged as suspicious - Amount mismatch detected and queued for review

Definition of Done: End-to-end test: WhatsApp message -> AI collects all fields -> receipt analyzed -> transaction created in DB -> fraud check passes or flags correctly.

---

Sprint 3 — Approval Workflow, Cash Exchange, and Reporting

Dates: 22 Jun – 5 Jul 2026 (Weeks 5–6)
Goal: Complete transaction approval workflow and in-branch counter tools operational.

Tasks: - [ ] Multi-level approval workflow: threshold config, employee vs admin gates — Backend Developer — 15h — Auth system - [ ] Approval UI: pending queue, approve/reject with reason — Backend Developer — 10h — Wireframes - [ ] Cash Exchange Denomination Module: admin rates per denomination, walk-in screen — Backend Developer — 12h — Feature 8 - [ ] Transaction history: searchable table with filters — Backend Developer — 15h — DB schema - [ ] Export to CSV and PDF — Backend Developer — 8h — Transaction history - [ ] Transaction detail view: receipt image, AI extraction, approval chain, Irembo reference — Backend Developer — 10h — All prior features - [ ] Frontend screens: approval queue, cash exchange counter, history/reporting — Backend Developer — 16h — Wireframes - [ ] Security Auditor: review approval workflow for authorization bypass vulnerabilities — Security Auditor — 6h — Approval workflow spec

Acceptance criteria: - Transactions below threshold approved by employee; above threshold blocked for employees - Cash exchange calculates correctly for all tested denominations - Search returns results filtered by date range and client name in under 2 seconds - CSV export contains all required fields

Definition of Done: Manager approves high-value transaction; employee attempt rejected. Cash exchange tested with 5 denomination combinations. History search tested with 50 records.

---

Sprint 4 — Irembo Integration, Offline Mode, and Multi-Branch

Dates: 6 Jul – 19 Jul 2026 (Weeks 7–8)
Goal: Payment automation, offline resilience, and multi-branch architecture finalized.

Irembo contingency: If merchant API approval has not been received by 6 Jul, Irembo tasks move to Sprint 5 and are replaced with a mock integration. PM escalates to CEO immediately if delayed past 6 Jul.

Tasks: - [ ] Irembo API integration: trigger on approval, success/failure handling, WhatsApp confirmation — Backend Developer — 25h — Irembo API approval (EXTERNAL) - [ ] Irembo retry logic and error handling (3 retries with backoff) — Backend Developer — 8h — Irembo integration - [ ] Offline mode: outage detection, SQLite write, UI sync-status indicator — Backend Developer — 20h — SQLite schema - [ ] Auto-sync: Supabase sync on reconnect with conflict resolution — Backend Developer — 15h — Offline mode - [ ] Automated VPS daily backup script — Backend Developer — 6h — VPS setup - [ ] Multi-branch verification: all 11 features branch-isolated, combined admin views working — Backend Developer — 10h — All features - [ ] Frontend: offline indicator, sync status, branch selector — Backend Developer — 8h — Wireframes

Acceptance criteria: - Approved transaction triggers Irembo payment; WhatsApp confirmation in under 30 seconds - Offline mode activates within 30 seconds; 3 offline transactions sync correctly on reconnect - Daily backup runs and produces a valid, restorable file - Branch A employee cannot access Branch B data

Definition of Done: Full transaction lifecycle tested online and offline. Irembo confirmed in staging. Backup verified restorable. Branch isolation confirmed.

---

Sprint 5 — QA, Security Audit, and NCSA Submission

Dates: 20 Jul – 2 Aug 2026 (Weeks 9–10)
Goal: Full QA coverage complete, security audit passed, NCSA certification submitted, client UAT done.

Tasks: - [ ] QA Engineer: full feature regression suite (all 11 features) + edge case + load testing — QA Engineer — 40h — Feature-complete build - [ ] Security Auditor: full audit (auth, payments, data at rest/transit, fraud module, NCSA checklist) — Security Auditor — 20h — Feature-complete build - [ ] NCSA certification application submission — Security Auditor — 8h — Security audit complete - [ ] Priority bug fixes from QA and Security Auditor reports — Backend Developer — 24h — QA report - [ ] Client UAT with Hazem + 2 staff — PM — 8h — Feature-complete build - [ ] API performance optimization (target: under 500ms per endpoint) — Backend Developer — 8h — QA performance report

Acceptance criteria: - All critical and high QA bugs resolved and retested - Security Auditor provides written NCSA compliance sign-off - Client UAT feedback incorporated - All API endpoints respond in under 500ms under normal load

Definition of Done: QA Engineer closes all critical issues. Security Auditor provides written sign-off. NCSA application submitted. Client (Hazem) signs off on UAT.

---

Sprint 6 — Staff Training and Go-Live

Dates: 3 Aug – 17 Aug 2026 (Weeks 11–12)
Goal: System live in production, staff trained, client signed off, project delivered.

Tasks: - [ ] Production deployment to Contabo VPS — Backend Developer — 8h — QA passed, Security approved - [ ] Configure 3 staff accounts (1 admin + 2 employees) for both branches — Backend Developer — 4h — Auth system - [ ] Staff training: admin session (2h) + 2x employee sessions (1h each) — Account Manager — 5h — Production deployment - [ ] Staff user manual (PDF) — PM — 4h — All features - [ ] Synology NAS integration and initial data setup — Backend Developer — 6h — Client has NAS hardware - [ ] Final walkthrough and sign-off with Hazem — PM — 2h — Go-live - [ ] Post-launch monitoring: error alerts, uptime monitoring — Backend Developer — 6h — Production deployment - [ ] Handover document: credentials, VPS access, backup schedule, emergency contacts — PM — 3h — Go-live

Acceptance criteria: - System accessible from both branch locations - All 3 staff accounts tested on production with correct role permissions - Hazem provides written/WhatsApp acceptance confirmation - Monitoring alerts verified with a test trigger

Definition of Done: Client acceptance confirmed. All credentials and documentation delivered. Monitoring live. Final $1,300 payment triggered.

---

MILESTONE MAP

#	Milestone	Date	Deliverable	Payment Trigger
M1	Kickoff and Contract Signed	22 May 2026	Signed contract, deposit received, delivery plan approved	YES — $3,900 (60%)
M2	Foundation Complete	7 Jun 2026	VPS live, DB schema, auth system, rate dashboard	No
M3	Core AI Features	21 Jun 2026	WhatsApp AI + Receipt Analysis + Fraud Detection working	No
M4	Full Feature Build	19 Jul 2026	All 11 core features integrated and testable	YES — $1,300 (20%)
M5	QA and Security Complete	2 Aug 2026	QA passed, security audit signed off, NCSA submitted, UAT done	No
M6	Go-Live and Delivery	17 Aug 2026	System in production, staff trained, client acceptance confirmed	YES — $1,300 (20%)

---

RISK REGISTER

Risk	Likelihood	Impact	Mitigation
Irembo API approval delayed past Week 6	Medium	High	Submit Day 1; build mock in Sprint 3; shift integration to Sprint 5 if needed; PM escalates to CEO if delayed past 6 Jul
WhatsApp Web.js session instability in production	Medium	High	Auto-reconnection built Sprint 2 Day 1; PM2 session monitoring; fallback manual transaction entry UI always available
NCSA certification scope expands beyond estimate	Low-Medium	Medium	Security Auditor engaged Day 1 with scoped checklist; 2-week buffer in Sprint 5; cost overrun escalated to CEO immediately
Google Vision API accuracy below 90% on Rwandan receipts	Low-Medium	Medium	Test with real TYNDILL receipts Sprint 2 Week 1; tune prompts; manual correction UI always available
Client delays WhatsApp SIM or bank details past Day 5	Low	High	PM confirms by Day 3 (27 May); if not received by Day 7, Sprint 2 blocked — PM escalates to CEO and notifies client in writing
Supabase/SQLite sync conflict causing data corruption	Low	High	Timestamp-based conflict resolution from day 1; simulated conflict tests Sprint 4; daily backup provides recovery point
$3,900 deposit not received before Sprint 1 start	Low-Medium	Critical	Development does not start. PM escalates to CEO and Account Manager immediately

---

AGENT HANDOFF SCHEDULE

Agent	Receives	Trigger Date
UI/UX Designer	Sprint 1 design brief: all 11 screen specs, user stories, acceptance criteria per screen	22 May 2026 (Day 1)
Security Auditor	NCSA compliance scope + auth/payments/data security requirements checklist	22 May 2026 (Day 1)
Backend Developer	Approved wireframes from UI/UX Designer	End of Sprint 1 — 7 Jun 2026
Backend Developer	Security requirements checklist from Security Auditor	End of Sprint 1 Week 1 — 29 May 2026
QA Engineer	Feature-complete build + full test specification	20 Jul 2026 (Sprint 5 Day 1)
Security Auditor	Pre-production security audit brief	20 Jul 2026 (Sprint 5 Day 1)
Account Manager	Client onboarding checklist: training schedule, NAS setup, credentials handover	2 Aug 2026 (Sprint 5 complete)

---

CLIENT ACTION ITEMS

Item	Responsible	Deadline	Consequence if Missed
Sign contract and pay $3,900 deposit	Hazem	22 May 2026	Development does not start
Provide bank account details (all accounts)	Hazem	29 May 2026	Sprint 1 bank account feature delayed
Confirm WhatsApp business SIM available	Hazem	29 May 2026	Sprint 2 WhatsApp integration blocked
Purchase Synology NAS DS925+	Hazem	6 Jul 2026	Sprint 6 NAS setup skipped or delayed
Make self and staff available for UAT	Hazem + 2 staff	20 Jul 2026	Sprint 5 UAT skipped; go-live risk increases
Pay $1,300 Month 2 milestone payment	Hazem	19 Jul 2026	Sprint 6 work paused pending payment

---

OPEN ITEMS

Item	Owner	Deadline
Confirm $3,900 deposit received before Sprint 1 start	Account Manager	22 May 2026
Submit Irembo merchant application	Account Manager	23 May 2026
Confirm client sign-off SLA (48h per milestone) with Hazem	PM	22 May 2026
Google Vision API account and billing confirmed	Backend Developer	7 Jun 2026
Anthropic API key secured	Backend Developer	7 Jun 2026
NCSA certification scope confirmed with Security Auditor	Security Auditor	29 May 2026

---

ملخص خطة التسليم — ARABIC SUMMARY

المشروع: نظام إدارة أعمال TYNDILL
العميل: TYNDILL للحوالات المالية وتحويل العملات — حازم — كيغالي، رواندا
المرجع: SMS-TYN-2025-001
التاريخ: 22 مايو 2026
مدير المشروع: وكيل مدير المشروع — SMS Group

ملخص المشروع

ستقوم SMS Group ببناء نظام إدارة أعمال متكامل لشركة TYNDILL للحوالات المالية — منصة متخصصة تؤتمت دورة التحويل الكاملة من استقبال طلب العميل عبر واتساب حتى تنفيذ الدفع عبر Irembo. يغطي النظام 11 ميزة أساسية تشمل تحليل الإيصالات بالذكاء الاصطناعي، كشف الاحتيال، إدارة الفروع المتعددة، والعمل بدون إنترنت مع المزامنة التلقائية. مدة التسليم: 3 أشهر (17 أغسطس 2026). السعر الثابت: 6,500 دولار.

الخطة الزمنية

• الأسبوعان 1-2 (25 مايو – 7 يونيو): البنية التحتية — خادم VPS، قاعدة البيانات، نظام المصادقة، لوحة أسعار العملات
• الأسبوعان 3-4 (8 – 21 يونيو): وكيل واتساب بالذكاء الاصطناعي، تحليل الإيصالات، كشف الاحتيال
• الأسبوعان 5-6 (22 يونيو – 5 يوليو): سير عمل الموافقات، وحدة صرف العملات النقدية، التقارير
• الأسبوعان 7-8 (6 – 19 يوليو): بوابة Irembo، الوضع دون اتصال، المزامنة التلقائية، النسخ الاحتياطي
• الأسبوعان 9-10 (20 يوليو – 2 أغسطس): اختبار الجودة، التدقيق الأمني، شهادة NCSA، اختبار القبول مع العميل
• الأسبوعان 11-12 (3 – 17 أغسطس): تدريب الموظفين، الإطلاق الرسمي، تسليم المشروع

جدول المدفوعات

المرحلة	المبلغ	الحدث المحفز
عند التوقيع (60%)	3,900 دولار	توقيع العقد — لم يُستلم بعد
الشهر الثاني (20%)	1,300 دولار	اكتمال كافة الميزات (19 يوليو)
عند التسليم (20%)	1,300 دولار	الإطلاق الرسمي وقبول العميل (17 أغسطس)

إجراءات العميل المطلوبة

1. التوقيع على العقد ودفع مبلغ 3,900 دولار — بحلول 22 مايو 2026
2. تقديم تفاصيل جميع الحسابات البنكية — بحلول 29 مايو 2026
3. تأكيد توفر شريحة واتساب للأعمال — بحلول 29 مايو 2026
4. شراء جهاز Synology NAS DS925+ — بحلول 6 يوليو 2026
5. الحضور للاختبار مع الموظفين — بحلول 20 يوليو 2026

المخاطر الرئيسية

1. تأخر موافقة Irembo API — متوسط الاحتمال / تأثير عالٍ — تقديم الطلب يوم 1 + خطة بديلة جاهزة
2. عدم استقرار جلسة WhatsApp Web.js — متوسط — إعادة اتصال تلقائية + واجهة إدخال يدوي كبديل
3. توسع نطاق شهادة NCSA — منخفض إلى متوسط — إشراك مدقق الأمان من اليوم الأول

---

Prepared by: Product Manager Agent — SMS Group Solutions Ltd
Reviewed by: CEO Agent
Approved by: Hisham Alhady — Managing Director
Version 1.0 — 22 May 2026