Context
The product goal was simple on paper and messy in operations: collect large volumes of Austria-focused business data, keep it structured, expose it through API and admin surfaces and make it usable for contact and export workflows.
What mattered technically
The strongest design choice was turning the pipeline into operating presets instead of one generic command. That let the system run in smaller Vienna demos, city-wide presets and broader Austria-wide passes without changing the operator interface every time.
Delivery shape
- Unified parsing flow instead of multiple disconnected scripts
- FastAPI application layer for internal access
- Contact management and export steps bundled into the same operating model
- Separate presets for demo, city scope and nationwide scale
Why it is a strong portfolio signal
This is not just a scraping script. It is an example of product-minded backend work: shaping collection logic, admin behavior, exports and workflow constraints into something an operator can actually use.
Outcome
The repository documents a Vienna demo around five thousand businesses, a Vienna-wide preset above fifty thousand and an Austria-wide path above one hundred thousand. The important outcome is not the raw number alone, but that the system was built as a repeatable workflow rather than a one-off crawl.