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

🧭 North Star Document: The Compass

Document Status: Active Last Updated: April 2026

One-Sentence North Star: Build the most trusted Saudi-native business operating system, powered by ERPNext, that helps organizations complete core workflows faster, smarter, and with compliance built in.

1. Vision & Mission: The Saudi-Native Business OS​

We are not building a dashboard. We are building a Saudi business operating system.

Most global ERPs treat Saudi Arabia as a localization afterthought — an Arabic translation layer, a tax plugin, or a compliance patch on top of legacy software. Our vision is to build the missing middle of the Saudi market: a localized, compliant, premium operating environment that feels built for Saudi businesses from day one.

Our system is the invisible engine of the business. It does not merely display the state of the business; it actively drives the work. By bridging an open-source core (ERPNext) with a modern liquid-glass UX, native AI, and hard-wired Saudi compliance, we enable businesses to create, approve, reconcile, comply, and automate without leaving the ecosystem.

Our mission is to give Saudi businesses a unified platform that combines ERP depth, beautiful UX, intelligent automation, and local compliance in one coherent system. The product should make daily business work feel simpler, faster, safer, and more trustworthy to execute.

2. The North Star Metric (NSM)​

Primary Metric: Frictionless Workflow Completion Rate (FWCR)​

The percentage of core business workflows completed entirely inside the platform without manual rework, external tools, or compliance rejection.

A dashboard can show data. An operating system should help people finish work.

A workflow is only valuable when it is:

  • initiated inside the platform
  • completed inside the platform
  • compliant by design
  • traceable through audit logs
  • repeatable without spreadsheets or disconnected tools

Why this metric matters​

FWCR measures actual business value, not just logins or page views. It reflects whether the product has become the place where work gets done.

Secondary / Leading Metrics​

  • AI Task Resolution: number of successful AI-assisted completions per week
  • Time-to-ZATCA Clearance: average latency from invoice generation to accepted clearance
  • Time to Complete Core Workflows
  • Percentage of compliant invoices generated on first attempt
  • Reduction in manual data entry
  • User task completion rate
  • Weekly active business users by role
  • Compliance exception rate
  • Support tickets per active customer
  • Time to onboard a new customer

3. Product Identity & Anti-Patterns​

What we are​

  • A Saudi-native business operating system
  • An ERP-backed execution platform
  • A compliance-first workflow environment
  • An AI-assisted business productivity layer
  • A premium UX product for operational teams

What we are not​

  • Just an ERPNext skin
  • Just a dashboard tool
  • Just a spreadsheet replacement
  • Just a reporting system
  • Just a UI redesign project
  • Just an AI chatbot over business data

Anti-patterns to avoid​

  • building a pretty interface that does not drive execution
  • adding AI where a deterministic workflow is better
  • hiding compliance behind manual workarounds
  • overfitting the first version to a single niche
  • turning the product into a generic dashboard layer
  • creating deep technical coupling that makes future changes painful

4. Target Customer Profile (ICP)​

Ground Zero (Alpha — “The Shadow”)​

A real-world pilot customer acting as the crucible for the product. Success here is measured by real operations matching the source of truth with minimal manual correction.

Phase 1 (The Missing Middle)​

Saudi SMEs, typically 10–100 employees, who have outgrown spreadsheets and lightweight accounting tools but find SAP or Oracle NetSuite too expensive or heavy.

Phase 2 (Mid-Market)​

Saudi businesses in trading, contracting, professional services, and project-based operations that want digital transformation without sacrificing usability, localization, or compliance.

Initial Vertical Focus​

The product should support multiple verticals, but the first implementation should prioritize workflows common across:

  • trading and distribution
  • professional services
  • construction and project-based businesses
  • small and mid-sized finance-heavy operations

5. Core Product Principles (The 5 Layers)​

Every feature must map to one or more of these foundational layers:

1. Experience Layer (Liquid/Glass UI)​

A premium, consumer-grade B2B experience. Data density must be balanced with visual hierarchy to prevent cognitive fatigue. We build for RTL (Right-to-Left) first.

