Eluno
Business software for small enterprises
Business software for a small enterprise that had outgrown notebooks and WhatsApp but was never going to buy an ERP.
Development
Operational systems where the difficult parts are the ones nobody demos: tenant isolation, approval chains that hold under delegation, stock that cannot be double-promised, and a ledger that still reconciles after a partial payment.
Foundations
They are unglamorous, and they are the reason a system can absorb a new requirement in month eight without a rewrite.
Entities, states and the transitions between them are designed before any screen exists. Most business software that becomes unmaintainable got the data model wrong in week one and spent the next year working around it.
Permissions, approval thresholds and period locks are enforced on the write path. Anything enforced only in the interface is a suggestion.
Ledgers, movements and audit entries are added, never edited. A balance you cannot reconstruct is a balance you cannot defend in a dispute.
Amounts are held in minor units. Proration, percentage escalations and tax all produce repeating decimals, and floating-point drift in a finance system becomes a customer-facing error.
Stack
Deliberately boring choices. A business system is a long-lived asset, and novelty is a cost its owner pays for years.
Software engagement
Describe the process, who touches it and where it currently breaks. You will get a data model sketch, a technical approach and a timeline before any commitment.