Public sector

Digital government software from Italy

Identity, payments, notice boards, accessibility. Italian public-sector work is the track record. English RFPs welcome — we answer in English.

Call +39 091 748 0072 Send the tender

EU company, GDPR by defaultThe code is yours from commit oneA developer answers the phone

EU companyItaly · GDPR by default
CETthe working day shared
You own the codeYour repo, first commit
One phone numberA developer answers

Does any of this sound familiar?

Public-sector software is judged on the documentation and the accessibility as much as on the build.

What it looks like now

Accessibility was left until the end and failed the audit
Identity and payment integrations are fragile
Documentation is assembled after delivery, from memory
Retention obligations are handled by convention, not code

What it looks like after

WCAG built in from the first interface, not retrofitted
Identity and payments integrated the way the standard specifies
Documentation produced as the work happens
Retention enforced by the system

Italian public administration is the track record

Public-sector software in Italy has to satisfy AGID design and accessibility rules, integrate national digital identity (SPID and CIE), take payments through PagoPA, and publish legally significant documents on a notice board where the timestamp genuinely matters. Those are not badges in a footer — they are constraints that decide the architecture, and building against them is a different discipline from building a brochure site on a CMS.

That is the experience we bring to public-sector work elsewhere. The specific national systems change; the shape of the problem does not.

What transfers across countries, and what does not

What transfers is the hard part: federated identity and the assurance levels behind it, payment reconciliation where the citizen must never be charged twice, document retention with a defensible audit trail, accessibility as a legal obligation rather than a preference, and procurement that judges your documentation as strictly as your software.

What does not transfer is the national plumbing. SPID is not a login button you port to another country, and PagoPA is not a payment gateway you drop into a Gulf ministry. Anyone claiming otherwise has not implemented either. We name which parts are experience and which parts are new work, in the proposal, because a tender that discovers this later becomes a dispute.

Accessibility is a requirement, not a nice-to-have

For public bodies in the EU, accessibility is law, and it applies to the service as delivered rather than to a compliance statement about it. We build to WCAG from the start — keyboard operation, contrast, focus order, forms that make sense to a screen reader — because retrofitting accessibility onto a finished interface costs several times what building it in does, and usually still fails an audit.

Hosting, data and the EU

We are an Italian company, so EU hosting and GDPR are the default. For public-sector buyers that is often the point: data residency is answerable, the processing agreement is a standard European one, and there is no transfer mechanism to defend. Where a tender requires hosting in your own country or on your own infrastructure, we build for that — but it needs to be stated in the requirements, not assumed, because it changes the design.

How we handle a tender

We read it before we answer it. If we do not fit the requirements, we say so and decline — a bid we cannot deliver wastes your evaluation time and our week. If we do fit, you get a written scope naming what is in and what is out, a delivery plan in two-week increments, and the technical documentation produced as the work happens rather than assembled afterwards. The code is yours, in your repository, which for a public body also means the next procurement cycle is not hostage to us.

We answer in English when the document is in English. We do not submit machine-translated Arabic, and we would treat a supplier who did that to us as unserious.

Where the buyers land

This hub is the practice. Market-specific work sits on its own page: digital government software for Riyadh, written for English-language RFPs and Vision-programme timelines rather than being this page with the city swapped.

Questions from this market

No. We read it first, and if we do not fit the requirements we decline. A bid we cannot deliver wastes your evaluation time. The first call costs nothing.

Yes — as delivered features in Italian public-sector work, not as logos. What that gives you elsewhere is the pattern for federated identity and payment reconciliation, not a portable SPID integration.

Yes, if the tender requires it. Our default is EU hosting under GDPR; anything else needs to be in the requirements so it shapes the design from the start.

It is built in, not quoted separately. For public bodies it is a legal requirement, and adding it after the interface is finished costs several times more and usually still fails.

The administration does, in its own repository. That also means your next procurement is not locked to us.

+39 091 748 0072 — Davide di Vietro or the project manager on your work.

Digital government in Riyadh — English RFPs, programme timelines.
The Palermo office — Where the team sits.
Custom software — How we build in general.

The way we work, in numbers that are actually checkable

2 weeksSprint length. Something you can click at the end of each one.

100%Of the code in your repository, from the first commit.

2010Working from the same office in Palermo since then.

1Phone number. Davide or your project manager picks it up.

Public-sector software is judged on the documentation and the accessibility as much as on the build. Both are cheaper written from the start than added at the end.
What Italian public administration work taught us

How this compares

The difference is not talent. It is having already failed and fixed these specific things.

	Custom build with us	A generic web agency
Accessibility	WCAG from the first interface	Audited near the end, often failed
Digital identity	SPID and CIE shipped in production	First time, on your budget
Payments	PagoPA reconciliation done before	A gateway integration
Documentation	Written as the work happens	Assembled afterwards from memory
At handover	Code and docs to the administration	Depends on the contract

How this actually goes

1
A call about the process
Twenty minutes on what your operation actually does, not a pitch. You speak to the person who would run the work, not to a salesperson.
2
A written scope
What is in, and — the part that prevents arguments — what is out. One fixed price, not a range that grows later.
3
Two-week sprints
Each one ends with something you can open and try. You see progress every fortnight instead of waiting months for a reveal.
4
Handover, whenever you want it
The repository has been yours since the first commit. We stay for operations if you want us, and nothing breaks if you do not.

The things you are probably thinking

Said plainly, because you would find out anyway.

You are not based here.

Correct, and we will not pretend otherwise. The office is in Palermo. What that costs you is the occasional flight for a workshop; what it saves you is an EU team at EU rates with the whole day in common.

What if you disappear halfway through?

The repository is yours from the first commit, in your own organisation, with the documentation written as we go. Another team can pick it up. That is deliberate: a supplier who can hold you hostage has no reason to stay good.

We have been burned by a development agency before.

Usually by a moving price and a vague scope. So the scope is written, the price is one number, changes are quoted before they are built, and you see working software every two weeks rather than at the end.

Our requirements are not fully defined yet.

That is normal and it is the first call, not a blocker. If the shape is still unclear we scope a short discovery with its own fixed price, and you own whatever comes out of it even if you stop there.

Can we start small?

Preferably. One sprint on the piece that hurts most tells you more about working with us than any proposal, and it costs a fraction of committing to the whole thing up front.

Where does our data live?

In the EU by default, because we are an Italian company and GDPR is our baseline rather than an add-on. If your contract requires another jurisdiction, we build for that and write the decision down.

What you keep if it goes wrong

The code, always

The repository is in your organisation from the first commit. If you stop the project at sprint two, you keep everything written up to sprint two, running, with the documentation.

A fixed number, not a range

After the written scope the price is one figure. If the scope changes, we quote the change before doing it — you never find out from an invoice.

An honest no

If an off-the-shelf product covers your case, we say so on the first call and you save the budget. We do not resell licences, so nothing about that advice pays us.

English RFP, public-sector team in Palermo. Call.

One call, no obligation. If an off-the-shelf tool fits you better, we will say so.

Call +39 091 748 0072 Request a quote

Davide di Vietro or the project manager on your work answers. No call centre, no form that disappears into a queue. Prefer writing? info@dadomediaweb.it.

Call Palermo Get a quote