What this offering is
We design, own and operate our own software-as-a-service platforms. Each one is a working product with its own release cycle, and the version we show you in a demonstration is the version we maintain and release. You subscribe to it under an order form, and the configuration work starts from a system that is already running.
Ownership matters in practice. Because we write the code, a request to change something goes to the people who maintain the product, not to a vendor we resell. A subscription covers configuration, data migration and integration of a product we already run, and anything that changes how the product itself behaves is a Custom Technology engagement.
The platforms in detail
Seven platforms make up the portfolio, covering healthcare, business, travel, transportation, logistics and retail. BizzOS, our AI business operating system, runs a whole business in one place. The other six are set out below. None is a rebadged version of another: each has its own data model and interface, and all are available separately, so you subscribe to what you need and leave the rest.
- MedLocal, a healthcare discovery platform connecting patients with the providers treating them
- TMS, a travel management system for bookings, itineraries and the records behind them
- FMS, a fleet management system for tracking vehicles and how they are deployed
- SPE, or Smart POS Enterprise, a point of sale platform for retail and hospitality
- 3alTari2, a transportation and delivery marketplace for moving goods and people
- PUSH, a gym and fitness platform for operators and their members
How a rollout runs
The five stages are the ones we use everywhere else, Discover, Design, Build, Launch and Scale, but nothing here starts from zero. The product exists, so the questions are narrower: how your process maps onto the platform, which roles and permissions people need, what data comes across from the systems you use now, and what has to connect to what.
Most of the effort goes into migration, integration and getting people onto the system: moving records across without losing history, connecting the platform to what you already run, training the people who will use it daily and agreeing a cutover date. After that we review how the platform is used and adjust the configuration as your business changes and new releases arrive.
What a subscription includes
A subscription covers access to the platform for the agreed users, onboarding and configuration, training for the people who will run it, and the support and maintenance set out in the order form. Product documentation comes with it. Scope, user numbers and support arrangements are written into that document rather than left to assumption.
The data stays yours. We host and process it to run the service, acting as a processor in accordance with our Privacy Policy and any data processing agreement in place between us, while you remain the controller. The platforms are built to support your own regulatory obligations, which remain yours to meet.
Seeing the product first
It starts with a conversation and a demonstration of the platform you are interested in. We would rather show you the product and hear where it does not fit than send a deck. If the fit is wrong, saying so early costs both sides less than finding out during migration.
After that comes a Discover session covering process, data and the systems already in place, and from it a written scope and an order form. Nothing is committed until that document is agreed. To begin, write to hello@jebrex.com with the platform of interest, the industry and roughly how many people would use it. Jebrex Tech, S.L. has its registered office in Barcelona, Spain, and a second location in Beirut, Lebanon.