Kreluna Gestionale
Customers, projects, tasks, and payments brought together in one workspace.
Open and try →Agencies, professional practices, and service companies in Milan manage projects, hours, quotes, and customers across spreadsheets and disconnected tools. Custom software makes sense when that patchwork starts causing errors and wasting time.
We do not replace everything: we identify the step most often performed manually today and turn it into a tool with roles, history, and exportable data.
Our only office is in Montecatini Terme: Kreluna does not have offices in Milan. 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.
Project-based businesses need to know how much time each customer takes: straightforward time entry, project summaries, and clear margins.
Owners, staff, and external consultants see only what they need, with access logged and customer data protected.
Invoicing, calendars, and email stay where they are: we assess which integrations are feasible and which tasks are better left manual.
Requests, checks, and approvals often pass through several tools. We map inputs, responsible people, timelines, and exceptions to understand where dedicated software genuinely reduces duplication and manual steps.
CRM, ERP, email, and document repositories can be connected when suitable APIs, permissions, and data are available. Each integration is estimated separately to avoid hidden dependencies.
For software projects, we begin with a session where the business shows us how it works today, including screens and files. This becomes a scope document signed before development.
Objective, intended users, materials, and current tools.
Included work, timeline, costs, and external dependencies.
Agreed revisions, checks, and delivery.
It can replace the parts included in the project after agreed testing and migration. Official procedures, historical data, and external systems remain in use until the transition has been verified.
Yes. The project is managed remotely from our Montecatini Terme office; we do not claim to have a Kreluna office in Milan. 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 companies and professionals in Milan, the project can be managed entirely online: shared materials, tracked revisions, and an agreed schedule. Every feature is tied to an operational need, avoiding pages or tools added simply to fill out the quote.
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 proposal separates the essential core from optional features so priorities, costs, and timelines can be compared before work begins.