What this covers
Custom technology is software we design and build around one organisation's operations, for cases where a standard product does not fit. It starts from how the work is done now: the steps people follow, the records they keep and the systems already in use. It can run on its own or extend software you already have.
The boundary is the fit. Custom technology is software shaped to one organisation's existing process, and that includes extensions to our own products. A whole multi-user system built from the data model up, with its own tenants, accounts and roles, is a digital platform, and that work is described on the Digital Platforms page.
Where it applies
The work below describes the kinds of system we build for an existing process. One programme can combine several of them, for example a new internal tool that also has to migrate records out of an older system. Which of these apply to your organisation is settled in Discover, not assumed at the start.
- Internal operating systems: workflow, approvals, scheduling, inventory and reporting built around one organisation's process
- Customer-facing portals that expose records already held in the systems you run today, for booking, ordering, membership and accounts
- Integration and migration: connecting existing software, moving records off spreadsheets, keeping both consistent
- Replacing a spreadsheet or an unsupported legacy tool that a working process still depends on
- Extensions to BizzOS, MedLocal, TMS, FMS, SPE, 3alTari2 or PUSH beyond a standard deployment
- Data and reporting layers: one operational model, with dashboards and exports that reconcile with source systems
How the work runs
The stages are Discover, Design, Build, Launch and Scale. Each increment produces software you can run and review, and priorities for the next increment can be reset in light of it. Security is built in during the work: separated environments, reviewed code, and audit logging over records that exist nowhere else. The regulatory obligations that apply to your sector are identified during Discover and the system is built to support them, not to certify anything on your behalf.
What is delivered
Each engagement produces working software, the deployment configuration needed to run it, and documentation covering the architecture, the data model and day-to-day administration. Handover includes training for the people who will operate the system. From there your own team can run it, or support and further development can continue under a separate agreement.
What is delivered, including whether source code transfers to you, is listed in the statement of work rather than assumed, and ownership of the deliverables is set there. Pre-existing JEBREX frameworks, libraries and tools stay with us and are licensed to you as incorporated in the deliverables. Your data remains yours, and where personal data is involved we act as a processor under your instructions, as described in the Privacy Policy.
How an engagement starts
An engagement starts with a message to hello@jebrex.com setting out the process you want to change, the systems it currently touches and the people who use them. The first conversation is a Discover session. It can end with the conclusion that custom software is not the right answer, and where that is the case we say so rather than scoping a build around it.
What follows Discover is a written scope: the problem, the proposed solution, the phases of work, what each phase delivers and what it depends on from your side. Nothing is built before that document is agreed. Work is then contracted under a statement of work, which is where the commercial terms are set. Jebrex Tech, S.L. has a registered office in Barcelona, Spain, and a second location in Beirut, Lebanon.