Services · Mobile app development · Home services apps
Codeeo delivers home services app development in Saudi Arabia for marketplaces, maintenance groups and property businesses that want one platform across several regions. We build the customer app, the provider app and the operations dashboard, and we connect them to the national systems Saudi users already trust: Nafath identity, National Address, mada and other local payment methods, and ZATCA e-invoicing. The result is a product that can launch in one city and add the next without a rebuild.
Our team of 80+ works from Riyadh, Dubai and Karachi. Riyadh clients can meet us in person; clients in other Saudi cities work with us by video call. You own the code and data outright. Discovery outputs and decisions are kept in writing for every stakeholder.
200+ companies servedFrom a first store to an ADX listed developer
What a national home services platform needs
Home services in the Kingdom are delivered by a mix of app-based marketplaces, established maintenance companies, property managers, developers offering after-sales care and a long tail of small workshops. A platform that wants national reach has to work for all of them as providers, and for customers from very different regions, climates and housing types.
The hard part is rarely the booking screen. It is the layer underneath: verifying who customers and providers are, finding homes reliably, collecting payment the way Saudi customers prefer, issuing compliant invoices and handling personal data under Saudi law. We build that layer once, properly, so every new city plugs into it. The capabilities below are the ones national operators ask us about most.
Providers verify their identity through Nafath during onboarding, and you can offer the same option to customers for higher value jobs. Commercial registration details for partner companies are captured and checked as part of approval. Verified status is shown on provider profiles so customers can see it before they confirm a booking.
You know exactly who is entering customers' homes.
Customers can enter their National Address short code, drop a map pin or both. The app stores building and unit details on top, so technicians arrive at the right door in any city, including newer districts where street names are still unfamiliar. Saved addresses carry gate, floor and parking notes for repeat visits.
Fewer failed visits caused by unclear addresses.
mada cards, Apple Pay, STC Bank and credit cards in the app, SADAD for larger invoices where it suits the customer, and buy now pay later through SAMA licensed providers such as Tabby and Tamara for bigger jobs. Cash on completion can be allowed in cities where customers still expect it, with the technician recording it in the app.
Customers pay with what they already use.
Every completed job produces a VAT invoice that meets ZATCA's Fatoora requirements, whether the seller is you or a partner provider. Commission invoices to providers are issued the same way, so the whole marketplace stays compliant. Credit notes for refunds follow the same rules.
Tax compliance built into every transaction.
Each city has its own service catalogue, visit fees, working hours, provider pool and dispatch zones, all managed from one dashboard. Seasonal settings differ too, because demand for cooling, water heating and leak repairs varies between the interior, the coasts and the southern highlands. Ramadan and Eid working hours can be set per city in advance.
Launch a new city by configuring it, not rebuilding the product.
Trade skills, professional verification results from the Ministry of Human Resources programme, work permits, commercial registrations and municipal licences issued through Balady are stored with expiry dates. Expiring documents trigger reminders and, if ignored, automatic suspension. Regional managers see compliance status for their own provider pools.
A provider network you can stand behind with regulators and customers.
Commission rates by trade, city or provider tier, payout schedules, holdbacks for warranty periods and adjustments for refunds are calculated automatically, with statements each provider can see in their own app. Finance teams can export provider statements and reconcile them with the gateway in one step.
Providers are paid correctly and on time, which keeps good ones loyal.
The customer app is designed right to left in Arabic from the first wireframe, with English as a full alternative. Service names, guided questions and notifications are written in natural Saudi Arabic rather than translated at the end. Provider screens can also run in other languages your technicians prefer.
An app that feels local in every region.
Head office sees bookings, response times, ratings, cancellations and revenue by city, trade and provider, with drill-down to individual jobs. Regional managers see only their own cities. Reports use the same definitions everywhere, so a response time in one region means the same thing in another.
Expansion decisions based on comparable numbers from every city.
A national brand lives or dies on how it handles complaints. Customers can reopen a job within your workmanship warranty, raise a dispute with photos, and receive a refund or a free return visit according to rules you set. Payout holdbacks mean the cost of a failed repair is recovered from the provider responsible, not absorbed by head office.
Consistent complaint handling in every city, with costs landing where they belong.
Who this is for
Operating across several Saudi cities changes what an app must do. Supply has to be recruited city by city, compliance has to hold everywhere, and reporting has to compare regions fairly. These four types of business come to us most often with national plans, and each starts from a different place, but all of them end up needing the same shared national layer underneath. We help you decide which city to open first and in what order the rest should follow.
You want one brand for AC, plumbing, electrical, carpentry and handyman work across the Kingdom. We build the national layer first, identity, address, payments, invoicing and payouts, then launch in a single city with a carefully recruited provider base. Once response times and ratings hold there, the next city is configured and opened. Investors and partners see a repeatable rollout model rather than a one-city experiment. The order of later cities can change as you learn, without any change to the product.
Prove one city, then copy the playbook.
You already run teams in more than one city, each with its own phone numbers and spreadsheets. A shared platform gives every branch the same booking, dispatch and invoicing process while letting local managers keep control of their technicians. Head office finally sees comparable performance figures, and customers who move between cities find the same service wherever they live. Branch managers keep their own targets and staff, while shared tools remove the duplicated effort of each branch running its own systems.
Buyers in your projects expect support after handover. A branded service app covers snag reporting during the defects period, then paid maintenance and home improvement services afterwards. Because your communities sit in different cities, contractor assignment and pricing follow each location, while your customer service team works from one view of every home you have sold. Snag data across projects also helps your construction teams spot recurring defects early.
After-sales care often becomes a revenue line of its own.
You maintain offices, schools or retail sites under contract and want to serve households too. The platform reuses your technicians, stock and dispatch, but adds a consumer booking app, card payments and ratings. Contract and household work run side by side, and planners can balance them across cities based on where demand appears each week. Your existing quality procedures carry over, which gives the residential arm a head start on trust.
How we work together
National platforms usually begin with a fixed scope project covering the shared layer and the launch city. After that, a retainer or a dedicated team carries the expansion, adding cities, trades and integrations on a steady release cycle. Larger groups often combine the two, keeping a core team on the product while separate pieces of work handle specific integrations. Whatever the model, scope and reporting are agreed in writing at the start, with a named lead on our side who stays with the platform as it grows from one city to many.
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
Native or cross platform apps, a web dashboard and cloud infrastructure that can be hosted inside the Kingdom. We plan for growth from the start, so adding cities, providers and bookings does not force a change of architecture later, and monitoring alerts your team before a busy period strains the system.
01Mobile
02Data and cloud
03Marketing and tracking
It depends on the national integrations and how many cities launch first.
A platform that launches in one city with core trades, local payments and ZATCA invoicing reaches the market far sooner than one that opens several cities at once with subscriptions and corporate accounts. We fix the scope and first release dates together at the end of discovery, and we plan later cities as separate stages so they do not hold up the launch. Most national operators find that the first city teaches them more than any amount of planning, so we keep that first release lean on purpose.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
Swift
Kotlin
Flutter
React Native
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio