Scrapers and automations are never truly done, because the sources they depend on keep changing. A site changes layout, an API updates, a process evolves. Without someone watching, things quietly break.
On a retainer I monitor your automations, fix them when sources change, and keep developing them as your needs grow. This is the Run phase, and it is why nothing I ship goes stale.
What you get
- Automations that keep working as sources change
- Issues caught by monitoring, not by you
- Ongoing improvements, not just fixes
- A predictable point of contact
Deliverables
- Monitoring and alerting on your systems
- Fixes when sources or APIs change
- Ongoing iteration and new features
- A monthly retainer scoped to your needs
Common questions
- Can you maintain automation someone else built?
- Usually yes. I start with a short review to understand it, then take over monitoring and fixes.
- How does the retainer work?
- A fixed monthly scope for monitoring, fixes, and a set amount of ongoing development, adjusted as your needs change.
Related work
This in the real world.
E-COMMERCE
100k+ products, −25% costs
Online-pharmacy price monitoring (Gemini.pl)
Real-time tracking of 100k+ products, trend analysis, and change alerts. Purchasing costs cut 25% via historical analysis.
Python · Web Scraping · FastAPI
CaseRECRUITMENT
5 EU sources, daily
Multi-country job-board aggregation (VDAB, Le Forem, EURES, Indeed)
Daily scrapers across Belgian and EU job boards, normalising postings from five sources into one structured, deduplicated recruitment pipeline.
Python · Scrapy · PostgreSQL
Case