What you get

SaaS application development: what a first release includes.

The workflow your customers pay for, plus what every SaaS product needs on day one. The rest waits for later releases, on a dated plan you approve.

Multi-tenant accounts and roles
Each customer company gets its own workspace, users and permissions, with its data kept apart from every other tenant.
Subscriptions and billing
Pricing plans, sign-up, recurring payments through a gateway such as Stripe, and invoices sent automatically, with VAT where it applies.
The core workflow
The one job your customers sign up for, built and tested end to end before any extra feature.
Admin panel
Your back office for tenants, plans, users and support requests, so you run the service without waiting on a developer.
Arabic and English
Right-to-left Arabic screens designed beside the English ones from the first wireframe. Adding Arabic later means reworking every screen.
Room to scale
The database and background jobs planned for many more tenants, plus usage data that shows what to build next.
Stack
Flutter, Laravel/PHP, Java, .NET, Go, Python
How we deliver software, from brief to release
How it runs · 4 steps

Four stages, with quality built into every step.

CTO oversight on the architecture, independent QA before each release, and a dated plan in FloPlan, the delivery software we built and use ourselves.

  1. 01

    Plan

    The tenant model, billing, roles and architecture go into a dated release plan. A CTO-level lead signs off the decisions that are expensive to reverse.

  2. 02

    Design and build

    Arabic and English screens designed together, then built in short increments you can see and try.

  3. 03

    Independent QA

    QA tests apart from the developers before each release: features, security, performance, and that no tenant can see another’s data.

  4. 04

    Launch

    We launch with you, support the first roll-out, and add the next modules release by release.

Get the phases, team and price for your first SaaS release

Case studies · 2

SaaS we built.

We developed Massart. On ButlerFM, our engineers joined the client’s own product team. Meet the people who did the work, and ask how they would plan your product.

  • Facility services SaaS

    ButlerFM

    Facility-management SaaS for cleaning businesses, with a web dashboard for the office and a mobile app for field staff’s checklists and QR check-ins.

    Talk to the team that worked on it: book a meeting

  • No-code app builder · Saudi Arabia

    Massart

    A no-code app builder: businesses build and publish their own iOS and Android apps from one platform, with drag-and-drop tools.

    Talk to the team that built it: book a meeting

Saudi Arabia

SaaS for Saudi companies.

Massart is our Saudi SaaS work. For a Saudi company building a SaaS product, the screens are Arabic first and checked by native Arabic speakers, our engineers work the same Sunday to Thursday week within an hour of Riyadh time, and the contract and support run from our Dubai headquarters.

Software development company for Saudi Arabia
FAQ · 8

Questions before a first call.

How much does SaaS development cost?

Your price is agreed in your proposal, once the first release is planned. It follows the effort: the user roles, billing, integrations, and whether you need mobile apps as well as the web platform. Then the phases that work runs through, and the team it needs, usually a project manager, developers and QA, with a CTO-level lead on the architecture. Modules after launch are estimated as you add them.

Who is on a SaaS application development team?

A product owner turns your idea into the first-release list and keeps the backlog in order, and a project manager owns the dates. A CTO-level lead decides the tenant model, billing and architecture. A UI/UX designer draws the Arabic and English screens, which native Arabic speakers on our core team check. Back-end and front-end developers, and mobile developers if you need apps, build it with a technical lead reviewing the code. A QA engineer who doesn’t write the code tests every release. Your proposal shows who works in each phase.

How long until the first release?

We agree the first release and its date in a written product plan before development starts, so you know the launch date early. The usual scope is the six parts listed on this page, and the more you leave for later releases, the sooner you launch.

Do you build multi-tenant SaaS, and how is each customer’s data kept apart?

Yes. Multi-tenant means one platform serves many customer companies, each in its own workspace with its own users, roles and settings. Their data is kept apart in one of three ways: a tenant ID on every record in a shared database, a separate schema for each tenant, or a separate database for customers who ask for one. We choose in the plan stage, because the choice is hard to reverse, and QA checks every release for one tenant seeing another’s data. Massart, above, serves many businesses from one platform.

How do subscriptions and VAT work for a SaaS sold in the UAE?

The platform holds your plans, trials, upgrades and cancellations, charges the card on each renewal through your payment gateway, and retries failed payments before access stops. UAE VAT is 5%, and registration is mandatory once your taxable sales pass AED 375,000 in 12 months. After that, every invoice is a tax invoice with your TRN and the VAT shown, and business customers’ TRNs are kept on their accounts. From your e-invoicing date, invoices to UAE businesses go as structured data through an Accredited Service Provider, so we plan the invoice data for it from the first release. Your tax agent confirms how VAT applies to customers abroad.

Can our SaaS serve customers in Saudi Arabia?

Yes, if it is planned for them from the first release. Saudi buyers expect Arabic first, mada beside Apple Pay and cards through a licensed Saudi payment gateway, and prices in riyals with 15% VAT. If the platform invoices Saudi businesses, we plan the invoice data, VAT fields and QR code to ZATCA’s e-invoicing rules, so the e-invoicing system you use can report them. Some customers will ask where their data is stored, so the hosting region is agreed in discovery.

What should we ask a SaaS development company before choosing one?

Ask how each customer’s data is kept apart, how billing and invoices will work, whether Arabic is designed from the first screen or added later, who tests apart from the developers, and how you will see the plan and its dates. Then ask to talk to the team behind a SaaS product that is already live.

Who keeps building the product after launch?

We can, with new modules and releases on the same plan. Or our engineers join your own product team through team extension, as they did on ButlerFM, where they filled gaps in the internal team.

Bring your SaaS idea and who it’s for.

We ask about your idea and who it’s for, what you use today, your launch timing and who else should be involved. You leave with clear next steps. We reply by email first and set up a call only if you want one. Asking commits you to nothing, and we sign an NDA first if you ask.