Kreluna Gestionale
Customers, projects, tasks, and payments brought together in one workspace.
Open and try →If your Rome business manages cases, members or guests with data spread across tools, we start with one specific process. We first assess possible configurations and connections; custom management software needs rules that justify development.
We start with a single process, such as practice deadlines or guest arrivals, and make it trackable and shared.
Our only office is in Montecatini Terme: Kreluna has no office in Rome. Studio meetings are by appointment. Analysis, revisions and delivery can take place online; any other meetings are agreed separately and are not automatically included.
Try the management softwareOpen Kreluna GestionaleOpen the demoThe demos show screens, states and work steps using sample data. They support discussion of the workflow; they do not demonstrate live integrations, successful migrations or the security of a system intended for real data.
Customers, projects, tasks, and payments brought together in one workspace.
Open and try →Appointments and practice workflows organized around day-to-day work.
Open and try →
An example of a complete digital process, from search to action.
Explore the project’s design decisions →Demo concepts designed and developed by Kreluna: they illustrate our approach and quality, but are not presented as projects commissioned by clients. Explore all projects and design decisions →
We map the steps, users, data, permissions, and difficulties in the current process.
The first version covers the features that are genuinely necessary and testable.
New modules and integrations are added to a system that can already be measured.
Each case has a status, owner, documents, and next deadline, with alerts so it does not depend on one person’s memory.
For a hospitality workflow, we can assess arrivals, cleaning and maintenance with separate owners and statuses. A shared calendar requires current sources, permissions and rules for changes or overlaps.
Roles, activity logs and retention periods are defined with the business before development. The client must confirm data processing requirements; technical implementation is not a compliance certification.
When a process involves departments, colleagues, or many files, the problem is not just storing data. It needs to show responsibilities, work status, the next task, and exceptions without multiplying spreadsheets and emails.
We select a frequent, measurable workflow, define roles and permissions, and build an initial module that can be tested. Integrations follow only after checking APIs and the quality of available data.
We ask to see how work is done today, using anonymized real examples. Then we document what the tool will do, what it will not do, and who will update it.
Objective, intended users, materials, and current tools.
Included work, timeline, costs, and external dependencies.
Agreed revisions, checks, and delivery.
Yes. Profiles, visibility, and approvals are designed around the agreed process. We do not assume them before understanding the actual responsibilities and data.
Every project starts with your needs. Together we define goals, features and timing, then prepare a tailored proposal.
When a process has specific rules, roles, or connections that standard tools cannot handle without duplicated work.
That depends on the APIs and access available. Every integration is assessed and quoted before development.
Describe one process from start to finish, including roles, steps, exceptions and current tools. Share anonymized sample documents or exports and specify data volumes and available access. Analysis defines the first module and assesses migrations and integrations separately.
Describe the process to improve and share an anonymized example of the data or documents used. We identify the first module to analyze before estimating development.
Write to KrelunaFor businesses, practices, and companies in Rome, work is organized remotely with one point of contact, scheduled online meetings, and decisions documented in writing. Distance does not change the method: objectives and content first, followed by structure, checks, and launch.
Assessing a migration requires anonymized sample data, formats, volumes and duplicate handling rules. The scope defines completeness checks and validation responsibilities; the previous system is not replaced before an agreed transition.
The first discussion separates what needs to work immediately from later developments, so the project does not grow out of control.