Selling software that becomes part of public processes

Selling software to public administrations forced me to change perspective. You are not selling technology alone: you enter processes involving homes, maintenance, documents, citizens and operators who must still be able to work the day after release.

At Tecnosys Italia I work commercially with solutions for public housing and, in a separate business line, local police. The contexts differ, but share one feature: software does not live in isolation. It must coexist with regulation, established procedures, existing systems, internal expertise and services delivered to people.

A vertical market changes how you sell

Tecnosys publicly reports more than forty years of experience, over 300 software installations and a presence exceeding 70% of the Italian public-housing market. These are company figures, not personal results. They help explain the context: entering such a specialised sector means meeting organisations that understand their processes deeply and do not need a generic technology demonstration.

Sales therefore becomes diagnostic work. Before proposing a feature, you need to understand who will use it, which passage it replaces, what information it requires and which other systems it touches. An apparently simple request may involve property assets, maintenance, document management, accounting, citizen portals and supplier relationships.

The product does not erase the process

Innovation stories often use a shortcut: new software eliminates complexity. In reality, part of that complexity is intrinsic to public services. Good digitisation does not hide it behind a screen; it organises it, avoids duplication, makes decisions traceable and enables people to work with coherent information.

AgID's Three-Year Plan for ICT in Public Administration emphasises interoperability, cloud, data and digital services. Those principles become concrete only when they meet everyday applications, responsibilities and processes. That is where a platform stops being a presentation and becomes working infrastructure.

This is also a Change Management problem: a technically correct solution can fail when the people expected to use it do not understand the change or are not supported through it.

From communication to complex sales

Moving from communication and production projects to software for public bodies did not erase my earlier skills. It made them easier to test. Listening, asking questions, translating between languages and coordinating expectations remain central; what changes is the depth of the consequences when a commercial promise becomes a process used for years.

This is where sales and listening meet work across technology, communication and people.

The responsibility not to sell a shortcut

In these markets, the commercial relationship does not end with a signature. What was promised must be understood by the team, configured, adopted and maintained. I increasingly see sales not as persuasion but as shared responsibility: defining a problem honestly before deciding whether and how technology can solve it.