01
Terms in writing
Support levels, response times and update schedules are written into your agreement before go-live.
Company
A Riyadh team that designs, builds, hosts and supports business software.
MUZN IT builds ready-made products and custom software for companies in Saudi Arabia, in Arabic and English, and provides the IT services around them. One team takes a project from scoping to support.
What we do
Three lines of work, one team.
Products, custom development and IT services can be taken separately or in one written proposal.
Products
Ready-made business software for finance, procurement, HR, catering and laundry operations, set up for your company as your own deployment.
See the productsCustom development
Business systems, portals, web and mobile apps, assistants and integrations, built around your process and delivered in milestones.
How a build runsIT services
Company set-up support, infrastructure and networking, security assessment, hosting, managed support and hardware supply and installation.
See the services How an engagement runs
Four stages, each ending in something you can check.
The stages are the same for a product deployment and a custom build. What differs is how much is designed and how much is configured.
-
Discover
Workshops with the people who will use the system. We map the process as it really runs, not as the organisation chart says it does.
You receiveScope and fit-gap document -
Design
Screens and flows in Arabic and English, reviewed with your team before any build starts.
You receiveClickable prototype -
Build
Delivered in milestones. Each one ends in software your team can test with real cases.
You receiveWorking releases -
Run
Go-live, training, hosting and support by the team that built it.
You receiveSupport agreement
How support works
Support terms are written into the agreement.
Support comes from the team that built the system, so a question about why something works the way it does goes to someone who knows.
02
Named channels
You report issues by email or WhatsApp. The channels and the working week, Sunday to Thursday, are stated in the agreement.
03
Arabic or English
You choose the language you work with us in, and the team answers in it.
04
Updates on a schedule
Updates are planned with you rather than pushed unannounced, and the schedule is part of the agreement.
How we work
Seven working practices.
Each of these can be checked in a proposal or in a project.
-
A written proposal before any work
Itemised scope, milestones, timeline and support terms. Nothing is charged until you approve it.
-
One team from scoping to support
The people who scope your project build it and support it. There is no hand-off to a different company.
-
A deployment of your own
Each client's system runs separately, with its own users and data, not as an account in a shared system.
-
Arabic and English from the first screen
Right-to-left layouts and bilingual documents are designed in, not added at the end.
-
You test with your own data
Milestones end in software your team can try with real cases before the next stage begins.
-
Terms are written down
Hosting location, backups, support, update schedule and ownership are in the agreement, not in conversation.
-
Samples are labelled
Screens on this site show sample data and sample names, and say so.
Where we are
Riyadh, serving the Kingdom.
We work with companies across Saudi Arabia from our Riyadh base.
- Location
- Riyadh, Kingdom of Saudi Arabia
- Working languages
- Arabic and English
- Working week
- Sunday to Thursday
Contact
Reach us directly.
Tell us what you run today. A consultant replies with next steps and a time for a scoping session.
- WhatsApp and phone
- +966 53 466 5977
- Sales and proposals
- sales@muznit.com
- Support and security reports
- support@muznit.com
Read next
More about how we work.
Tell us what you are running today and where you want to be.
A consultant from our Riyadh team replies with next steps. A written, itemised proposal follows before any work starts.