One AI system for your whole company. Built around how you already work.
OSwright builds each company its own operating system: every area on one record, AI working inside every area, and an AI night shift that rebuilds the system from what your people report each day. We know it works because our own business runs on it.
Your company, drawn as one system. AI in every room.
Partners, selling, buying, stock, delivery, money, people, comms and advice are rooms around one record. People and AI read and write the same record, each within their role, so nothing is copied between apps and nothing waits for an export.
Scroll the drawing sideways to see all of it.
- 1A WhatsApp chat becomes a lead, with the company it came from.
- 2A quote's cost changes after approval, and it asks for approval again.
- 3Someone leaves, and their email, door, Wi‑Fi and phone go in one press.
- 4Every change, by a person or by AI, goes on the audit log.
Most business software is written by software companies, and asks the business to change how it works.
We're a business that built its own software, with AI, around how we work. Now we build yours.
Modo OS has run Modo's five companies, in the UAE and India, since 1 June 2026.
AI does more than answer questions here. It runs, writes and checks the system.
AI rebuilds it every night
Your people report a problem or an idea in a sentence. Overnight, AI writes the change, tests it, checks every screen and ships it by morning.
How the night shift worksAI reads every area, every hour
Thirteen advisors watch their areas, one reads across all of them, and each person starts the day with a briefing of what needs them.
AI in every layerAI writes the first draft
Quotes, follow-ups, reorders, renewals, letters and meeting actions arrive drafted. A person reads and sends.
What it draftsAI that can use the whole company
1,737 procedures your AI assistant can call, each one checked against the role of the person asking.
Talk to your companyBuilt by a business that runs on it.
At Modo, read from Modo OS on 21 Oct 2026.
The Modo OS storyHistory repeats.
In 2020 a smart home that didn't work became Modo: Hasaan Kadli fixed his own house, then other people's. In 2026 software that didn't fit the business became Modo OS. Clients and partners saw it at work and asked for one of their own.
So the way Modo builds its own system became a business of its own: OSwright.
A whole company, or the one piece it needs.
A distributor and installer
Modo's five companies: partners and tiered prices, quotes from live stock, projects, crews, stores, people and comms on one record, with AI in each.
A research lab's stores
Goods in with QC deadlines, smart cabinets that log who took what, loans with reminders, maintenance, and the material list kept in step with the company's ERP.
A value-added distributor
Daily supplier offers from email, WhatsApp and WeChat, compared by AI against stock, sales speed, incoming and reserved stock and price history.
It starts with two hours.
Scope
We go through your company area by area. Your answers are the scope.
The number
Build, run, and cloud and AI, priced area by area. The scope is the number.
Build and move in
In your cloud, in the order you pick. Nothing lands until a dry run is checked. Then the night shift starts on your reports.
Every area of the company on one record. With AI working in each one.
This is what an OSwright system can hold, area by area, and what AI does inside each. Every line carries the mark of what stands behind it, so you can tell what runs a company today from what is still on the drawing board.
A whole company on one system
Partners
Applications from a link, tiered prices per brand, credit terms and advance balances, a portal where a dealer sees their orders and statement, agreements that remind before they expire, and brand kits that stay current for every dealer.
Selling
Leads from WhatsApp, email, calls and the website, merged when they repeat, one lead per company by email domain. Quotes pull live stock and partner prices, ask for approval when a discount or margin crosses a line, and again if a cost changes. Prices by payment term: Scoped
Buying
Purchase orders with approvals, landed cost spread over the lines, supplier invoices matched to what was ordered and received, and cost history with the reason for each change. Daily supplier offers compared like a price tracker: Scoped
Stock
Several warehouses and companies, rack and bin locations, serials scanned in and out, counts, transfers, reorder alerts, and a camera wall beside the stock screens.
Delivery and returns
Packing lists and delivery notes signed from a link, crews scheduled with their day rates and budgets, returns with root cause, and service tickets after installation. Export papers for many countries: Scoped
Money
What each partner owes in every currency, payables by age, expenses and petty cash, linked to the accounting system already in place, with invoices drafted from sales orders.
People
Attendance from the office doors, leave with approvals, documents that warn before they expire, payroll with bank and WPS files, reviews, KPIs per role, and joining or leaving in one press: email, door, Wi‑Fi, phone extension and website profile together.
Comms
Email tied to the partner or deal, WhatsApp numbers and groups in one inbox, calls recorded and transcribed, meetings with summaries and action items, and a team messenger where any message becomes a task.
Advice
Advisors read each area every hour, one reads across all of them, and each person gets a morning briefing of what needs them.
Devices
Company phones and laptops on iOS, macOS, Windows and Android, enrolled and managed from the same system: lock, wipe, locate, policies, apps pushed to every phone.
One piece, where that is what a company needs
A lab's inventory
Goods in with QC deadlines and escalation, labels, put-away, smart cabinets that log who took what and alarm on an open door, loans with reminders and one extension, maintenance and RMAs, reorders, and the material list kept in step with the existing ERP. Computer vision at goods in and RFID: Scoped
HR on its own
Leave, documents that warn before they expire, payroll files, reviews and KPIs, and one-press joining and leaving. Running at Modo; it can stand alone.
Tasks and notifications
What needs you, updates and digests, and a task from any message, call or meeting. Running at Modo; it can stand alone.
Built on what you already have
OSwright connects to the hardware and services a company already pays for, so the system can act on them, and AI can too.
UniFi
Access for doors and attendance, Talk for calls, Protect for cameras, Identity for Wi‑Fi. Joining and leaving reach all four in one press.
Google Workspace
Accounts and email. Mail is tied to the partner, lead or deal it belongs to. Microsoft 365: not built yet.
The accounting system you keep
Zoho Books today, with invoices drafted from sales orders and stock valuation pushed across. SAP, Business Central and Odoo are linked as part of a scope.
Online stores
Shopify, with stock kept in step so a store never sells what the warehouse doesn't have.
Every work number and group in one inbox, linked as a device so groups work. The official API is there if you prefer it.
The AI assistant your team already uses
Connected to the system with each person's own permissions, alongside the chat built into the system.
Built for the people who use it all day
Keyboard first
Every list opens a record; J and K move, F widens, a number key jumps to a tab, and one shortcut finds anything. The people who quote all day asked for it.
View as any role
See exactly what a sales executive, an accountant or a warehouse lead sees, before you hand it over.
Your names, your logo
The system carries your company's name, logo and colours. It is your operating system; OSwright is a line on the sign-in page.
AI in every layer of the company. Building it, running it, advising on it.
Most software adds a chat box to an old product. An OSwright system is built with AI, rebuilt by AI every night, and has AI working inside every area, under the same roles and the same audit log as the people it works for.
The stack
AI that builds the system
Every night an AI dev team works through what your people reported that day: it writes the changes, tests the code, opens and checks every screen, audits itself and ships by morning. When your process changes on Tuesday, the system follows by Wednesday.
At Modo, read from Modo OS on 21 Oct 2026.
How the night shift worksAI that advises
An advisor per area, every hour
Thirteen advisors read selling, buying, stock, money, people and the rest each hour and raise what needs a decision: a lead nobody has touched, stock that will run out, an agreement about to lapse.
One that reads across all of them
The leadership advisor connects the areas: the margin on a quote against the cost history, a team that is overloaded, someone who regularly finishes after 9 pm.
A briefing every morning
Each person starts the day with what needs them, one line each, and the decisions arrive prepared, with the facts behind them.
AI that drafts. People decide.
AI writes the first version of the work that eats a day. Nothing goes out until a person has read it.
Quotes
From live stock, the partner's price tier and the last price you gave this customer, with the margin shown to whoever approves it.
Follow-ups
An update to every open lead, written from the past week's emails, calls and WhatsApp messages with them.
Reorders
Drafted from three months of sales, what is incoming and what is reserved for customers.
Letters and reviews
An increment letter and the salary record from the meeting notes; a review compared with the last one.
AI that listens
Calls
Every call on the company phone system is recorded and transcribed inside your own system, then summarised: intent, facts, actions, sentiment. Action items become tasks. Tested in English, Hindi and Malayalam.
Meetings
Transcripts, summaries and action items land on the meeting record and the people in it, with the recording beside them.
WhatsApp and email
A chat with someone new becomes a lead with the company it came from. Every email from one company lands on one lead, whoever sent it.
Talk to your company
Connect the AI assistant your team already uses, or use the chat built into the system. Ask in a sentence; it calls the system's procedures as the person asking, and answers from the record.
Example questions. Names are made up.
AI that remembers, in your system
What the system has learned about how your company works lives inside the system, not in an AI vendor's memory: the processes, the decisions and the lessons that cost time, each versioned so a regression shows up as a change, not as a surprise.
Switch models, keep the memory
Use a different AI tomorrow and it reads the same memory today's did.
Every new model is audited
When a new model arrives, the screens and the code are audited with it, so a better model shows up as better work.
The handbook writes itself
Guides for every process are rewritten in plain language whenever a process changes, so a new joiner learns today's way.
Your models, your choice
Frontier or local, per surface
Choose frontier models where they earn their cost, and local open models in your own cloud everywhere else. Each surface can be set on its own.
Data leaves only where you send it
Speech-to-text runs locally. Data goes to an outside model only for the surfaces you point at one, under your own account and its settings.
One account, limits per person
The whole team can use the built-in chat on one backend account, with limits on how much each person uses.
AI under the same rules as people
Roles decide
Ask for the P&L without the right and the answer is no, whether you ask a screen or an assistant.
Every AI call is logged
Who asked, which procedure ran, what changed. 798,850 entries at Modo since 29 May 2026.
Dry run first
A bulk change by AI shows what would be added, changed or skipped. A person checks it, then one click.
The owner's passkey
Changes that touch money, permissions, sign-in or data wait for a fingerprint or Face ID from the person who owns the system.
Every night, an AI dev team rebuilds your system from what your people reported that day.
Software usually freezes the day it is delivered, and every change after that is a request, a quote and a wait. An OSwright system keeps being written. It can do whatever you want, as long as you can put it into words.
One night
- 18:00Anyone presses Send feedback and writes a sentence: a bug, an idea, a process that changed.
- 22:00AI triages the day's reports and writes the changes.
- 01:00It tests the code and the data.
- 03:00It opens every screen it touched and looks at it, on a desktop and a phone.
- 05:00It audits and hardens itself, and rewrites the guides.
- 07:00Shipped. The person who asked is told.
Times are illustrative; the run starts after the working day and ships before the next one.
From a sentence to a shipped change
Quotes on 90-day terms should go to the GM for approval, and show the price for those terms.
ExampleBuilt, tested, screens checked, audited. The approval rule is live, the handbook page for quotes is updated, and the sender has a note saying what changed.
ExampleThree checks before anything ships
The code and the data
Types, tests and the database rules, so a change can't break what it doesn't touch.
Every screen
AI renders the pages it changed and looks at them, at desktop and phone widths, light and dark, before anyone else does.
The AI tool layer
It exercises the same procedures your assistant uses, so a change works for AI as well as for the people on the screens.
Two kinds of change
Safe changes
A screen, a button, a report, a new field, a fix. They ship on their own and show up in the change log in plain language.
Sensitive changes
Anything touching money, permissions, sign-in or the shape of the data waits in a queue until the owner approves it with a fingerprint or Face ID.
Every build is numbered and kept. You can go back to an earlier one, unless a change has reshaped the data; those are exactly the changes that wait for the passkey.
What we do, and what AI does
“What we do as people is map everything out. What the AI does is build it. If the mapping isn't there, that is where AI-built apps fail.”
Hasaan Kadli, Founder and CEO, ModoAt Modo, read from Modo OS on 21 Oct 2026.
A business that built its own software. Twice, it turned a problem into a company.
Modo OS has run Modo since 1 June 2026: five companies in the UAE and India, smart-home distribution and building-automation projects, one record, AI in every area. It is the proof behind everything on this site.
History repeats
A smart home that didn't work
The keypads in Hasaan Kadli's room didn't work, and the installers had stopped turning up. To switch on a light he had to open the panel on each floor. So he took an electronics course, set up a soldering bench, learned the system and fixed his own house. Then other people's. That became Modo, which designs smart homes and buildings backwards from what each client is trying to achieve.
Software that didn't fit the business
Modo ran on a stack of online subscriptions that didn't talk to each other, each asking Modo to work its way. So he rethought it again, and built one system for the whole company with AI. Clients and partners saw it at work and asked for one of their own. That became OSwright.
“We're not a software company trying to sell this to a business. We're a business that built this software for itself, and now builds it for others.”
Hasaan Kadli, Founder and CEO, ModoThe build
Modo OS runs on two sites, Dubai and Bangalore, each serving its own region and standing by for the other. Failing over between them takes about 40 seconds, tested on 10 July 2026.
What it replaced
Seven apps retired or retiring: quotes, inventory, device management, email signatures and the website so far, the books and the online stores at year end. About USD 6,000 a year in subscriptions so far, and every one of those tools now works with the others, which none of them did before.
At Modo, as of October 2026.
How the team moved in
Day 35: adoption
The day the first build rolled out, the goal changed from building to adoption. People don't want new tools, so the rule was simple: use this, and nothing else.
A bug bounty
For the first three months, staff earned store vouchers for the problems they found, with a Hall of Fame for the top reporters and the most active. The company found its own bugs, and the system got better fastest then.
Now
About 60% of each person's KPIs are read from the system.
What one person's day looks like
The founder
Opens one page: approvals waiting, the morning briefing, the calendar, who is in the office, and the advisories across every area. Asks the rest in a sentence.
The quoting desk
Builds a quote from the keyboard, from live stock and the partner's price tier; the system asks for approval when a discount crosses a line, and again if the cost changes.
HR
Onboards in one press: email account, door access, Wi‑Fi, phone extension and the website's team page. Documents warn before they expire.
The receptionist
Answers a call; the transcript, the summary and the actions land on the record before the next call.
Your answers are the scope. The scope is the number.
We map your company the way we mapped our own, area by area, with the people who do the work. Then AI builds it, and keeps building it after you move in.
Six steps, each with a sign-off
Scope
Two hours, area by area: what the system does today, what you need, and the questions only you can answer. Bring the people who own each area.
Try it
Your team gets a demo with made-up records, and can view it as any role, to compare it with how they work today.
The number
Build, run, and cloud and AI, priced area by area once the scope is complete.
Agreement
Scope, support terms and dates, in writing.
Build and move in
In your cloud, in the order you pick. Exports from your current systems, a dry run of what would be added, changed or skipped, checked by your team, then one click. Nothing lands until a dry run is checked.
Live
The night shift starts on your own reports. One person at your company owns the system and approves sensitive changes.
How the number is built
No figure is quoted before the scope. The number has three parts, and each new piece of work is priced on its own so any one can be dropped.
Build
The areas that exist, set up with your data and settings; new work priced item by item; moving in.
Run
A support desk on agreed response times, the night shift, and an uptime target.
Cloud and AI
Paid by you to the providers, sized from your volumes, on accounts you hold.
Start small, or start whole
The core first
Change only the layer where your process differs from ours, go live, and gather the next hundred requests from your own people in the first thirty days, tiered into must-have, fix and nice-to-have.
The one piece you need
Inventory for a lab, HR on its own, or tasks and notifications on their own, joined to the rest later on the same record.
Who owns what
You own the system
It runs in your cloud account, under your name. One person at your company approves what changes.
Your people steer it
Anyone can report a problem or an idea in a sentence; the night shift turns reports into changes.
We stand behind it
OSwright maps the work, sets up the build, runs the support desk and keeps the night shift honest.
Your cloud, your keys, your AI. Every action on the record.
A system that rewrites itself every night has to be stricter than one that never changes. These are the rules it runs under.
Where it runs
Your own cloud account
You hold the keys and get the bill. Nothing runs on shared infrastructure with another company.
Two regions
Each serving its own users and standing by for the other, the way Modo OS runs across Dubai and Bangalore.
Backups you choose
Database images, an office NAS, cloud storage; Modo keeps all three. Set them to your policy.
Who can do what
Roles, with exceptions
Every user has a role; a person can be given an exception. Anyone missing a permission can request it from their manager, and the request goes up the chain to whoever can grant it.
The same rules for AI
An assistant acting for a person can do exactly what that person can, and no more. A receptionist's assistant can't read the P&L.
The owner's passkey
Changes to money, permissions, sign-in or the shape of the data wait for a fingerprint or Face ID from the system's owner.
Dry runs
Bulk changes, from an import or from AI, show what they would do before they do it.
Everything on the record
The audit log
Every change and every AI call: who, when, what. Search it, or ask the AI who changed the decimal point on that quote.
The change log
Every night's changes in plain language, numbered by build, with the person who asked for each.
At Modo, read from Modo OS on 21 Oct 2026.
Start with two hours. Area by area.
A scoping session goes through your company one area at a time: what it does today, what it needs, and the questions only you can answer. You leave with a scope; the number follows it.
What to bring
- The tools you use today, and what each one costs you in time.
- The people who own each area, or an hour of each of their time.
- The process that frustrates you most. We start there.
- Where it should run: your cloud provider and region, if you have one.