Property document automation
Real-estate document service for property sales · Built from scratch, solo
Updated
Before
Sellers paid EUR 200–300 for each certificate and waited 2–3 weeks while someone collected the papers by hand.
After
2–3 min
per certificate, at EUR 99 instead of EUR 200–300.
- 2–3 min
- per certificate, instead of 2–3 weeks
- EUR 99
- per certificate, instead of EUR 200–300
- 95%
- of documents completed on the main known portal
- 1Person:Customer
Orders a property certificate.
- 2Software:Script
Known portal: logs into the account and collects the data.
Software:Vision AIUnknown portal: reads the pages.
- 3Software:Service
Builds the certificate.
- 4Software:Service
Runs five checks, then sends the certificate to the customer.
Always on
- A failed step retries on its own.
- The operator sees every job in real time.
Problem
Each certificate was prepared by hand from many property-manager accounts. It took 2–3 weeks and cost EUR 200–300 per document.
Diagnosis
Portals differ and change often, so one scraper never lasts. Known portals can be scripted; unknown ones need reading like a person.
Options I weighed
Every portal works differently and changes often. How is the data collected?
Chosen
A script for known portals, vision AI for unknown ones
Cheap and predictable where possible, adaptable where not. The AI path sits behind a switch that turns it off instantly. Cost: two code paths to maintain.
Rejected
One hand-written scraper per portal
Breaks whenever a portal changes its layout.
Solution
The service logs into the property managers' accounts, collects the data and builds the certificate itself. Five checks run on every document before release; unknown portals go to vision AI.
- Operator app
- Next.js
- React
- Tailwind CSS
- Radix UI
- Zod
- Data and jobs
- Supabase
- PostgreSQL
- Automation and AI
- Python
- Playwright
- Crawl4AI
- Docling
- Instructor
- Gemini
- Delivery
- Docker
- Vitest
- EU-hosted server
Related services
Figures: Author-verified