Services · Ecommerce development · CRM subscription sites
We deliver CRM subscription website development in Jeddah for software teams selling CRM tools to trading houses, freight forwarders, hotels and Umrah travel operators across the western region. The platform covers the pricing site, checkout, recurring billing, seat changes and invoices, and it is designed for customers whose headcount rises sharply before Ramadan and the Hajj season and falls again afterwards. Billing follows those swings fairly, so customers keep paying instead of cancelling.
Discovery and design reviews with Jeddah clients run by video call, with our Riyadh and Dubai teams joining the same sessions. You see working screens at every review rather than slides. Whether you need a full CRM subscription platform development Jeddah project or only the public site, the same team carries it from plan design to launch.
200+ companies servedFrom a first store to an ADX listed developer
What we build
A CRM vendor in Jeddah rarely sells to steady, predictable teams. An Umrah operator may double its call centre staff for Ramadan. A clearing agent near Jeddah Islamic Port adds coordinators when shipping volumes rise. A family trading group runs several companies, each with its own commercial registration and VAT number, but wants one contract with you. Standard subscription templates handle none of this gracefully. We design the billing model around how your customers actually buy: temporary seats with clear end dates, group accounts with separate invoices per entity, and a site that explains all of it in Arabic first, plain enough that an operations manager can choose a plan without a meeting. Payments run through a SAMA licensed gateway, and every invoice is issued in line with ZATCA e-invoicing. Long-standing habits, such as Jeddah firms paying suppliers by bank transfer at month end, stay supported alongside card payments.
Customers add a block of temporary users for a fixed window, such as the weeks around Ramadan or the Hajj season, priced separately from the core plan. The seats expire on their end date and the customer is charged only for the period used.
Peak season brings extra revenue instead of cancellations.
One parent account holds several companies, each with its own commercial registration, VAT number and billing contact. Users move between entities, while invoices stay separate so each company reclaims its own VAT.
Family groups buy once and account for it correctly.
Right to left pricing pages that describe plans in terms Jeddah buyers use, such as bookings handled, shipments tracked or agents on shift, rather than abstract feature lists. English versions sit alongside for expatriate managers.
The right plan is chosen without a sales call.
mada, Visa, Mastercard, Apple Pay and STC Pay at checkout through your gateway, with 3D Secure and saved tokens held by the provider. Annual plans can be paid by bank transfer against an invoice.
Customers pay the way they already pay suppliers.
When seats are added mid-cycle, the platform charges the remaining fraction of the period and shows the calculation on the invoice line. Downgrades take effect at renewal unless you choose otherwise.
Fewer disputes about unexpected charges.
Simplified invoices for individuals and standard tax invoices for businesses with the buyer's VAT number and national address, plus credit notes when seats expire early or a refund is agreed, all reported according to your ZATCA integration phase.
Customers can reclaim VAT without asking for corrected invoices.
Notices before renewal, before seasonal seats expire and after a failed charge, sent by email, SMS through a registered sender name, or WhatsApp templates approved on your business account.
Renewals are expected, not a surprise.
Owners and finance contacts see the current plan, active seasonal packs, upcoming charges and every invoice. They can switch entity, update a card or add users without contacting support.
Your support desk handles product questions, not invoice requests.
Your CRM reads the plan, seat count and expiry dates from the billing platform, so temporary users lose access on schedule and paid modules switch on as soon as the charge clears.
Access always matches what the customer has paid for.
Charge for what customers consume, such as shipments tracked, bookings processed or WhatsApp conversations sent, alongside a base plan. Usage is read from your product each day, shown to the customer as it accrues, and billed at the end of the cycle with a clear breakdown on the invoice.
Busy customers pay more, quiet months cost them less.
Who this is for
Jeddah's economy runs on trade through the port, on visitors arriving for Umrah and Hajj, and on long-established family businesses. A CRM vendor here usually serves at least one of those groups, and the billing platform has to reflect how they budget, approve and pay. These four starting points cover most of the vendors we speak to on the west coast. Many Jeddah vendors also sell to customers in Makkah and Madinah, where the pilgrimage calendar drives demand even more sharply, so the same seasonal logic applies across the region. Whichever group you serve, the aim is the same: make paying for your CRM as easy as using it.
Your customers manage pilgrim enquiries, group bookings and agent commissions, and their staffing changes through the year. We build seasonal seat packs, short-term plans and reminders timed to the calendar, so an operator can scale up for Ramadan, scale back afterwards and stay subscribed. Hijri dates can be shown alongside Gregorian ones on invoices and renewal notices. Group deals, for example a block of seats for a consortium of operators, can be billed through a single contract with per-company invoices.
Seasonal pricing rules are set by you and easy to change each year.
Forwarders and customs brokers around the port want plans priced by shipments or users, with clear invoices their accounts team can match to a purchase order. We add usage metering, purchase order fields and annual invoicing by bank transfer, and keep card checkout for small agents who want to start immediately. Customers in other Red Sea and Gulf markets can be priced and invoiced separately, with the VAT treatment confirmed by your tax adviser.
Usage figures come from your product, so the meter is trusted.
Group finance wants one agreement and one renewal date, while each subsidiary needs its own tax invoice. We design parent and child accounts with consolidated reporting and separate Fatoora invoices, so the group sees total spend and each entity books its own cost and VAT. Approval rules let the group finance director sign off seat increases above a threshold before they are charged.
Entity structure is agreed in discovery before any screens are designed.
Hotels and serviced apartments use guest CRM and loyalty tools priced per property or per room count. We support property based plans, multi-property groups and add-ons such as messaging credits, with a pricing page that lets a general manager compare options quickly before passing the decision to head office. Seasonal demand around events and holidays in Jeddah can be matched with short-term add-ons, priced and expired the same way as seat packs.
Per-property billing keeps group invoices tidy.
Working with Codeeo
We are a team of 80+ across Dubai, Riyadh and Karachi, with 200+ projects delivered across the UAE and the US, and a 4.7 rating from 23 Google reviews. Jeddah engagements run by video call with shared boards and staging links. Cost is driven by the number of billing rules you need, especially seasonal packs, group entities and usage metering, by how many payment methods you accept, by whether a custom billing service is needed and by how much customer data has to migrate from your current system. We give you a written estimate after discovery, broken down by release, so you can decide what goes live first and what waits.
After launch, we watch the first renewal runs and the first seasonal peak with you, because that is when real customers test proration, reminders and expiry dates. Ongoing support continues on an agreed scope, or we hand over to your own developers with documentation of the billing model and the code.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
We choose between a subscription billing platform and a custom billing service built in Laravel or Node, depending on your gateway and how unusual your seat rules are. Front ends use Next.js or WordPress, hosted in a region that suits your data obligations. Webhooks are signed and replay safe, so a delayed gateway message never charges a customer twice.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
We set the timeline after discovery, around your sales calendar.
Vendors serving Umrah and hospitality customers often want the platform live before a peak season, so we plan backwards from that date and phase what is essential. Core plans, checkout and invoicing usually come first, with group accounts or usage metering in a second release if needed. Gateway approval and ZATCA onboarding on your side also affect timing, so we start those early. Content such as Arabic plan descriptions, terms of service and the refund policy also needs approval from your side, and we schedule review time for it from the first week.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio