Services · Ecommerce development · AI meeting assistant subscription sites

Subscription sites that sell meeting assistants to Riyadh's boards and ministries.

Codeeo delivers AI meeting assistant subscription website development Riyadh product companies use to sell to the capital's two very different buyers: fast moving private firms that pay by card on a monthly plan, and government bodies and regional headquarters that buy annual licences through formal procurement. We build the Arabic first storefront, the checkout and quote paths, the recurring billing and the account area, with invoices that meet ZATCA rules, so both kinds of customer can buy your product the way their organisation actually purchases software.

Our Riyadh team runs discovery workshops in person, at your office or ours. We work on the commercial platform: pricing, payment, invoicing and account management. The meeting assistant's recording and AI features stay in your product, connected to billing through a documented interface.

Built for
Riyadh product companies and vendors selling AI meeting assistant plans to private firms, regional headquarters and public sector buyers in the capital.
Typical timeline
We agree timing at the end of the Riyadh discovery workshop, once procurement routes, payment providers and invoicing are settled, and record it in a written plan before any design work.
What you own
Source code, billing rules, gateway and Fatoora credentials, customer data, contracts and invoices, all in accounts held by your company rather than by us.
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 we build

A storefront for card buyers and a procurement path for institutions.

Riyadh is where ministries, authorities, listed companies and many regional headquarters sit, and they all hold a great many meetings: committees, steering groups, boards and executive reviews. That makes the city the obvious first market for a meeting assistant, but it also means many of your largest buyers will never type a card number into a checkout.

The platform we build therefore has two front doors. One is a clean self serve route for smaller teams in Olaya, King Abdullah Financial District and the city's growing startup scene. The other is a structured request for quote route that produces the documents a procurement officer needs. Both lead to the same billing engine, the same account area and the same ZATCA compliant invoices, so your finance team runs one system rather than two.

Explain your project
  • Procurement ready quote flow

    Buyers enter seat numbers, contract length and required documents, then receive a formal quotation in Arabic and English with your commercial registration and VAT details. Sales approves it in the admin area, and the subscription activates once the purchase order or signed agreement is uploaded.

    Institutional deals close without a chain of email attachments.

  • Annual licence billing

    Yearly contracts with fixed seat counts, mid term additions billed pro rata to the contract end date, and renewal notices sent to the finance contact early enough for a new budget line to be approved.

    Annual customers renew on time instead of lapsing over paperwork.

  • Card checkout for private firms

    A short Arabic first checkout with mada, Apple Pay, Visa and Mastercard through a SAMA licensed gateway, tokenised so monthly renewals charge automatically. VAT is shown clearly before payment so a Riyadh office manager can expense it without questions.

    Small teams start a paid plan in minutes.

  • Department and entity licences

    A parent account for a group or ministry, with seats split across departments, agencies or subsidiaries, each with its own administrator and usage view, while billing rolls up to one invoice or splits by cost centre as the customer requires.

    Large organisations manage licences without asking you to reassign seats.

  • Fatoora invoicing

    Invoices and credit notes generated by the billing engine for every renewal, upgrade and refund, in the format and with the fields required under ZATCA's phase two rules, including the QR code and Arabic content.

    Finance closes each month without retyping invoices.

  • Dunning around the working week

    When a monthly card renewal fails, retries and reminders follow a schedule built around the Sunday to Thursday week and public holidays, in Arabic and English. Premium features such as formal minutes pause in stages, so an executive committee is never cut off halfway through a recorded session.

    Expired cards are fixed before customers notice any interruption.

  • Data residency statement page

    A plain language page explaining where customer, billing and meeting data is stored, how the PDPL is applied and which NCA controls your hosting meets, written with your team so procurement and legal reviewers find answers before they send a questionnaire.

    Security reviews start from a documented position.

  • Pilot to paid conversion

    Riyadh deals often begin with a time limited pilot for one committee or department. The platform tracks each pilot's start and end, usage and contacts, then turns it into a paid subscription with the agreed price, without recreating the workspace or losing the meetings already recorded.

    Successful pilots become contracts without a messy hand over.

  • Entitlements and usage sync

    When a contract changes, the billing service updates the meeting assistant's limits on seats, recording minutes and premium features, and minute usage returns to billing for reporting, overage and renewal planning.

    Access always matches what the customer has paid for.

  • Sales and revenue dashboard

    Open quotes, contracts awaiting purchase orders, renewals due this quarter, monthly recurring revenue and churn, visible to sales leaders and finance in one view and exportable to your accounting system.

    The pipeline and the billing ledger tell the same story.

