Kreluna Gestionale
Customers, projects, tasks, and payments brought together in one workspace.
Open and try →Professional practices, small lodging businesses, associations, and training schools in Rome manage cases, deadlines, members, and guests with tools designed for something else. Custom management software brings order where folders, spreadsheets, and reminders are scattered today.
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 does not have offices in Rome. The project is handled remotely; any in-person meeting must be arranged separately and is not automatically included.
Try the management softwareOpen Kreluna GestionaleOpen the demoThe demos show how customers, appointments, and tasks can become a clear workflow instead of another complicated tool.
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 lodging businesses: arrivals, cleaning, maintenance, and vendors in one calendar accessible from a phone.
Role-based access, an activity log, and defined retention periods, consistent with the data controller’s obligations.
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.
Yes. The project is managed remotely from our Montecatini Terme office; we do not claim to have a Kreluna office in Rome. Analysis, revisions, and delivery take place online.
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 your business, objective, available materials, required features, and approximate budget. After the initial discussion, you will receive a proposal with the scope, timeline, costs, and exclusions.
Tell us what you want to achieve, who will use the solution, and which tools are already in place. We will reply with the questions needed to assess the work.
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.
We reconstruct the current process, the people involved, and the data now moving between spreadsheets, email, or separate tools. Permissions, imports, and automations become part of the project only after their usefulness has been established.
The first discussion separates what needs to work immediately from later developments, so the project does not grow out of control.