Service · SaaS & web apps
SaaS and web app development: one product instead of ten tools.
From the user journey to the product online: screens designed one by one, a clickable prototype, then development with AI and, when the project needs it, the team's developers. One person accountable from the first sketch to production.
The need
The work gets done. In ten tools that don't talk.
Before a SaaS, there is usually a knot: spreadsheets, WhatsApp groups, emails and copy-paste, held together by one person who knows where everything is.
- 01
Data in five places
The same client exists in a spreadsheet, a CRM and three email threads, never quite the same.
- 02
Steps done by hand
Every order, invoice or report is copied from one tool to the next, with the errors that come with it.
- 03
Nothing you can sell
The process works for your team, but it isn't a product others could pay for.
The process
Built up layer by layer.
Who uses it, to do what, in what order: the user journey mapped before a single screen.
Every screen designed, with real content and the empty, loading and error states nobody draws.
A clickable version tested with real users, so changes cost minutes, not sprints.
Developed with AI and the team's developers, deployed, and handed over with access and documentation.
The result
Every cable in one console.
The impact is the knot undone: one place for the data, the steps automated, and a product people can use without a training session.
- 01
One source of truth
Each client, order and number exists once, and everyone sees the same thing.
- 02
Hours handed back
The copy-paste between tools goes away; the team does the work only people can do.
- 03
A product to sell
Infounder is a SaaS platform; Flaha.ma a marketplace. Built to be used by people outside the team.
(02) Products, from SaaS to banking.
Sites and products in production, for clinics, brands and founders. Each cover opens the live site or the case study.
All projectsInfounder
Every screen designed, from the first rough sketch to finished pages their developers could build straight from.
SaaS platformRead the caseFlaha.ma
Clearer listings, a far simpler way to post one, and proof of who you are dealing with on every page.
MarketplaceVisit the siteBank ALBILAD
Every place they gave up, mapped, then a rebuild around the handful of things people actually come to do.
UX audit, redesignRead the case
Questions
Before you write.
01Do you build the back end too?
Yes, with AI-assisted development and, for heavier back ends or integrations, the team's developers. I stay accountable for the whole.
02Can we start with a prototype?
Yes. A clickable prototype is often the right first step: it tests the idea before the full build.
03Who owns the code?
You do: the repository, the hosting and the accounts are in your name.
04How much does a SaaS or a web app cost?
The price depends on the scope: number of pages or screens, features and languages. Send the brief and you get a written reply within 24 hours with the scope, the timeline and a fixed price.