Kreluna Gestionale
Customers, projects, tasks, and payments brought together in one workspace.
Open and try →If projects, hours and clients in your Milan business move between spreadsheets and separate tools, we analyze one complete workflow. Dedicated software is assessed after identifying duplicate data, responsibilities and exceptions, without assuming everything must be replaced.
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 has no office in Milan. 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.
If project summaries are needed, we define how hours are recorded and approved. Margin calculations also require reliable costs and revenues: formulas, sources and access must be agreed before development.
For each role, we define which data can be read, changed or exported. Activity logs, retention and external access require explicit requirements; they are not assumed and do not replace assessment of the business’s obligations.
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 analysis, we request an example of current work with anonymized screens and files. The scope document describes fields, roles, steps and exclusions; it is agreed before development and identifies integrations to assess.
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.
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 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.
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 proposal separates the essential core from optional features so priorities, costs, and timelines can be compared before work begins.