Develop once. Reuse for good.

Standardordner2030 is not a finished catalogue and not a large suite. We are building an open folder in which digital specialist procedures take shape and can then be reused by further municipalities and organisations.

A municipality or public organisation has a concrete problem and needs a specialist procedure for it. That can be developed first for this one organisation – or together with others who have the same problem.

Afterwards the procedure sits in the folder as an open building block. Others can reuse it, adapt it to their workflows, or develop it further together.

Small means a clearly bounded task, a manageable need, faster to deliver than a transformation project. No complete new suite, no unnecessary complexity.

The starting point is not a technical problem, but a very human thought: “There really should be a solution for this!”

Anyone working in administration, organisation, or digitalisation knows that sentence. A task costs time every day: lists in spreadsheets, email back and forth, copying information between systems, manual workarounds, software meant for something else – or the realisation that software for this one task exists in theory, but would require a new major project.

The problem is often not that no software exists at all. The problem is that a concrete task immediately becomes a complete project. Standardordner2030 starts one size smaller: at the concrete task. And once that solution works, the next municipality does not have to start from zero.

A municipality needs a digital solution for a concrete process. Another may soon face the same task. Standardordner2030 thinks from the first solution to the next reuse.

The path is: need, development, folder, reuse, adaptation, further development. What is created for one organisation can then be available to others. An extension in turn stays part of the open procedure.

Standardordner2030 thinks of specialist procedures as smaller, reusable, and connected. A procedure does not have to do everything. It should first solve one concrete task – and stay open enough that others can reuse and adapt it.

The primary audience is people and organisations in the public sector – especially small and medium municipalities, local administrations, public organisations, municipal companies and utilities, as well as staff, digitalisation leads, and IT leads in smaller organisations.

Importantly: the audience does not need IT expertise. Standardordner2030 first speaks to people in Germany who want to improve administration and organisation. Not people looking for “a modular API-first open-source architecture”.

It should meet people who say: “We still do it this way – but it really should be easier.” That is the real starting point.

Several principles belong together and show another path between major projects and island solutions.

A procedure for a concrete task may solve exactly that task. Further functions can be added later – as another building block, or by connecting to existing systems.

Request, appointment, document, case: what belongs together should know about each other. Information flows instead of being entered again.

Reuse works better when the software stays open. Open source is not the product. It keeps the folder open for reuse, adaptation, and further development.

First the specialist procedure should solve the concrete task. After that it matters that others can follow it, host it themselves, adapt it, and develop it further together.

Today a solution often stays with the one project it was built for. Standardordner2030 includes the step after that: what is developed can sit in the folder and be reused by others.

Our aim: develop a specialist procedure once and reuse it many times. We do not claim that numerous procedures are already in productive reuse. We are building the folder in which that becomes possible.

Whoever needs a function does not necessarily have to fund an entirely new product. A concrete need can start an open procedure. Over time a shared body of software grows – where the needs actually appear.

Standardordner2030 is initiated and developed by Pacifico Digital Explorations. Pacifico is the starting point and develops the first applications and the technical foundation.

Long term, the idea is larger than a single Pacifico product. The folder should be able to open and grow: further developers, companies, organisations, municipalities, public institutions, and partners can contribute, build applications, extend blocks, or bring requirements.

“Developed by Pacifico” is correct for the current state – but conceptually not necessarily the long-term identity of Standardordner2030.

The year is not a promise: “Everything will be done by 2030.” It is a question about the future: How should software for the public sector look if we rethink it today?

Software could be clearer and more pleasant, less rigid, communicate with other tools, stay open, evolve, be introduced step by step, complement existing systems – and actually help people in their work.

Standardordner2030 is also a concrete vision for how public software could come into being. Not futuristic for its own sake, but very practical.

The folder is not full yet. And that is intentional.

We do not know today which specialist procedures will be needed most urgently tomorrow. That is why we are not simply building a huge suite and claiming that solves everything.

We fill the folder where concrete needs appear. A solution can begin for a single organisation, be developed together, and then be reused by many.

Not an all-in-one suite, and no claim to replace all administrative software. Not a finished catalogue of reusable procedures – the folder is being built, and that stage may stay visible. Not an abstract open-source project detached from concrete tasks. And not classic custom development whose result stays locked inside a single commission.