Berke Özyaşar

Automation bots

Turnkey systems that run on their own for repetitive work such as data collection, price and stock tracking, reporting and notifications.

Checking the same websites every day, moving the same data from one place to another, preparing the same report by hand: these are jobs software can do for you. I'm Berke Özyaşar, and I turn repetitive work such as data collection, price tracking, reporting and notifications into turnkey systems that run on their own.

Who it's for

  • E-commerce and retail companies that need to keep regular track of competitor prices, stock levels or listings
  • Teams that collect data from different sources and turn it into reports
  • Businesses that want to run an unstaffed service with a mobile app and a server
  • Anyone who wants to know immediately when a specific event happens

What's included

  • Automated data collection through web scraping and API integrations
  • Price and stock tracking, with email or message notifications when a threshold is crossed
  • Cleaning the collected data, writing it to a database and reporting on it
  • Text and comment analysis, for example identifying the overall sentiment in video comments
  • Scheduled tasks, retries on failure and logging
  • A simple dashboard or Grafana panels to monitor the results

How I work

The job itself comes first

Who does this job today, how often, and in what steps? Writing out the manual process step by step makes clear what the automation will and won't do.

Designed to withstand breakage

Websites change, and APIs sometimes don't respond. I build retries, rate-limit compliance and an alert mechanism into the bots so you hear about it when something goes wrong.

Compliance

We assess the terms of use of the sites data is collected from, and any obligations around personal data, from the start. If there is an official API, I prefer to use it.

Handover

The system is set up and running on your server, or on a server set up on your behalf, and handed over with documentation.

Start small

The healthiest approach is to start the first version with a single source and a single output, confirm that the system runs correctly for a few days, and then expand the scope.

Technology

I mostly write bots in Python and Node.js. For data collection I use official APIs first, HTML parsing if there are none, and browser automation when necessary. Results are written to a database such as MySQL, with Grafana dashboards and email or message notifications for monitoring. For projects with a mobile side I use React Native.

Related projects

The autonomous car wash app I built for a client was designed to bring flows such as finding a station, starting a wash and paying onto the phone at unstaffed car wash stations. The Polymarket bots are an example of automation that scans order books every few seconds and trades on its own when the conditions are met. To talk about your project, you can write to me from the contact page.

Example projects

Frequently asked questions

What kind of work can be automated?

Repetitive work whose rules can be defined: regular data collection, price and stock tracking, report preparation, sending a notification when a specific event occurs, and so on.

Where does the bot run?

Usually on a server, as a scheduled task or a continuously running service. Depending on your needs, it is installed on your server or on a new one.

What happens if the target site changes?

The bot logs the error and alerts you; the integration then needs to be updated. That is why it is a good idea to plan post-launch maintenance from the start.

Can data be collected from any website?

Technically it is often possible, but the site's terms of use and personal data regulations are what decide. If an official API is offered, I use that first.

Let's ship your app together.

Describe what you want to build in a few sentences. I reply the same day.

Use ↑ ↓ to navigate, Enter to open, Esc to close