Schema
The objects the firm already talks in, with the field names it already uses. Nothing is renamed to suit the software.
Customizable
CRM.
Every firm is told the same thing: take the system the vendor built for somebody else and change how you work to suit it. Zyrn builds the other way round — your objects, your vocabulary, your rules — and hands over the source, the data and the hosting in your name.
00 — AS FOUND
000%
- 00As found— RECORDS · UNLINKED
- 01NamedYOUR REFS · NOTHING RE-ENTERED
- 02The schema20 TYPES · 130 FIELDS
- 03The pipeline03 STAGES · 07-DAY FLAG
- 04The ledgerEVERY CHANGE, ATTRIBUTED
- 05Handed overSOURCE · DATA · HOSTING
Forty-eight records adrift, which is how they actually live before there is a system: some in a spreadsheet, some in a notebook, some in whoever answered the phone. Everything after this is the same forty-eight points of light — none will be added, none lost.
What it covers
Six modules. The schema is agreed before a screen is drawn.
Pipeline
Stages that match how the desk really works, and a stall rule counted in working days rather than calendar ones.
Ledger
Every change attributed and timestamped, because the question that gets asked is who changed it, not whether it changed.
Roles
Who may see, who may edit, and who may delete — enforced at the data rather than by hiding a button.
Feed
A one-way sync from whatever is already the source of truth, with archiving instead of deletion when a record leaves it.
Handover
The source, the data and the hosting, in the firm’s name. There is no seat count and nothing to renew.
One is already running
Lumina Desk, built for a brokerage in Amman. Counted out of the repository, not estimated.
- BUILD 81 source files, 8,996 lines. 16 screens, 09 action modules, 07 endpoints.
- SCHEMA 20 declared types carrying 130 typed fields. Every one of them argued for before it was added.
- DEPENDENCIES 08 at runtime. A dependency is a decision somebody else gets to change later.
- SEATS Not counted, because they are not charged for. The bill does not move when the desk grows.
How it runs
Three phases, the same three every line runs. Measured at each one.
P.01
Model
Two to three weeks. The objects, the vocabulary and the rules, written down and agreed before a screen exists.
P.02
Build
One quarter. The desk runs against real records from the first week, because a system tested on invented data is tested on nothing.
P.03
Hand over
The repository, the database and the hosting move into the firm’s accounts. Changes ship from inside the firm after that.
What changes
Signals the engagement watches, and the direction they are expected to move.
- SOURCE OF TRUTH One system, rather than a system and the spreadsheet everybody actually uses.
- COST Flat. It stops tracking headcount, which is the line item that made the old one hurt.
- CHANGE A new field is a commit, not a support ticket and a quarter of waiting.
- EXIT There is nothing to migrate off. The source and the data were always the firm’s.
Shape the desk
What you trade, where truth lives today, who works in it. The schema recomposes in your own vocabulary — then send exactly that.
Built to the firm.
Not rented to it.
The engagement closes when the repository is in your account and the team is shipping from it.