System paths / capability
Choose a technical path after the readiness gates
- Delivery
- Custom and remote
- Working language
- English
- Local provider access
- Client-authorized only
Portals and workflow systems
Build staff, partner, or customer workspaces with role-aware queues, approvals, dashboards, records, notifications, and exception handling. Applicable Arabic/RTL interaction, SAR formats, +966 numbers, address or identity fields, and local-user scenarios become test fixtures only after the client defines them.
- Role and permission model
- Draft and approval states
- Accessible errors and recovery
- Audit and ownership evidence
Integrations and modernization
Connect or repair client-authorized systems for payments, invoicing, identity, CRM, content, analytics, messaging, or operations. A provider name is not an access promise. Record eligibility, account owner, API version, data path, credentials, support, failure behavior, and a safe replacement or manual route.
- API and account authority
- Data and secret boundaries
- Idempotent retries
- Migration and rollback
AI assistance with a human gate
AI can support search, summarization, drafting, classification, knowledge retrieval, or workflow assistance when source, language, data, review, and fallback are explicit. It does not approve Arabic, legal or regulatory conclusions, identity, payments, e-invoices, data transfers, hiring, credit, or another material decision.
- Source-linked output
- Sensitive-data review
- Human confirmation
- Disable and fallback path
Match one system path to one accountable outcome
Describe the current workflow or product, who owns it, which providers it needs, and what evidence would demonstrate a useful technical improvement.
Prepare the project brief