This system ran a business before it became a product.

Most management systems are built outside-in: somebody imagines how a business works, then writes software to match the imagination. DecaLeap was built inside-out. It was written to solve problems that were actually on the desk — an order that went out at the wrong price, a warehouse that could not see priority, commissions calculated in a spreadsheet that started an argument with a rep, and a month that closed on two different numbers.

When a system is built that way, two things happen. First, it has no screens that look good in a deck and that nobody ever opens. Second, its structure reflects a real business — a customer who is also a distributor’s end customer, an order that ships in three partial despatches, and a person who is both a sales rep and a contractor submitting an invoice. These are not edge cases. This is a Tuesday.

The name came from that gap. Deca — ten. Leap — the jump. Not another percentage point of improvement on a manual process, but the move from running a business in files to running it in one system.

Security is not a paid add-on.

This system holds your customer list, the prices you agreed and what your team is paid. These protections are in every account and every package — no surcharge, and no more expensive tier you have to buy to reach them.

• Two-factor authentication from an authenticator app, with ten single-use recovery codes for the phone that gets lost. A company can require it of everyone.
• A correct password is half an authentication. Between the password and the code there is no session — only a short-lived, single-use challenge that is worthless anywhere else.
• We do not store passwords — only a scrypt hash with a per-user salt.
• A separate database and a separate process per customer, not a shared schema with a tenant column. Backup, restore and deletion are operations on your data alone.
• Access is granted per employee and per module — and a module you were not granted does not merely vanish from the menu: the API refuses it. A warehouse operator does not see commissions; a rep does not see payroll.
• An audit trail over sensitive actions and sign-in attempts — who did what, and when.
• Daily encrypted backups, copied off the server — and a full export to Excel is open to you at any time.

The two-factor design follows the Israeli Tax Authority’s information-security appendix (§17) — the requirement that applies to software vendors under the “Israel Invoices” programme.