An Amman software company building Arabic-first operating systems for Jordanian businesses
An Amman software company building Arabic-first operating systems for Jordanian businesses. Software development company in Amman, Jordan. Jordan is the only market where BarmajTek operates from its own location. The team is in Amman, contracting is in Jordanian dinars, and meetings happen in person when that is the right format rather than only on a screen. In practice this means a discovery workshop can be held at the customer’s premises and workflow review can happen in front of the staff who will actually use the system. The operational difference is that wrong assumptions surface in week one instead of month three. Work starts from a specific operating decision: how an appointment gets booked, how an invoice gets issued, how a manager knows the day went as intended. We then separate engineering work from items needing accounting or legal review before price or schedule is fixed.
Team based in Amman with in-person meetings available.
Commercial currency
Proposals and contracts in Jordanian dinars.
National invoicing
We build integrations with JoFotara, operated by the Income and Sales Tax Department.
01
JoFotara national e-invoicing
The Income and Sales Tax Department operates JoFotara on a clearance model: an invoice is submitted and validated before it reaches the customer, returning a unique identifier and QR code that must appear on the final document. This changes point-of-sale design itself, because the receipt is no longer printed the instant a button is pressed but after the system responds. We design the path to handle connectivity loss, rejection, retry, cancellation, and daily reconciliation, because what usually breaks in an integration is not the happy path but what happens when the system does not answer. BarmajTek claims no official accreditation from the Department: it publishes no approved-vendor list, and what we provide is engineering work against the system’s published interfaces.
02
Personal data protection
Personal Data Protection Law No. 24 of 2023 is in force, and the Ministry of Digital Economy and Entrepreneurship states it applies to processing even where data was collected before enforcement, with a twelve-month alignment period. Existing systems are therefore in scope, not exempt. Discovery records data categories, hosting location, who has access, retention, deletion, and export, then turns these into testable controls inside the system such as role permissions and access logging. Legal conclusions, appointing a data protection officer, and decisions about transfers outside Jordan remain the customer’s responsibility with qualified counsel; this page does not replace legal advice.
03
Why Arabic-first systems
Most systems available to the Jordanian market were built in English and translated afterwards, and the result shows in details anyone who has used them recognises: partially mirrored layouts, numbers that flip inside tables, missing Hijri dates, name fields too short for three- and four-part Arabic names, and search that cannot handle hamza and taa marbuta variation. We build the Arabic interface as the original rather than the second copy, so page direction, column order, printing, and reports are correct from the first release, with a complete English version for those who need it. This is not an aesthetic preference: it reduces data-entry errors and training time for reception and accounting staff.
04
Sectors we know closely
Our products did not come from market research but from operating problems that recur in Jordan: the clinic losing appointments between a paper book and WhatsApp, the restaurant reprinting menus whenever a price changes, the car rental office discovering a vehicle licence expired too late, the gym that only learns a membership lapsed when the member arrives at the door. Clinic Tek is available today; the remaining products sit at stages stated plainly on each product page without overstatement. Where no existing product fits, we build a custom system using the same method rather than pushing the customer toward something that does not serve them.
05
How a project starts and ships
Work begins with a discovery meeting that can be held at the customer’s premises, in Amman or beyond. It produces a written scope stating explicitly what is inside the project and what is not, because most disputes come from a clause never written down. Next comes a testable workflow prototype before the full system is written, then short releases the customer reviews and their staff try. Acceptance criteria are written in Arabic and English and the launch approver is named. Code ownership, hosting accounts, the domain, and app store accounts stay in the customer’s name with a complete data-export path, because the customer’s ability to leave us is a contract term rather than an added service.
Before pricing
Inputs the customer and team must evidence
01Confirm the tax number and JoFotara registration status before designing the invoicing path.
02Classify personal data and define retention and deletion under Law 24 of 2023.
03Name the staff who will use the system daily and include them in prototype review.
04Agree Arabic and English acceptance criteria and name the launch approver.
05Register code, hosting, domain, and app store ownership in the customer’s name.
Scope examples
Work to evaluate for Jordan
These are discovery examples, not claims of delivered market projects or customers.
We are based in Amman with the team resident in Jordan, so in-person meetings and on-site discovery workshops are possible. Jordan is the only market where we work from our own location; other markets are served remotely.
Yes. We build against the system’s published interfaces and design rejection, retry, and reconciliation paths. We do not claim official accreditation from the Income and Sales Tax Department, which publishes no approved-vendor list, and registering the business and obtaining credentials remains the customer’s responsibility through official channels.
Jordanian dinars for local customers, with the proposal stating what is in scope, what is out, and payment terms before work begins.
Both. If one of our products covers the case we start there to save time and cost; if it does not fit we build a custom system using the same method. We explain the cost and timeline difference before the decision rather than pushing you toward an option that does not serve you.
There is no fixed price for an app, and any figure given before the users, workflows, and integrations are known is a guess. Cost in Jordan depends on how many operating journeys exist, the user types, whether the app must connect to national invoicing, a payment gateway, or point-of-sale hardware, and whether both iOS and Android are required or a web interface is enough. We issue a proposal in Jordanian dinars after a discovery workshop that fixes scope in writing, separating what the price covers from items billed separately such as store fees, hosting, and support. See our Jordan software cost guide for how estimates are broken down before requesting a proposal.
It depends on whether you need a brochure website or a system that runs daily operations. A brochure site is bounded and predictable; an admin system is priced by the number of roles and permissions, how much data must migrate from the old system, the reporting required, and the post-launch support level. We decline to quote before discovery because a low headline number usually hides items that reappear later as extras. Ask instead for a written scope that states what is excluded, then compare proposals on scope rather than on the final figure alone.
We publish an Arabic guide on correcting and cancelling electronic invoices in Jordan, plus a broader national e-invoicing guide. Those pages are educational and do not replace the JoFotara portal or a tax adviser.
Personal Data Protection Law No. 24 of 2023 requires classification, retention, and deletion decisions. Discovery records data types, hosting, and subprocessors so the customer can review the map with qualified counsel. A marketing page is not a compliance ruling.
Turn Jordan requirements into testable scope
Send the Jordan entity, users, data, providers, and timing. We will separate buildable work from external legal or provider prerequisites.
