Mental BoundMental Bound
EL
Fire Protection

Fire Protection Pro — Every inspection on time

Our own system for Greek fire-protection companies. Staff upload supplier invoices, delivery notes and their own invoices to clients, Claude reads them, a person confirms, and the system keeps the stock, the account of every installation and a maintenance schedule that reminds them before anything is due. The app is in Greek; demos are on request.

Full-Stack DevelopmentLLM (Large Language Model)Multimodal AIAgent (AI Agent)MCP (Model Context Protocol)
Software DevelopmentAI & AutomationData & Analytics
Visit website
pirosvesi.gr/en
The Fire Protection Pro landing page: the headline Every inspection on time. Every figure in its place., the Book a demo button, the formats it reads, and the top of the app's maintenance screen in Greek
The landing page on a phone: the headline, the description, the two buttons and the top of the maintenance screen
The landing page. The app's screens on it are drawn with sample data.

At a glance

trades
10
Extinguishers to signage and studies, plus one for everything else; every line is filed under one
months to the next service
12
Booked by a confirmed extinguisher invoice; the hydraulic test goes 60 months on
days' notice
30
Each task turns due 30 days ahead by default, on the dashboard and in the menu
hard deletes
0
Originals and readings are kept; visits, declarations and stock counts are only ever added

What we built

Reading the paperwork

Claude
  • Upload supplier invoices, delivery notes, combined invoice-delivery notes (ΤΔΑ), credit notes, a technician's Excel and the company's own invoices to clients: PDFs, scans, phone photos, Excel or CSV.
  • Claude reads each one into a proposal: supplier, items, quantities, prices and discounts, copied as printed. An e-invoice's XML is read by code, at no reading cost.
  • A person checks the proposal beside the original and confirms. Duplicate files, totals that don't match the document and a delivery note that may already be invoiced are flagged first.
  • Nothing counts until a person confirms, and every figure is computed in SQL.
  • Suppliers and technicians fill themselves in from the documents, matched by VAT number first, each with its balance. List price and discount keep separate histories, and a change shows on the dashboard.
  • The vocabulary joins a supplier's wording to the company's item (“ΠΥΡ/ΡΑΣ Ξ.Σ. 6KG” is the 6 kg dry-powder extinguisher) and learns each new spelling.
  • It shares its core with JobCosting.gr: both grew out of a costing system we built for a construction company.

Installations, schedule and stock

Per installation
  • Each installation is a client's site, with its address and its own maintenance schedule. Every task has a next date, an interval and a reminder lead time, 30 days unless set.
  • Tasks show as overdue, due or scheduled, counted on the dashboard and in the menu. A late visit doesn't shift the contract's calendar.
  • A confirmed invoice for selling, servicing or recharging extinguishers records the visit itself and books the next annual service 12 months on and the hydraulic test 60. An admin sets the intervals; other recurring tasks, such as a detection test or a pump run, are added by hand.
  • From each extinguisher invoice it drafts the text of the gov.gr solemn declaration: editable, every version kept, copied for gov.gr or Word. A person issues it on gov.gr and records its code.
  • Stock comes from the same documents: purchases add, sales subtract, credit notes reverse. Counts and corrections are only ever added, and a shortage shows without blocking a sale.
  • Each installation's account: what was invoiced, line by line and by trade, in materials, services and technicians, with net, VAT and total, and an Excel export.
  • Clients with their invoices, paid and outstanding, and their installations.

Assistant, roles and history

Claude · MCP
  • An assistant answers in Greek from the company's documents, stock and installations. It builds tables for Excel and saves reports that rerun on today's figures.
  • It proposes a change only as a card; nothing changes until a person clicks it.
  • The same assistant works inside a user's own Claude, through an MCP server, with the same permissions as on screen.
  • Three roles, admin, accountant and manager, enforced by the database, not just by the screens.
  • No sign-up: an admin creates every account, and an account is disabled, never deleted.
  • Original files and every reading are kept; visits, declarations and stock counts are only ever added.
  • It reads the documents a company already issues and receives. It doesn't issue invoices or replace the accounting software or myDATA.
  • The landing page, pirosvesi.gr: a static Next.js site on Vercel, Greek at the root and English at /​en. Demo requests come by email.

From the invoice to the next visit

  1. Office or site

    Upload

    A supplier's invoice, a delivery note, a technician's Excel or the company's own invoice to a client: PDF, scan, photo or XML.

  2. Claude

    Read

    Claude reads it into a proposal; an e-invoice's XML is read by code. Nothing counts yet.

  3. Accountant or admin

    Confirm

    A person checks the proposal beside the original, with duplicates and mismatched totals flagged, and confirms.

  4. Postgres

    Count

    SQL updates the stock and the installation's account. The browser never sums.

  5. Each installation

    Schedule

    An extinguisher invoice books the next service and hydraulic test, and each task turns due 30 days ahead.

Each confirmation teaches the vocabulary a supplier's wording, so the next invoice needs fewer fixes.

Screens

pirosvesi.gr/en#product
Document reading: a supplier's ΤΔΑ beside its lines on the review screen, a note that the totals match the document, a warning that a delivery note from the same supplier may be invoiced here, and the Reject and Confirm buttons
Reading: the document beside its lines, the totals checked, a delivery note that may already be invoiced.
pirosvesi.gr/en#product
The maintenance section: a confirmed invoice to a hotel for servicing and recharging extinguishers, and below it the installation's schedule with the annual service in 12 months and the hydraulic test in 60
A confirmed invoice records the visit and books the next ones.
pirosvesi.gr/en#product
The declaration section: the drafted text of a gov.gr solemn declaration for a hotel's extinguishers, with a table of types, work and quantities and the buttons to mark it issued and to copy it for gov.gr
The gov.gr declaration, drafted from the invoice. A person issues it.
pirosvesi.gr/en#product
The stock section: the stock screen with stock, purchases and sales per item, one hose marked as a shortage, and an Excel button
Stock from the paperwork. A shortage shows and never blocks a sale.
pirosvesi.gr/en#product
The assistant section: a question in Greek about the hoses in stock, answered with a table of three hoses, one of them short, and Excel and report buttons
The assistant answers from the company's own figures.
pirosvesi.gr/en#features
The features section: an account per installation, prices and discounts, clients and collections, one item under many names, suppliers and technicians, and roles and Excel
And what the office needs: accounts, prices, clients, one item under many names, roles.

Built with

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Supabase (PostgreSQL)
  • Claude
  • MCP
  • ExcelJS
  • Vercel

Ready to get started?

Tell us about your goals — we'll propose milestones within 48 hours.

Start your projectTry the Project Planner