Our method

Think. Design. Resolve.

Our motto is not a slogan: it grew out of a reflection on how data becomes knowledge — and knowledge, value. From there follow four clear, measurable phases and three principles we never negotiate: continuous improvement, a single point of contact, open standards.

Before the method

From data to paradigms

The value of a business venture rests on the ideas and the will of the people who bring it to life. The services and products that follow, the processes and the organisation determine the efficiency, effectiveness and profitability of every project.

At the base lie atomic data — the facts — which define information and relations. Properly grouped, these give rise to patterns, to knowledge, to theories and axioms — all the way up to principles, systems and reference paradigms.

Within this semiotic geometry, the value of technology choices comes into focus: it is the ground on which our method is built.

From facts to paradigms: data is handled with tools, information and patterns with processes, patterns and principles with the organisation. In the animation, the rising characters transform at every level: from raw facts to relations, to patterns, up to the equations of principles.

“Information Technology is an indispensable factor for any business, but IT is not the solution: it is merely a tool. Ideas and know-how are what give that tool its value.”

From this reflection comes our motto

Think.

Climb the pyramid: from the facts of your context to relations and patterns. Understand before choosing.

Phase 01 · Analysis →

Design.

Give knowledge a shape: principles, architectures, standards — and a verifiable plan.

Phase 02 · Design →

Resolve.

Return to the facts: the solution in operation, measured on real data — which feeds the pyramid once again.

Phases 03–04 · Implementation and Support →

The phases

The motto becomes a path

Think

Analysis

We start from an assessment of your infrastructure and your business objectives. Where needed, we carry out a Business Impact Analysis and a feasibility study, mapping processes, constraints and risks.

Design

We design the architecture of the subsystems and the implementation plan. Choices are validated before release, with close attention to security, accessibility and efficiency.

Resolve

Implementation

Supply of hardware and licences, system set-up and configuration, testing and a controlled kick-off. Every step is tracked and shared.

Resolve

Support

Management, maintenance and continuous improvement across the entire service lifecycle, with monitoring of performance, security and availability.

The principles

Three principles hold the four phases together

The phases say what we do; the principles say how. They are the same ones we apply to our own infrastructure, processes and products — not rules written for the website.

1 · Continuous improvement

The method does not end at phase 04: it starts again. Every service in operation is measured, reviewed and improved in iterative cycles with constant feedback — that is the logic of our ISO 9001:2015 management system, not a slogan.

We measure: agreed KPIs and SLAs, with regular reporting to the client
We learn: every intervention updates the knowledge base — in the SPOC model, closing a ticket feeds the KMDB and CMDB, so the system gets better with every cycle
We verify: we demand it even of AI — in our RAG platform, answer quality is assessed with metrics, not merely claimed

The cycle we apply to every service in operation — and to ourselves.

2 · SPOC: a single point of contact, end-to-end responsibility

Complexity belongs inside our processes, not in your experience. We operate as one integrated team: the people who design are connected to those who manage and those who support, and towards you there is a single point of contact — from the first assessment to this morning's ticket.

No passing the buck: one number, one person accountable; escalations are our internal process, not your problem
Macro-processes formalised before delivery: incidents, requests and changes are mapped in swim lanes, with priority queues and tracked closures — see the actual diagrams

Our Competence Centres integrate with your IT department: they strengthen it, they do not replace it
The same applies to projects: across the service lifecycle, responsibility stays end-to-end, with no grey areas between project and operations

3 · Open standards

Our first project, back in 2010, was an entirely open source virtualisation system built on OpenStack. Fifteen years on, the principle has not changed: we choose open technologies and standards because the result must remain yours — governable, verifiable, portable.

Open technologies where they matter: from the open source tools of the SPOC service to the on-premise RAG stack, through to the open heritage of ACMe-PA
No vendor lock-in — not even ours: open APIs and formats, migration always possible, and the client owns the result

Process and quality standards: ITIL best practice for services, a certified ISO 9001:2015 quality system, WCAG 2.1 AA accessibility
A choice consistent with the public sector (Italy's CAD digital administration code favours reuse and open source) and prudent for anyone: what is open today does not hold you hostage tomorrow

Why it works

A lean structure, clear roles, measurable results

Our organisational model for services is built around a lean, flexible structure, with clear decision-making roles able to respond quickly and efficiently to a wide range of needs.

Competence Centres that guarantee the result is achieved
Standard procedures that can be tailored to the client's context
Constant availability of resources, even during peaks that cannot be planned for
Every phase produces verifiable outputs: no promises, just evidence

Let's put the method to work on your project

An initial conversation, with no obligation, to work out where to start.