The process lives in one person's head
When that person is on leave, the work stops. Nothing about the handover is written down, because the tool never asked for it.
Services
Web application development
A web application is the right answer when the work is shared, role-based, or has to be available outside one machine. We build it as a product: a real data model, permissions, an admin surface, and an interface that survives a slow connection and a phone screen.
Who it is for
- Businesses running an internal process through email and spreadsheets.
- Companies that need a customer or partner portal.
- Teams replacing a desktop tool only one person can open.
Problems it solves
Everyone edits the same file
Two copies, a conflicted upload, and a decision that cannot be traced to a person or a date.
The tool does not work on a phone
The people who need it most are standing in a warehouse or sitting with a customer, not at a desk.
Use cases
Customer or partner portal
Login, documents, requests and status — without an email thread per request.
Operations dashboard
Live numbers from the systems that already hold them, with every definition written down.
Internal approvals
A request, a decision, and a record of who approved what and when.
Booking and scheduling
Availability, confirmation and a calendar the whole team can trust.
What is in scope
Fixed scope. Fixed price.
Agreed in writing before anything is built. You approve before we start.
- Information architecture and the screens that matter
- Data model, roles and permissions
- Arabic RTL and English from the same codebase
- Server-rendered pages, so content is crawlable and fast
- Deployment, backups and monitoring
- Handover: repository, environment variables and a runbook
How it is delivered
- 01
Define the decision, not the page
Every screen exists so someone can decide or act. We start from that decision and work backwards to the fields.
- 02
Build the thin path first
One role, one complete task, end to end — before the second role and the edge cases are added.
- 03
Test on a real phone, on a real connection
The laptop on office Wi-Fi is the easiest case, not the target case.
- 04
Document the definitions
Every number on a dashboard has a written definition, or it is decoration.
FAQ
Questions about this service.
What owners usually ask before requesting a quote for it.
Do you use a template or a framework?
We use a framework — Next.js, TypeScript, Tailwind — and write the application. We do not resell a theme and call it custom.
Can it be Arabic-first?
Yes. Arabic is designed as a first-class layout, not a translation layer added at the end. That is a build decision, not a CSS class.
Who hosts it?
Usually Vercel or a server you already own. Accounts are created in your name, so moving later does not require our permission.
How much can we change later?
Copy and content without a developer. Structure and data model with one — which is why the model is documented, and why we do not lock it behind an interface only we can operate.
Start a project
Want this scoped for your business?
Send the brief. It comes back as a written scope and a fixed quote before anything is built.