Services · Ecommerce development · CRM subscription sites

Subscription sites that let Riyadh CRM vendors sell seats online and invoice properly.

Codeeo handles CRM subscription website development in Riyadh for software companies that sell customer relationship tools by the seat, the plan or the module. We build the Arabic first pricing pages, the sign up and payment flow, the recurring billing engine and the account area where a buyer adds users or changes plan. Every charge produces a ZATCA compliant tax invoice, and enterprise buyers in the capital get the purchase order route their finance teams expect.

Our Riyadh team can run discovery in person at your office, so product, finance and sales sit in the same room while we map plans, prices, approvals and the invoice rules that the billing system has to follow from day one. If you only need the marketing site, we scope CRM SaaS website development in Riyadh on its own.

Built for
CRM and sales software vendors in Riyadh selling to SMEs, regional headquarters and semi-government buyers.
Typical timeline
Agreed in discovery once plans, payment routes and invoicing rules are fixed, then written into the statement of work.
What you own
The site code, the billing configuration, gateway and tax accounts, customer records and invoice archive, all in your name.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What the platform includes

The parts a Riyadh CRM vendor needs to take recurring revenue.

Selling a CRM in Riyadh usually means two kinds of customer at once. A small trading company wants to pick a plan, pay with mada or Apple Pay and start inviting colleagues within minutes. A regional headquarters in KAFD or a ministry supplier wants a quotation, a purchase order, a vendor registration pack and an annual invoice paid by bank transfer. The platform we build handles both from the same product catalogue, so the plan your sales team quotes is the same plan the self-serve buyer sees. Prices, seats, modules and add-ons live in one billing model. The website reads from it, the checkout charges against it, and your CRM product reads the result to decide which features each workspace can use. Arabic is the default reading direction, with English alongside for the many multinational teams based in the city.

Explain your project
  • Arabic first pricing pages

    Plan comparison tables built right to left, with feature names your Riyadh buyers recognise, seat counts, monthly and annual toggles and VAT shown the way Saudi consumers and businesses expect. English mirrors the same content rather than leading it.

    Buyers compare plans in their own language without calling sales.

  • Self-serve checkout with local methods

    Card checkout through a SAMA licensed gateway, with mada, Visa, Mastercard, Apple Pay and STC Pay where your acquirer supports them. Saved payment tokens stay with the gateway, never in your database.

    An SME can subscribe and pay in one sitting.

  • Quote to subscription for enterprise

    Sales builds a quotation from the same catalogue, the buyer accepts it online, and the platform opens the subscription with agreed seats, term and payment schedule. Purchase order numbers and cost centres are captured for the buyer's finance department.

    Large deals close without a separate manual billing process.

  • Bank transfer and SADAD invoicing

    Annual and multi-year contracts are invoiced with bank transfer details or a SADAD bill reference where your bank provides one, and payment status flows back automatically so the account is not suspended while finance processes the payment.

    Enterprise invoices are paid through the channels buyers already use.

  • Fatoora integration for every charge

    Simplified and standard tax invoices, credit notes for downgrades and refunds, and buyer VAT numbers for business customers, generated and reported in line with ZATCA e-invoicing rules for your integration wave.

    Each renewal and change produces a compliant invoice without manual work.

  • Seats, modules and usage add-ons

    Charge by user, add modules such as marketing automation or call recording, and bill usage like WhatsApp conversation credits or SMS bundles. Mid-term changes are prorated and co-termed to the main renewal date.

    Revenue grows with each account rather than staying flat.

  • Account and billing portal

    Account owners add seats, change plans, update cards, download invoices and assign a separate billing contact. Roles keep a sales manager from cancelling the company subscription by mistake.

    Fewer billing tickets reach your support team.

  • Dunning and grace periods

    Failed renewals trigger retries and Arabic and English reminders by email, SMS or WhatsApp, with a grace period before features are restricted. Rules differ for card customers and invoiced enterprise accounts.

    Fewer accounts lost to an expired card.

  • Procurement and trust pages

    Pages and downloads that answer what Riyadh procurement teams ask: where data is hosted, how the product meets NCA controls, the PDPL privacy notice, commercial registration and VAT certificates, and a security questionnaire contact.

    Vendor onboarding moves faster at large buyers.

  • Revenue and renewal reporting

    Monthly recurring revenue, renewals due this quarter, churned and expanded accounts, and outstanding enterprise invoices in one finance view. Figures reconcile to Fatoora invoice totals and gateway settlements, so the numbers your board sees in Riyadh match the numbers your accountant files.

    Finance closes each month from one trusted source.

