PKB Core · Property inspection, Prague · 2026 – now
Giving an inspection practice its evenings back.
PKB Core runs the whole job, from a booking on the website to a paid invoice. Inspectors work with no signal and lose nothing, and the protocol writes itself in Czech, English and Russian.
- Product
- Architecture
- Offline inspector app
- Protocols
- Automation
Overview
What they sold was a document. Making it took an evening.
PKB inspects flats before people buy them. Inspectors handed in their work their own way, a folder of photos here, a photo of a notebook there, and an administrator spent the evening turning it into a protocol: Word and Excel, translations through a chat window, PowerPoint to make it presentable.
We built the whole chain as one system: the request, the schedule, the inspection, its defects and photos, the protocol, the invoice and the payment.
For businesses whose work ends in a document someone assembles by hand.
What it had to do
- Capture an inspection where there's no signal, and lose nothing.
- Give every inspector the same words for the same defect.
- Turn work already done into the protocol, in three languages.
- Run the office's routine without anyone chasing it.
Try it
Take the signal away.
Pin a defect where it was found, then go down to the basement. The phone keeps everything, and lets go of a change only once the server confirms it has it.
The library
One vocabulary for a defect.
112defect templates, written once and used by every inspector, so the same crack is described the same way
From their own spreadsheet
Built from the practice's expert spreadsheet, in their words, not a template's.
The standard behind it
Each carries a technical note citing the Czech standard that applies.
A cost attached
Each carries a repair-cost range the client can act on.
Try it
Switch the language.
The protocol assembles from work already done, laid out like the deck the office used to build by hand, and translated without anyone pasting text through a chat window.
- 1Cracks in Room CornersMedium defect
- 2Uneven FloorMajor defect
- 3Gap Between Floor and Skirting BoardMedium defect
- 4Damaged Window SillMedium defect
- 5Window Adjustment NeededMedium defect
The protocol's own headings and PKB's own defect wording, in each language.
The product
The office runs itself.
A job nobody claims goes to the inspector with the lightest day. Clients and inspectors are reminded the day before. Invoices mark themselves overdue, and payment reminders go out. On Monday, a digest leads with whatever is stuck.
On site, the inspector's phone holds the whole job until the server has it.
- 4Mould in the shower enclosureBathroom · Major defect
- 3Damaged Window SillKitchen · Medium defect
- 2Uneven FloorLiving room · Major defect
- 1Cracks in Room CornersLiving room · Medium defect
Demo dataThe screens are captured from the live product with its demo dataset; no client's property is shown.
The hard part
The phone that went quiet.
Once, a finished inspection stayed on a phone that had stopped reporting. Nothing arrived at the office, and nothing said anything was missing. We recovered it from the handset.
Then we made every phone visible: which runs an old version, which still holds unsent work, which has gone quiet. Now the office can call the inspector before a client calls the office.
Impact
From an evening to half an hour.
4–5 hof Word, Excel and PowerPoint, for every reportClient-reported
30 minto review and send the protocol the system wroteClient-reported · their worst case, most take less
Reviewed, not written: the protocol is checked and sent, and the evening is free again. PKB Core is live at app.pkb-cz.com.
