I’m now open for founder-led SaaS MVP and marketplace web app builds.
I help early-stage founders turn rough product ideas into usable MVP structure: product scope, user flows, role-based dashboards, booking/request flows, bilingual Arabic/English interface planning, and launch-ready product direction.
Recent builds include commission-proof platforms, marine marketplaces, property-management dashboards, and custom service-request systems.
Best fit:
• SaaS MVPs
• Marketplace platforms
• Booking or request-flow apps
• Admin dashboards
• Founder-led product ideas that need structure before scaling
My approach is practical: define the core flow first, avoid unnecessary features, and build around the real business use case.
The dashboard preview in the hero does a lot of the selling here. When a client wants this live I usually build the hero widgets as real React components with sample data so the page already feels like the product. Happy to pair on the build side if one of these turns into a Next.js project.
A playful SaaS website concept designed and built in Webflow, featuring custom UX/UI design, an interactive product tour, and AI-generated brand visuals.
The dinosaur mascot makes the whole page feel friendly without hiding the product, Lena. Was the product tour built with Webflow interactions or did you bring in custom code for it? I have seen tours like this get heavy on mobile once they grow past four or five steps.
A court copy request can pass through several teams before it’s ready for delivery. At each step, staff need to know where the request stands, who’s responsible for it, and what happens next.
That’s the workflow I'm building into CAMS V2 (Copy Agency Management System). I helped implement its district-based multi-tenant architecture with support for multiple countries. Each district has its own workspace for managing copy requests, and staff access depends on both their role and assigned location.
The platform covers the day-to-day work of a court copying branch:
Copy requests: Staff can create and track normal and express applications from receipt through the copying branch to delivery.
Role-based access: Court staff, copying branch staff, and administrators have permissions suited to their responsibilities and jurisdictions.
Fees and payments: Staff can manage copying fees and record payments against individual requests.
PDF views and reporting: Staff can open application details as PDFs and review requests by status and location.
My work spans the React frontend and Laravel backend. Alongside the tenancy work, I contributed to application forms, status tracking, PDF views, and payment integration. I also rewrote date filters and added MySQL indexes for queries the application lists use frequently.
If you’re building a SaaS platform that needs to support multiple locations and coordinate work across teams, I’d be happy to talk.
Status plus owner plus next step is exactly what staff need on a request like this. On a multi city POS build I worked on each city only saw its own stock and sales at the query level and not just in the UI. It saved a lot of trouble later. How are you handling that split between districts in CAMS V2?