2. Execution Layer (Workflows)​

The system must facilitate approvals, task hand-offs, document intelligence, and role-based actions natively. No jumping to email to get an invoice approved.

3. Intelligence Layer (AI-Native)​

AI is a core worker, not a novelty chatbot. It handles OCR/document processing, automated ledger reconciliation, summaries, classifications, and RAG-powered query answering.

4. Compliance Layer (The Guardian)​

ZATCA Phase 2, GOSI, PDPL, VAT, and auditability are built in by design, not retrofitted. Compliance validation begins at the data-entry level.

5. Infrastructure Layer (The Forge)​

High availability, reproducible environments, zero-downtime deployments where feasible, and separated infrastructure architecture ensure data sovereignty and enterprise-grade reliability.

6. Strategic Guardrails (Non-Negotiables)​

1. The ERPNext Boundary Rule​

The core ERPNext codebase should remain untouched wherever possible. All customizations, localized business logic, and UI abstractions should live in custom Frappe apps or the middleware layer. This preserves a clean upgrade path.

2. Absolute Data Sovereignty​

To align with Saudi trust expectations and local data-handling requirements, primary databases, AI services, and document blob storage should be hosted in Oracle Cloud Infrastructure (OCI) Riyadh/Jeddah. Saudi financial and sensitive business data should remain inside the Kingdom.

3. No Compliance, No Ship​

If a feature processes financial data or personal data but lacks the Guardian layer’s audit trail, validation, or regulatory formatting, it does not ship.

4. API-First Middleware​

The frontend must never speak directly to the ERPNext database. All communication flows through the API gateway / middleware layer to ensure security, payload control, orchestration, and cacheability.

5. Separation of Concerns Is Mandatory​

Blueprint, infra, backend, frontend, AI, and compliance each have clear boundaries and review gates.

6. Simplicity Is a Strategic Advantage​

The product should make complex business work feel manageable, calm, and obvious.

7. Defining Success & Differentiation​

How we win​

  • Modern liquid / glassmorphic UI
  • Saudi compliance baked into workflows
  • AI-assisted execution and search
  • ERP-grade depth with better usability
  • Strong data residency and cloud trust
  • Faster implementation than legacy ERP systems
  • Lower total cost of ownership than expensive incumbents
  • Better fit for Saudi business operations than generic global systems

What success looks like for users​

  • run core business operations with fewer tools
  • reduce manual effort in accounting and administration
  • produce compliant documents and invoices correctly
  • access business information quickly and clearly
  • delegate repetitive work to automation
  • understand what is happening in the business at a glance
  • trust that the system is aligned with Saudi requirements

North Star success definition​

We know the product is succeeding when a Saudi business uses it as its primary operating environment for day-to-day workflows, with minimal manual workaround, strong compliance confidence, and measurable productivity improvement.

In practical terms:

  • users complete more work inside the platform
  • fewer critical business actions happen in spreadsheets
  • compliance-related errors decrease
  • finance and operations teams save time
  • customers trust the product enough to expand usage across departments
  • the product becomes central to how the business runs

8. Guiding Questions for Major Decisions​

Before accepting any major decision, ask:

  1. Does this move us closer to becoming a business operating system?
  2. Does this improve workflow completion?
  3. Does this strengthen Saudi compliance or trust?
  4. Does this simplify or clarify the user experience?
  5. Does this reduce manual effort or operational friction?
  6. Does this fit the architecture and maintainability goals?
  7. Does this support long-term scale rather than short-term convenience?

9. Metric Ownership​

Primary Owner​

Product leadership

Supporting Owners​

  • Engineering for instrumentation and workflow completion
  • Design for user journey clarity and reduced friction
  • Compliance for local rule mapping
  • Customer success for workflow adoption and feedback
  • Data / analytics for measurement integrity

10. Review Cadence​

This document should be reviewed when:

  • the product vision changes
  • the initial market focus changes
  • the compliance landscape changes materially
  • the core workflow strategy changes
  • the company expands into a new major segment or region

It should remain stable, but not frozen.