The process lives in spreadsheets
Files get copied, versions diverge, and nobody can see what is waiting on whom.
OH Studio
Custom web applications for the workflow your tools do not cover
OH Studio builds Laravel applications when the business process is the product: accounts, roles, dashboards, and the records your team touches every day.
What gets in the way
A generic tool almost fits
The monthly SaaS is close, then every exception becomes a manual workaround.
There is no permission model
Everyone sees everything, or one person holds the only login.
How the work is shaped
A Laravel app shaped around the records
The brief names the objects: clients, orders, courses, tickets. The admin is built around those, not around a demo.
Roles before extra features
Who can create, edit, and export is decided early. Filament is used when that admin should stay fast to change.
An API only if something else must call it
A mobile app or a partner integration gets an API in the scope. A single web app does not grow one for show.
Technologies
Laravel
Filament
MySQL
Vue
REST
What you can expect
- The technical brief is the spec. The quote follows it.
- Staging exists before production data is touched.
- Auth and roles are features, listed in the price, not implied.
- The same studio can add a Flutter client later against the same API.
Related work
Leonis Collection — Luxury Stays & Concierge Platform
Leonis Collection is a bilingual luxury-stay and concierge platform for Morocco, designed and developed end-to-end by Omar Hajjoub at OH Stu...
View project
Multilingual PropTech Platform: Resilient CRM & Agent App
Case study: multilingual property site, Filament admin, payments, Flutter app, Hostinger legacy DB resilience by Omar Hajjoub.
View project
Omar Hajjoub Studio: Full-Stack Digital Business Platform
Explore Omar Hajjoub Studio, a production-grade platform unifying portfolio, AI, CRM, e-commerce, and mobile app. See full-stack mastery in...
View project
IPTV Channel Directory & Multi-Site License Infrastructure
Enterprise-grade IPTV channel management & licensing infrastructure built with Laravel 12 and Filament 4
View project
School System LMS
A multi-tenant learning management platform for educational institutions
View project
Payvlo: Simplified Invoicing & Checkout for Freelancers
Streamline freelance invoicing and payments with Payvlo, a unified platform for beautiful invoices and secure checkout experiences.
View project
Client reviews
Ahmed Karimi
Omar delivered an exceptional e-commerce platform. The attention to detail in both design and code quality was outstanding. Highly recommend!
Sara Mansour
Incredible work on our mobile app. Omar has a rare ability to understand business needs and translate them into beautiful, functional products.
Karim Belhaj
The WordPress site Omar built increased our conversion rate by 40%. Fast delivery, clean code, and stunning design. A true professional.
How a project runs
Technical brief
Actors, records, and the one workflow that must work in version one.
Model
The data and the roles are agreed before the screens multiply.
Admin
Your team uses the staging admin with sample records.
Production
Deploy, backups, and the first real users are a separate step from the demo.
Questions clients ask
What counts as a custom web application?
Software your team logs into: a CRM, an LMS, an internal tool, a marketplace. A brochure site is web development, not this page.
Can you start from a tool we already pay for?
Sometimes the right answer is to keep it. The brief is also where that gets said, before a rebuild is priced.
Who owns the code?
The scope states the handoff. You should expect the repository and the admin, not a locked binary.
How is this different from the enterprise pack on the services page?
That pack is an indicative range for larger Laravel platforms. This page is the offer. The brief turns it into a quote.
Write down the workflow version one must finish
Use the technical brief. Name the people who log in and the record they create, edit, or close.