Why we build this

Most organisations running buildings already hold all the information. It is just scattered. The asset register is a spreadsheet. The certificates are in a shared drive. The agreement with the contractor is in somebody's inbox. The invoice is in the finance system. Each one is correct on its own, and none of them agree with each other.

That is survivable right up to the moment somebody asks a question with consequences attached. An insurer asks when the panel was last inspected. A regulator asks who signed off the remedial work. A tenant asks why the same unit has failed three times this year. The information exists. Proving it takes days, and the proof gets assembled by hand, from four places, by whoever remembers where to look.

We did not think that needed a better spreadsheet. We thought the record of what happened should be a by-product of doing the work, rather than something reconstructed afterwards under pressure.

So that is what Prova is. The job, the cost and the evidence stay attached to the same record, as the work happens. When the question comes, the answer is already there.

What we know

We would rather be judged on the product than on a brochure. Here is what is already built into it, and what that tells you about how we think about the problem.

Compliance is jurisdictional, not generic

Regulatory coverage in the product today includes UK health and safety obligations, German DGUV requirements for electrical installation and machinery maintenance, and per-country statutory inspection cycles. An obligation means something different in each country, and the system treats it that way.

Multi-country was the starting point, not a later port

Every address carries its own jurisdiction, timezone and coordinates. Business calendars are holiday-aware per jurisdiction. Spending limits and approval workflows work across currencies, and B2B invoicing supports the reverse charge mechanism.

Obligations change, so they are yours to edit

Obligation categories are defined and edited by you. A requirement we have not already covered is a configuration change you make yourself, not a development request and a place in somebody's queue.

One platform, not a suite of separate tools

Facility management is our main product and it is where our development effort goes. Project management sits alongside it. Both run on the same records, the same permissions and the same audit trail.

That is the experience on offer: depth in a specific problem, and a system designed from the start by people who expected to be asked hard questions about it.

What that means for you

You talk to the people who built it

There is no account management layer between you and the product. The person who answers your question about how compliance grading works is the person who wrote it.

Nobody hands you an empty screen

We complete the initial system setup and data onboarding with your staff before launch, so your buildings, your contractors and your certificates are in place on the first day rather than on your to-do list.

You get a real decision, not a decision made on a demo

We would rather run one region through one full compliance cycle than sign an estate-wide rollout on day one. At the end of it you are deciding on your own buildings, with your own data, instead of on a product tour.

A second product later is not a migration

Because every product sits on the same records and the same audit trail, adding one does not mean moving data between systems. It also does not mean a second supplier, a second contract or a second security review.

Your influence on what gets built is real

The people you talk to are the people who set the roadmap. A requirement that matters to your buildings goes into the plan directly, without a product committee in between.

What happens to your data

This matters more than anything else on this page, because you would be handing us your compliance record.

EU hosting

All customer data is held on servers inside the European Union.

GDPR

The platform and our data processing agreements are GDPR compliant.

Audit trail

Every create, change, sign-off and privileged action is written to a tamper-evident chain, queryable per record.

Access control

Denied by default, granted by role and by scope. A local manager sees their site and nothing else.

Photo metadata

Images are stripped of EXIF data on upload, so location and device details do not travel with your evidence.

Where we are today

Here is the company behind the product, in plain terms.

Prova is a European software company with clients in Europe. The founders build, implement and support the product themselves, so the people who run your onboarding are the people who wrote the system.

Our legal home is the European Union. A United Kingdom entity is planned rather than registered, and until it is, we serve UK customers from the EU company. We would rather tell you that here than have you find it during procurement.

We do not publish customer names or case studies on this site. Ask on the call and we will tell you what we can share.

What working with us looks like is the rest of this page: direct access to the people who build the product, real influence over what gets built next, and an onboarding run by the people who wrote the system.

Prova Software EOOD is registered in Bulgaria under UIC 208821816. You can check that in the Bulgarian Commercial Register. Every claim on this page describes what is built and what is contracted.

Who you would be buying from