Who this is for

Four Riyadh vendors we see most often.

The capital has a dense mix of local software houses, regional offices of international vendors and startups coming out of accelerator programmes. Each arrives with a different billing problem. Some have a product and no way to sell it online. Others sell online but cannot invoice the way Saudi buyers need. The four situations below shape what we build first and what we leave for a later release.

Most clients fit more than one description. The common thread is that billing must follow Saudi tax, payment and data rules without slowing down the people who sell the product.

01

A local CRM moving from contracts to online plans

You sell today through account managers, spreadsheets and bank transfers. We turn your contract terms into a plan catalogue, put self-serve plans on the website for smaller buyers and keep the quotation route for large accounts, so sales stops typing invoices by hand and finance sees every renewal coming. Account managers keep their relationships; they simply stop chasing payments that the platform can collect.

Start with the plans you already sell, not new ones.

02

An international CRM opening a Saudi entity

Your global billing system charges in another currency and issues invoices that Saudi buyers cannot reclaim VAT on. We build a Saudi storefront and billing layer under your local entity, with riyal pricing, Fatoora invoices and local payment methods, while syncing subscriptions back to your global product.

Often linked to a regional headquarters set up in Riyadh.

03

A startup with a vertical CRM

A CRM for clinics, real estate brokers or contracting firms needs to show value quickly and convert trial users without a sales call. We focus on the pricing page, sign up, onboarding emails and a clean upgrade path, and keep the first release small enough to learn from. Startups from Riyadh accelerator programmes often need investors to see clean recurring revenue figures, which the reporting view provides.

Trials are optional and set by you, never assumed.

04

A vendor selling to government buyers

Government and semi-government entities in Riyadh buy through formal procurement, often via Etimad, and pay annually against invoices. The site still matters: it carries the product information, compliance pages and price list that evaluators check, and the billing platform tracks contract terms and renewals. We make sure contract start and end dates, payment terms and renewal notices are tracked so nothing lapses quietly.

Online checkout is rarely the route here; invoicing is.

How a Riyadh build runs

  1. 01On-site discoveryWorkshops at your Riyadh office with product, finance and sales to agree plans, seats, add-ons, payment routes, invoice wording and who approves discounts and refunds.
  2. 02Billing modelWe write the catalogue, proration rules, renewal logic and dunning steps as a document your finance lead signs before any screen is designed.
  3. 03Arabic first designPricing, checkout and portal screens designed right to left first, then mirrored for English, and tested with real plan names and long Arabic labels.
  4. 04Gateway and Fatoora setupYour gateway account, webhooks and ZATCA onboarding are configured in sandbox first, so every charge, refund and credit note is tested against real invoice output.
  5. 05Product entitlement syncYour CRM product reads plan, seats and modules from the billing platform, so access changes the moment a customer upgrades or a payment fails.
  6. 06Launch and migrationExisting customers are imported with their renewal dates, notified in both languages, and moved over in batches while finance reconciles the first billing cycle.

Technology

What we build this with.

We pick the billing engine by your model: a subscription platform such as Stripe Billing or Chargebee where it suits your gateway, or a custom Laravel or Node billing service when local gateways and Fatoora rules need tighter control. Sites are built in Next.js or WordPress. Hosting follows your data residency decision.

01Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

02Commerce

  • Shopify Plus
  • WooCommerce
  • BigCommerce
  • Headless storefronts

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

04Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions Riyadh CRM vendors ask

It depends on the billing model, not the number of pages.

A site with self-serve plans on one gateway is quicker than one that also handles enterprise quotations, purchase orders, usage billing and migrated customers. We agree the scope in discovery, write the timeline into the statement of work, and stage the release so self-serve plans can go live before the enterprise route if that suits your sales calendar. The biggest variable is usually how long gateway approval and ZATCA onboarding take on your side. Content matters too: Arabic plan descriptions, legal terms and the privacy notice need sign off from your team, and we plan review rounds for them early so they do not hold up launch.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews