AI & Automation
Custom internal tools in Qatar
Small custom software for the job no off-the-shelf product quite fits.
- Villa facade, Al WaabQAR 48,000Syrian stone · 40 m²
- Majlis wall, LusailQAR 12,500Jordanian stone · 12 m²
- Shop front, MsheirebQAR 22,000Syrian stone · 18 m²
Stone in stock
Syrian stone120 m²
Jordanian stone45 m²
7
projects shipped across Qatar and the GCC
Design, search visibility and pipeline — built together, in English and Arabic.
Definition
What an internal tool is
An internal tool is a small piece of software for one job your team does repeatedly: a jobs board, a stock check, an approval queue, a dashboard of the numbers you track. Only your staff sign in, from a laptop in the office or a phone on site.
It is not an ERP, and not a spreadsheet with clever formulas: it has rules the data must follow, a history of changes, and screens that show each role only its part. Unlike workflow automation, which runs with no screen, a tool is where people work.
Why it matters
Why the spreadsheet eventually costs more
Most teams run a critical process in a shared spreadsheet that one person understands. It works until two people edit the same row, or that person leaves; in the demo above, nobody can say who changed the price. A product off the shelf suits standard work, but for your own process it often fits half and charges every user every year.
Rules that hold
A job cannot be marked done twice and stock cannot go below zero, whoever is typing.
Each role sees its part
The site team's accounts never receive prices, even by accident.
A name on every change
Every edit is recorded with who made it and when, so 'who changed the price?' has an answer.
Built for mixed teams on the move
Office staff in Arabic, site staff in English, on a phone first, because much of the work happens away from a desk.
The decision
Spreadsheet, product or custom tool: how to choose
If only one of the warning signs fits, a better spreadsheet or a product setting is probably cheaper.
Stay with the spreadsheet
One or two editors, nobody needs to see less, mistakes are cheap. Tidy it: a tab per purpose, locked formulas, a named owner.
Buy a product
Standard work such as accounting, payroll, leave or a general CRM. If it fits most of your process and the rest is a setting, buy it.
Build a tool
Your own process, with roles that must see different things, rules that must always hold, and a need to know who changed what.
The warning signs
Workarounds in the product you tried, seats paid for people who check one screen, a spreadsheet owner who cannot take leave.
How we build
Rules in the database, access by role
Ottora Studio's system is a full operations system, not a small tool, and none of it is AI, but it shows how we build.
- Rules live in the databaseA database constraint refuses overlapping equipment, so the system accepts zero double-bookings.
- Unfinished actions have an endingAn unpaid booking releases its own slot after 15 minutes, so an abandoned checkout never holds the calendar.
- Approvals chase themselvesA 9-stage content pipeline whose client approval gates chase themselves after twenty-four hours.
- Access decided by role16 modules, each open only to its roles. An admin without finance access gets 0 rows from the ledger, even querying directly.
How it runs
From the spreadsheet you have to a tool your team uses
What we need from you: an afternoon with the people who do the job, the spreadsheet as it really is, and one owner.
Watch the job
The spreadsheet, the WhatsApp group and the paper, plus the rules everyone follows without saying them.
Scope one job
Screens, who sees what, the rules that always hold, and the systems it connects to. Everything else waits.
Build in small steps
You try each screen as it is built, on your own phone, with your own data.
Import and check
The spreadsheet comes in, and mismatches such as stock that does not add up are resolved with you, not silently corrected.
Switch over
The team moves on one day and the old spreadsheet becomes read-only, so there is one place for the truth.
Hand over
Training per role, a short written guide, and the code, data and hosting in your company's name.
An example
An example: jobs and stone stock at a cladding firm
An example, the same cladding firm as the demo above, not a client.
The shared spreadsheet
- Two people, one rowMariam and Yousef edit row 3 at the same time, and one change is lost.
- Stock from memoryLast updated three weeks ago, so a job starts and the Syrian stone runs short.
- Prices for everyoneThe site team sees every price, and nobody knows who changed one.
The tool
- One record per jobThere is no shared row to collide on.
- Stock that moves with the workWhen Yousef marks a job done, its square metres of stone leave stock, with his name and the time.
- Prices by roleThe office sees prices; the database never sends them to site accounts.
What Internal tools includes with us
Scoped to one job with the people who do it, written down before building
A screen per role, such as office, site or finance, with what each may see
Access enforced in the database, not by hiding buttons
Rules that matter written as database constraints, so bad data is refused
A history on every record: who changed what, and when
Built for a phone on site and for the office, in Arabic and English
Your current spreadsheet imported and checked, so nothing is retyped
Training by role, a written guide, and the code and data in your company's name
How we build
Built to the same six standards
Rules that matter live in the database, and tests run before every release. Pages are measured on a mid-range phone, access is decided by role in the database, and Arabic is designed right to left from the first layout. Tracking waits for consent, and the domain, hosting, code and data are in your name.
Read our standards, with the project that shows each one.
Common questions
Isn't custom software expensive?
A tool for one job is usually smaller than people expect, and often costs less than a few years of per-user licences for a product that only half fits. It is quoted after a short call. What sets the scope: the roles and screens, the rules that must always hold, the systems it connects to, and how messy the data to import is.
What does it cost to run?
Little, and it sits on your own accounts: mainly the hosting plan and the database, both in your company's name. There are no per-user licences, so adding a site supervisor costs nothing extra. If the tool uses an AI provider for a reading step, those usage fees are billed to your account too. We list them before you commit.
What if our process changes?
Then the tool changes. That is the advantage of it being yours: no waiting for a vendor's roadmap, no higher plan to unlock a field. A new status or column is quick. Changing a rule the database enforces needs more care, because existing records must follow it too, so it is tested first. Keep a short list of what the team asks for.
Who owns the tool and the data?
You do. The code, the database and the hosting are in your company's name, as is every account the tool depends on. It is built with widely used technology, such as Next.js and Postgres, so another developer could read and extend it. At handover you get a written guide, and if you stop working with us, the tool keeps running on your plan.
Can it connect to our accounting system or CRM?
Usually, where the other system offers an API, a documented way for software to read and write its data. A finished job can raise an invoice, a new customer can appear in your CRM. Where there is no API, a scheduled file export is the fallback. Connections are settled at scoping, because they often decide more of the work than the screens do.
Will my team actually use it?
If it is quicker than what they do now, and only then. So it is built with the people who do the job, tried on their own phones while it is built, and switched on with the old spreadsheet made read-only. A tool that runs beside the spreadsheet loses, because people go back to what they know.
Where is the AI in an internal tool?
Often nowhere, and that is fine. Internal tools sit under AI & Automation because they are usually built alongside automations and assistants. AI earns a place when the tool must read something unstructured, such as a supplier's quote. Then its output is shown to a person to confirm, never written straight into the records.
More in AI & Automation
Every part of AI & Automation works better alongside the others — here's the rest of it.
Ready to hand the busywork over?
15 minutes · A clear next step · No pressure