Service: SaaS and MVP development
SaaS development, from first version to running product
I build software products that people log into and pay for: accounts, roles, dashboards, payments and the back end that holds them together. One full stack developer, front end to back end, who stays after launch to keep it running.
Who this is for
- Founders with an idea and a budget, who need a working first version in front of customers.
- Businesses that want to turn an internal tool or a service into a product other companies pay for.
- Teams stuck on spreadsheets and subscriptions that no longer fit, who need their own platform.
What a SaaS build can include
- Accounts and roles: sign up, log in, and different permissions for owners, staff and customers.
- Separate spaces per customer, so each business on the platform sees only its own data.
- Dashboards where your users run their part of the product.
- Payments, one-off or recurring, through a payment provider in your name.
- An admin panel for you, to see and manage everything on the platform.
- Integrations with the tools your users already work with.
- Hosting and deployment, set up in your accounts and documented.
Built for Savant, Dubai
Savant is a booking platform for a multipurpose event space in Al Quoz. It works like a small SaaS: the instructors who rent the space each get their own CRM dashboard, with their own bookings and guests, while guests book and pay on the public side. I built it alone, front end to back end. Read the case study.
What I build with
React and TypeScript on the front end, Laravel and PHP on the back end, MySQL for data, and Stripe for payments, with a regional provider such as N-Genius alongside it where Gulf cards need one. Savant runs on exactly that stack, with 961 tests behind it.
These are ordinary, widely used tools on purpose. Any competent developer can pick the code up, which matters more for a product you may raise money on, sell, or hand to a team later.
How a SaaS project runs
- A call about the product, who it is for, and what the first version must do.
- A written scope for the first version, with a fixed price and a timeline, before any code.
- The build, in your accounts from the first day.
- Launch, then care: the product kept running, and new features quoted one at a time.
What it costs
SaaS builds start at $5,000 (about AED 18,400). More features cost more, and the first version is scoped so you pay for what you need to launch, not everything you might want later. Care and maintenance after launch starts at $99 a month. You get the exact price in writing before anything starts.
Questions people ask
Should I build a full product or an MVP first?
Almost always an MVP: the smallest version that real customers will pay for or use. It costs less, reaches people sooner, and tells you what to build next with evidence instead of guesses.
Who owns the code?
You do. The code, the repository, the hosting, the domain and every account are registered in your name from the start, never mine. That matters even more for a product you might raise money on or sell.
What happens after launch?
Care and maintenance starts at $99 a month and keeps it updated, backed up and fixed. New features are quoted one piece at a time, each at a fixed price before work starts.
What happens if you disappear?
Everything lives in your accounts, documented, with access you control. If I vanished tomorrow, another developer could pick it up on day one. That is the standard I would want if I were paying.