Skip to main content

Business Model & Commercial Strategy

Document Status: Active Last Updated: April 2026

One-Sentence Summary: We generate recurring SaaS revenue by selling a premium, Saudi-native business operating system, supported by upfront implementation fees and intelligent add-ons that help businesses scale securely.

1. Purpose of This Document​

This document defines the commercial logic of our Saudi-native business operating system.

It answers four questions:

  • Who pays?
  • What are they paying for?
  • How do we price value in a way customers trust?
  • How do we build a scalable, profitable business over time?

We are not building a race-to-the-bottom open-source wrapper. We are selling a premium, compliant, enterprise-grade business engine, and the pricing model must reflect that reliability and trust.

2. Business Model Overview​

The business is a B2B software platform with a hybrid revenue model:

  • recurring SaaS subscriptions as the long-term core
  • one-time implementation and onboarding fees in the early stages
  • premium compliance and support packages for more demanding customers
  • AI and automation add-ons as the product matures
  • premium support SLAs (Enterprise)

This is not a pure self-serve SaaS product and not a pure services business. It is a product-led software company with high-value onboarding and deployment support.

Because the platform touches finance, compliance, and operational workflows, a high-touch implementation motion is realistic and desirable in the early market.

3. Core Revenue Model​

3.1 Subscription Revenue (ARR)​

Recurring SaaS fees provide access to the platform and its ongoing value.

The subscription should cover:

  • Next.js experience layer
  • middleware and workflow orchestration
  • ERPNext-backed backend capabilities
  • ongoing platform improvements
  • GOSI-related setup where relevant
  • ZATCA-related configuration and validation
  • infrastructure hosting and operations
  • baseline AI capabilities within fair-use limits

3.2 Implementation Revenue (One-Time)​

ERP software requires onboarding. We charge a one-time implementation fee to cover:

  • data migration
  • chart of accounts setup
  • workflow mapping
  • approval design
  • compliance configuration
  • user and role setup
  • training and handover

This also funds the Customer Success effort needed to drive a strong Frictionless Workflow Completion Rate from day one.

3.3 Compliance and Localization Services​

Some customers will require deeper Saudi-specific setup and support.

This may include:

  • tax logic and invoice rules
  • policy and audit mapping
  • regulated workflow customization

This can be monetized through premium packages, professional services, or higher-tier subscriptions.

3.4 AI and Automation Add-Ons​

Advanced AI should become a monetizable layer as the product matures.

Examples include:

  • OCR and document extraction
  • reconciliation assistance
  • natural language business querying
  • workflow drafting and recommendations
  • automation agents for repetitive tasks

3.5 Premium Support / Success Packages​

Larger customers may pay for:

  • SLA-backed support
  • priority response times
  • dedicated customer success support
  • training expansion
  • guided rollout assistance

4. Pricing Philosophy​

4.1 Radical Predictability​

A major customer pain point in ERP markets is pricing that becomes confusing as the business grows.

Our commercial promise is that pricing should be clear, predictable, and aligned with operational scale rather than hidden complexity.

4.2 No Per-Module Hostage Pricing​

We should avoid forcing customers to pay separately for every meaningful workflow component if they are already in a tier designed to support that operational level.

If a tier includes operations or accounting, it should include the workflows needed to run them properly.

4.3 No Surprise Compliance Fees​

Standard Saudi compliance support should be part of the platform value, not a constant surprise add-on.

Customers should feel they are buying a compliant platform, not a base product with unavoidable legal essentials hidden behind extra invoices.

4.4 Fair-Use AI​

Core AI capabilities should be included with transparent usage limits.

This protects the company from runaway compute costs while still making AI feel like a real part of the product value.

4.5 Price by Operational Scale, Not Noise​

The best pricing signal is not the number of buttons or modules. It is the size and complexity of the business using the platform.

5. Subscription Tiers​

Pricing numbers are intentionally omitted here and should be modeled separately.

Tier 1: The Core​

Target: Small businesses and the SME wedge

Included:

  • accounting core
  • sales and invoicing
  • ZATCA-ready invoicing capabilities
  • HR and payroll foundations where applicable
  • GOSI-aware setup where relevant
  • basic purchasing
  • core workflow support
  • baseline AI use

Value proposition: Replace fragile spreadsheets and lightweight tools with a compliant, AI-assisted financial engine.

Tier 2: The Operating System​

Target: Growing businesses that need broader operational control

