Public sector software development starts at the paper form.
Public sector software development rarely fails on the statutory case systems. It fails on the processes beside them, captured on paper and typed up in the office. Those we build as web applications.
One delivered project
We moved a municipal summer sports programme from paper onto a web application.
Cut small
A clearly bounded process needs no platform, only the slice that hurts most.
External users first
Instructors, contractors and clubs produce the data, usually with no access to the internal system.
Government digitalization software: what we build.
-
The summer sports programme of a municipal enterprise
External instructors record their course in seconds from a phone. The enterprise sees the reporting daily and produces sponsor evidence in one click.
More on this
Before that, every course on every day meant a paper form, and the totals were added up after the season. Three details per course are enough: attendance, how it went and the weather.
-
Take over legacy paper records
We read last season's forms with AI support and imported them. The application started with comparison figures from the previous year.
More on this
A stack of similar forms covering several years is captured in structured form, checked and imported. More on that: AI Automation.
-
Access for external users first
Where the data is produced by contractors or volunteers, we build for their day: phone before desktop, three fields, access without an IT ticket.
-
Reporting and evidence at the press of a button
Report by period, course, location and attendance. The document for sponsors, funding bodies or the council appears on click.
More on this
Facility and course administration and guided application journeys belong here too, on request extended by a mobile app. The course side: Sport & Clubs, the office side: Administration & Back Office.
-
The deletion list first, the software second
We ask first which process can be dropped altogether. A digitized form that nobody analyses is only faster at being redundant.
More on this
After that we work backwards: what has to be evidenced to whom? Running costs are named before we build. Code, repository and accounts run in your name.
Which process still runs on paper?
Tell us which service triggers the most phone calls. We say which part maps cleanly to a digital process.
Common questions from municipalities and municipal enterprises.
Have you worked for the public sector before?
Yes. For the municipal enterprise of a city we moved course and attendance capture for a sponsor-funded summer sports programme onto a web application, including an AI-supported takeover of the previous season. The city is not named, for lack of approval.
Can you integrate with our statutory case system?
If the case system offers an interface, that is routine. If it does not, the bottleneck sits with its vendor, and we clarify that before the project starts. Often the better route is to put the process in front of the case system: capture outside, an orderly handover inside.
What about data protection and hosting?
Hosting in the EU, a data processing agreement, data minimisation by design. In the project above three details per course are enough, and no personal data of participants was needed. See GDPR-compliant delivery.
Does something like this have to go out to tender?
Your procurement rules decide that, depending on contract value, legal form and internal policy. Many projects of this size sit below the thresholds for formal procedures.
When are you the wrong partner?
For certified case systems available off the shelf, such as civil registry work. In EU-wide tenders a small team usually fails the suitability check, and the same goes for framework contracts with round-the-clock availability.
What about digital accessibility?
Public bodies have requirements of their own. We build with semantic HTML, keyboard operation and sufficient contrast, and agree the scope of testing up front. Details: accessible delivery.
What does it cost to run per year?
We name the figure before we build. For a narrow process with few users, running costs stay small enough for a normal operating budget.
Read on.
Which form gets handled twice at your organization?
You get a first assessment, including one that says the effort would not pay off.
From paper form to reporting.
Name the process, the people who capture it and the evidence needed at the end.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.