SaaS · Web app · Custom software
Web app and SaaS development from the first screen to release.
A web app or a SaaS succeeds when the people using it reach their goal without help. That comes from the journey and the screens before the code, then from a product built and released, not just designed.
I design and develop web apps, SaaS products, dashboards and custom tools, with AI-assisted development and, when the project calls for it, the team's developers. One person accountable from the first sketch to production.
Where products stall
The idea is good. The product isn't used.
- 01
Built before it was designed
Features coded before anyone mapped the journey. Users get lost and support fills up.
- 02
Designers and developers in two worlds
Mock-ups that can't be built, builds that don't match the mock-ups, and weeks lost between them.
- 03
Dashboards nobody reads
Every number on one screen, none of them the one that matters this morning.
- 04
A prototype that never ships
A beautiful Figma file and no product in production.
What you get
A product designed and built by the same team.
- 01
User journeys and screens
Who does what, in what order, and every screen it needs, validated before development.
- 02
A clickable prototype
Tested with real users so changes are made when they cost minutes, not weeks.
- 03
Development and release
Front end, back end and integrations, built with AI-assisted development and the team's developers, then put in production.
- 04
Dashboards that guide the next action
The figures that matter at a glance and the next step two clicks away, on desktop and phone.
Measured
Shipped, then measured.
A product is finished when it is used. Every release comes with the events that show whether users reach their goal: sign-ups, activations, the actions your business lives on.
The projects below go from a SaaS platform to a marketplace and a banking UX audit. Every product is different; what I can promise is a product designed and built with the same care.
SEO in detail How it is built, step by step(02) SaaS, marketplace, 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
How it works
From one link to a site that brings clients.
One link and one line on what isn't working. No call needed to start.
Within 24 hours: the three things I would change first, the scope, the timeline and a price.
New pages around the action you want, a clickable version to test, then development.
Online, Search Console set up, Google Business linked, and the first pages written for real searches.
Questions
Before you write.
01Do you only design, or also develop?
Both: journeys, screens and prototype, then development and release, with AI-assisted development and the team's developers when the project needs them.
02Can you build an MVP for a SaaS?
Yes. The scope is cut to the journey that proves the idea, then extended release by release.
03Do you build dashboards and internal tools?
Yes: back-offices, dashboards and tools your team uses every day, on desktop and mobile.
04How long does a web app take?
It depends on the scope. An MVP usually takes weeks to a few months; the reply to your brief gives a timeline.
05How is pricing done?
A fixed price per phase (design, prototype, development), written in the reply to your brief.