Who this is for

Four Riyadh teams this platform is designed around.

Meeting assistant companies in Riyadh rarely sell to one type of customer. A single product might be piloted by a startup in a co working space, bought by a bank's strategy office and evaluated by a government authority in the same month. These are the situations we plan for, each with a different emphasis in the first release. Whichever one sounds closest, the same rule applies: the first version should handle the buyers you already have in conversation, not every buyer you might meet next year.

01

A Riyadh startup moving from pilots to revenue

Your assistant has proven itself in a handful of free pilots and the next step is charging. We build a focused AI meeting assistant SaaS website development Riyadh founders can launch quickly: an Arabic pricing page, card checkout, a trial you can switch on or off as a product decision, and invoices that are compliant from the first payment. Enterprise routes are added when the first institutional buyer asks for one.

Launch with the simplest plans that still reflect how customers use meetings.

02

A vendor selling to the public sector

Government entities in Riyadh often buy through formal tenders and the Etimad platform rather than a website checkout. Your site still matters: it carries the product information, the data residency position and the quotation route that procurement teams reference. We build those pages and the account area that licensed users log into once the contract is awarded.

Tender submissions themselves stay with your bid team.

03

A regional headquarters selling across the Gulf

Companies under the Regional Headquarters Programme often sell from Riyadh into several Gulf countries. The platform handles Saudi invoicing for Saudi customers and separate tax treatment elsewhere, with currency and language settings by market, so one billing system serves the region without mixing the rules.

Tax treatment for each country should be confirmed by your adviser.

04

An established product with messy billing

Some Riyadh companies already have hundreds of customers billed through spreadsheets and manual transfers. We move them onto an AI meeting assistant subscription platform development Riyadh finance teams can trust, migrating renewal dates, seat counts and agreed prices so that no customer sees a surprise on the next invoice.

From a Riyadh workshop to the first automated renewal.

  1. 01In person discovery in RiyadhA working session with product, sales and finance to map plans, buyer types, procurement routes and the invoices each customer group expects.
  2. 02Commercial model and cataloguePlans, seat and minute units, contract terms and discount rules written as a single catalogue the platform reads from, approved by your finance lead.
  3. 03Design for two buyer pathsArabic first screens for the self serve checkout and the quote route, reviewed in person with your team and tested with real procurement documents.
  4. 04Billing, invoicing and gateway buildThe billing engine, gateway integration, Fatoora invoicing and the entitlements link to your product, built against agreed scenarios such as a mid term seat increase.
  5. 05Rehearsed migrationExisting customers and contracts imported in test runs first, checked line by line against your records, then moved live on a date chosen around your billing cycle.
  6. 06Live support through renewalsWe watch the first monthly renewals and the first annual notices closely, then hand over runbooks so your team manages prices and credits independently.

Technology

What we build this with.

Storefronts are typically built in Next.js, with a subscription billing service chosen or written around your pricing, gateway integrations with SAMA licensed providers, and hosting in Saudi data centres where your buyers require local storage. Your CRM and accounting system are connected so that quotes, contracts and invoices share one customer record.

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 meeting assistant companies ask us.

It depends on how many buyer paths and integrations the first release includes.

A self serve storefront with a few card plans and compliant invoicing is the quickest route. Adding the quotation and purchase order path, entity licences, migration of existing customers and a full Fatoora integration each extends the plan. We fix the timing at the end of the in person discovery workshop in Riyadh, once these decisions are made, and write it into the delivery plan so your sales team knows when each route goes live.

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