Included:

  • everything in The Core
  • inventory management/operations management (industry specific)
  • approvals and advanced workflows
  • CRM and marketing integrations
  • stronger reporting and operational visibility
  • higher AI processing limits

Value proposition: Run more of the business in one unified platform instead of relying on fragmented point solutions.

Tier 3: Enterprise Cloud​

Target: Larger organizations with stricter security, data residency, and operational requirements

Included:

  • full platform access
  • dedicated OCI tenancy or single-tenant architecture where required
  • custom service-level commitments
  • enhanced support
  • custom rate limits and infrastructure controls
  • advanced compliance and security configuration

Value proposition: Enterprise-grade trust and isolation without the cost and complexity of legacy enterprise ERP suites.

6. Value Delivered to Customers​

Customers are not buying software screens. They are buying operational outcomes.

The product should help customers:

  • reduce manual accounting work
  • generate compliant invoices correctly
  • improve workflow completion speed
  • reduce reliance on spreadsheets and messaging apps
  • centralize operational work
  • gain confidence in compliance and auditability
  • improve visibility across departments
  • support better decision-making

This value is what justifies subscription and implementation fees.

7. Cost Structure and Unit Economics​

To remain a healthy software business, the company must protect gross margin while still delivering a premium service.

Main cost buckets​

  • product and engineering
  • design and product management
  • cloud infrastructure and hosting
  • AI processing and document intelligence usage
  • compliance and advisory work
  • support and customer success
  • sales and marketing
  • implementation and onboarding
  • security, logging, and observability tooling

Unit economics direction​

The long-term goal is for recurring software revenue to grow faster than customer support and implementation cost.

Early on, the model may be more services-heavy. Over time, the system must become more product-heavy and more standardized.

Cost discipline principles​

  • cache AI work where possible
  • standardize onboarding patterns
  • productize repeat custom requests
  • avoid unnecessary infrastructure sprawl
  • keep implementation repeatable

8. Land and Expand Strategy​

Our go-to-market motion should begin with a strong wedge and expand from there.

Land​

We enter through the most urgent and painful workflow: compliant accounting and invoicing.

This gives customers an immediate reason to trust the platform.

Expand​

Once the customer trusts the platform for finance and compliance, we expand into adjacent workflows such as:

  • procurement
  • inventory
  • HR and payroll
  • approvals and documents
  • automation and intelligence

Commercial result​

This should naturally increase retention and expansion revenue without aggressive upselling.

9. Path to Sustainability and Scale​

Phase A: Pilot / Alpha​

The objective is to prove the system in real business conditions.

Revenue may be limited or highly discounted. The priority is product truth, workflow validation, and customer learning.

Phase B: Early Direct Sales​

The first few customers should be founder-led and implementation-supported.

This phase validates:

  • pricing tolerance
  • onboarding repeatability
  • implementation economics
  • willingness to pay for compliance and usability

Phase C: Repeatable Scale​

Once the product is proven, scale should come through:

  • partner-led implementation
  • accounting and advisory firms
  • digital transformation agencies
  • referrals from satisfied customers
  • a stronger outbound and content motion

10. Strategic Risks​

10.1 Becoming too services-heavy​

If custom work dominates revenue, the company risks becoming a consulting firm instead of a scalable software business.

10.2 Underpricing compliance​

Saudi compliance is valuable and operationally important. It must be priced as part of the platform value, not treated as an invisible burden.

10.3 Overcomplicating pricing early​

Too many tiers, feature gates, or exceptions will slow sales and confuse customers.

10.4 Not productizing implementation knowledge​

Every implementation should feed back into product improvements, reusable configurations, and better documentation.

11. Strategic Principles​

  • recurring revenue is the long-term foundation
  • implementation revenue should accelerate adoption, not define the company forever
  • compliance is a value driver and a trust driver
  • AI should create leverage, not decoration
  • pricing must fit SMEs and mid-market customers
  • commercial packaging should remain simple enough to understand quickly
  • the company should continuously convert services knowledge into software

12. Key Assumptions​

This model assumes that:

  • Saudi businesses will pay for compliance confidence and better workflow execution
  • SMEs will adopt a product that reduces complexity and manual work
  • mid-market customers will pay for better support and configuration
  • AI and automation can become monetizable product layers
  • onboarding and implementation services are necessary in the early phase
  • the platform can gradually shift from implementation-heavy to software-heavy revenue

These assumptions should be validated through pilots, sales conversations, and customer expansion behavior.