Customer journey
From first visit to working application
Each stage has one accountable system and a human approval where authority changes. Select a deployment model to see what differs.
- 01
Discover
Accountable: MONADJ.com
Anonymous browsing, package comparison, no account or tracking of form content.
- 02
Inquire
Accountable: Lead service
Validated, consented inquiry routed to an approved mailbox or CRM.
- 03
Qualify & demo
Accountable: Sales & solutions
Fit, deployment and service needs confirmed; demo on synthetic data.
- 04
Propose
Accountable: Quote & proposal
Versioned package, deployment and services; finance and legal sign-off.
✓ Human approval - 05
Contract
Accountable: Contract & order
Signed order defines entitlements, term, support and data-processing terms.
✓ Human approval - 06
Provision
Accountable: Provisioning authority
Audited, idempotent command creates the organization through the existing allowlist control.
✓ Human approval - 07
License
Accountable: Entitlement service
Versioned entitlement record; signed license file for customer-hosted sites.
- 08
Activate
Accountable: Identity
Named founding administrator activates through the approved identity provider.
✓ Human approval - 09
Onboard & operate
Accountable: MONADJ application
Guided activation, import and first project; users work within approved permissions.
- 10
Support & renew
Accountable: Support desk & entitlement
Contract-checked support, consented access, renewal and export obligations.
Deployment model
- Provision
- Tenant created in the shared, isolated MONADJ service.
- License
- Server-side entitlements; no license file.
- Access
- Tenant URL and approved identity provider; responsive web on any device.
- Upgrade & support
- Updates by staged MONADJ releases with rollback.
- Provision
- Dedicated instance in a MONADJ- or customer-owned cloud account by contract.
- License
- Enterprise entitlements; region and isolation evidence agreed.
- Access
- Dedicated endpoint and customer identity provider.
- Upgrade & support
- Maintenance windows and compatibility checks agreed per RACI.
- Provision
- Customer installs signed packages after a readiness assessment (candidate, not certified).
- License
- Signed offline license file with term, meter and grace rules — no phone-home dependency for daily work.
- Access
- Internal endpoint; VPN, device and network policy set by the customer.
- Upgrade & support
- Signed update bundles with migration pre-checks; support via consented access or redacted diagnostic bundle.
An inquiry is never an administrator account. Preserve allowlist-only organization creation until a replacement authority is explicitly approved.
Application access is not connected in this build. Cloud users need an approved tenant URL and identity provider; customer-hosted users need their internal endpoint and required VPN or device controls. No credentials are collected here.
The public website must never be a runtime dependency for ordinary on-premises work.
Mobile access architecture
Three layers with separate decisions. The public website never holds project data.
Responsive application (EN/AR/FR, 390 px verified)
PWA or native app (offline, push, device management)
Ready to see execution with greater clarity?
Start with your team, your governance and your operating model.