إنتقل إلى المحتوى الرئيسي

Product Vision

Document Status: Active Last Updated: April 2026

1. Vision Statement​

We are building a Saudi-native business operating system powered by ERPNext, designed to help companies run their core operations with modern UX, built-in compliance, and intelligent automation.

This is not a dashboard product, not a spreadsheet replacement, and not simply an ERP customization. It is a business execution environment that combines the depth of ERP with the clarity of a premium interface, the trust of local compliance, and the leverage of AI.

2. The Product Category We Are Creating​

Our product creates a new category for the Saudi market:

A modern, compliance-first, AI-assisted business operating system for Saudi companies.

The system should feel like the place where work actually happens. Users should be able to create, review, approve, reconcile, comply, search, and automate inside one coherent environment instead of switching across disconnected tools.

This category matters because most businesses in the market currently choose between:

  • expensive legacy ERP systems
  • lightweight accounting tools with limited localization
  • fragmented spreadsheets and manual workflows
  • custom software with weak compliance coverage
  • modern tools that look good but do not understand Saudi business reality

Our product is meant to sit in the gap between these options.

3. Long-Term Product Identity​

The product should evolve into the operating layer for Saudi businesses.

What that means​

  • ERPNext remains the transactional engine underneath.
  • Our platform becomes the experience and control layer on top.
  • Saudi compliance becomes part of the workflow design, not an afterthought.
  • AI becomes a practical business assistant, not a novelty feature.
  • The interface becomes premium, modern, and calm enough for daily operational use.

What the product should feel like​

Users should feel that the product is:

  • fast to understand
  • pleasant to use
  • safe to trust
  • easy to adopt
  • powerful enough for real operations
  • flexible enough to grow with the business

4. Vision for the User Experience​

The product experience must be materially better than the legacy ERP experience that many users tolerate today.

Experience goals​

  • clean, liquid, glass-inspired interface language
  • role-based dashboards and workflows
  • clear hierarchy and reduced cognitive load
  • Arabic-first and RTL-ready behavior
  • minimal friction between intent and action
  • highly visible status tracking for critical business actions

The user should never feel like they are fighting the system just to complete work.

5. Vision for Compliance and Trust​

Saudi compliance is not a feature module. It is a product principle.

The product must be designed so that compliance is:

  • visible
  • testable
  • auditable
  • embedded in the workflow
  • difficult to bypass accidentally

That means the product should naturally support requirements such as:

  • ZATCA-ready invoicing flows
  • audit trails and immutable records where required
  • VAT/tax logic aligned to local expectations
  • data handling aligned with Saudi privacy and hosting requirements
  • strong traceability across financial and operational actions

Trust is a product feature. In the Saudi market, trust is not just about brand. It is about whether the system can safely run the business.

6. Vision for Intelligence and Automation​

AI should not sit on top of the product as a chatbot layer. It should be woven into the workflows where it can save time, reduce error, and improve execution.

Over time, AI should help with:​

  • document understanding
  • invoice drafting and validation support
  • reconciliation assistance
  • natural language querying of business data
  • workflow routing suggestions
  • summaries and operational insight generation
  • repetitive administrative tasks

The product vision is not to automate everything. It is to automate the parts of the business that are repetitive, error-prone, and high-value when accelerated.

7. Vision for the Product Architecture​

The architecture should support a clean separation of responsibilities.

Strategic architecture intent​

  • ERPNext as the backend system of record
  • custom Frappe apps only when needed for localization or extension
  • middleware for orchestration, abstraction, and business logic control
  • React / Next.js for the modern experience layer
  • dedicated infrastructure for scale, security, and data residency
  • compliance logic protected as a first-class system concern

This architecture matters because the product must be maintainable, upgradeable, and scalable over time. The product vision is not only about how it looks and behaves, but also about how it remains sustainable as complexity grows.

8. Vision for the Market Position​

Our product should be recognized as the strongest fit for Saudi businesses that need all of the following at once:

  • modern user experience
  • deep operational functionality
  • Saudi compliance support
  • strong trust and data residency posture
  • automation and AI capabilities
  • practical implementation speed

The long-term aim is to be seen not as a niche ERP tool, but as the business operating system category leader for Saudi-first organizations.

9. Product Evolution Path​

The product should evolve in stages:

Stage 1: Focused workflow excellence​

Start with one high-value, compliance-sensitive workflow and do it extremely well.

Stage 2: Operational expansion​

Add adjacent workflows that naturally connect to the first workflow and increase platform usefulness.

Stage 3: Cross-functional platform maturity​

Bring finance, operations, approvals, documents, automation, and intelligence together into a unified business environment.

Stage 4: Ecosystem depth​

Grow into a platform with modules, integrations, and configurable capabilities that support different business types and scales.

The product vision is therefore not a static endpoint. It is a trajectory.

10. Design Principles That Follow From the Vision​

Because of this vision, the product must consistently obey the following principles:

  • compliance is built in, not bolted on
  • workflow completion matters more than dashboard display
  • UX must reduce friction rather than add decoration
  • AI must create real operational leverage
  • the architecture must stay modular and upgrade-safe
  • the product must feel local to Saudi business realities
  • the system should support growth from SME to mid-market and beyond

11. What Success Looks Like​

The vision is successful when Saudi businesses begin to use the product as their primary operating environment for daily work.

That means:

  • users trust it for core business execution
  • finance and operations teams rely on it every day
  • compliance requirements are handled naturally
  • manual work drops materially
  • AI and automation remove repetitive effort
  • the business sees the platform as essential, not optional