Budget: 6000 UAH Deadline: 30 days
I will develop a backend bot in Python for parsing through a headless browser with automatic synchronization of analytics in Google Sheets via API, ensuring stable data collection across all 580 positions even when the structure of the websites changes.
What specific technical method do you plan to use to bypass Cloudflare protection and anti-fraud systems of large laboratories, if without using residential proxies and simulating fingerprints of real browsers your script will get banned after the first hundred requests, leaving you with an empty table and "blind" monitoring at the most critical stage?
Do you have a budget for proxy services to bypass blocks, as well as a step-by-step stack (Playwright/AIOHTTP) and implementation timelines — I am ready to discuss in personal correspondence. 🤝
Budget: 27000 UAH Deadline: 13 days
Hello! The task is clear and understandable. I specialize in automating data collection and have experience working with medical aggregators. I will implement a stable tool that will allow you to keep your finger on the pulse of the laboratory market effortlessly.
What you will receive:
1. Accurate data: Parsing 580 services taking into account promotions and website features (DILA, Synevo, etc.).
2. Convenient control: Administration of the service list through familiar Google Sheets.
3. Instant reports: Every Monday at 09:00 you will receive analytics in Telegram about any price fluctuations of competitors.
4. Stability: Error logging and the ability to run manually by the team /run.
Cost: 35,000 UAH.
Deadline: 13 working days.
Budget: 6000 UAH Deadline: 5 days
Hello!
I develop bots for Telegram using NodeJS. I am ready to take on the project. Write to me, we will discuss.
Budget: 12000 UAH Deadline: 10 days
Hello.
To obtain data, you can use both a browser and separate libraries for requests.
I have indicated the approximate cost and terms in the bid.
I have experience in parsing various websites, both protected and unprotected. I will set up the parser and bot according to your requirements.
Further project support is possible.
Please write to me privately to clarify all details.
Budget: 6000 UAH Deadline: 3 days
Good day!
I offer professional development of your Telegram bot for price monitoring. I have experience in web scraping, working with the Telegram API, and Google Sheets. I am ready to implement all functionality according to the technical specifications, ensure stable operation, and automatic data collection.
Please write to me to discuss the project details and agree on deadlines.
Budget: 6000 UAH Deadline: 12 days
Good day, Vyacheslav!
I understand where the pitfalls are. The most challenging part is not the parsing, but matching services between websites. Each laboratory has its own names for the same analysis. I will do this through a mapping table in Google Sheets, which can be edited manually without a programmer.
Regarding the stack: Python, Playwright for JS websites, Google Sheets API, python-telegram-bot. Deployment on VPS with cron or GitHub Actions. Data - Google Sheets plus SQLite locally as a buffer during parsing.
An important point: parsers typically last about 3-6 months before the first breakdown due to changes in layout. This is normal, but it needs to be understood in advance.
I will add one thing from my side. If you enter your prices in a separate sheet, the bot will immediately show in the report where the competitor has become cheaper than you. This hint is already present in your example report, but it is not specified in the terms of reference. I will do this for free as part of the task.
I have experience with parsing and Telegram bots, and I can show examples. I am ready to discuss support after launch. Please write to me privately.
Budget: 15000 UAH Deadline: 10 days
I have tested all the specified websites and am receiving data. The main difficulty is the different names and codes of services; I propose a solution - we will create a single list (your Google Sheet) and link the services from each website to it. After the initial setup, everything works automatically.
Regarding your questions:
1. The cost mentioned is approximate; we will discuss it in private messages.
2. The execution time is 10 days; this is for development, it may be earlier or later.
3. I write in Python.
4. It will probably be convenient for you to provide it in Google Sheets and store it on the server in a database.
5. Yes, I have experience, and I also have a portfolio with many undisclosed projects.
6. This is how I work; I do not create parsers without support - this is not a one-time development.
I host the parsers on my servers, monitor stability, and fix errors when websites change. I am ready to discuss in more detail; feel free to write.
Budget: 6000 UAH Deadline: 12 days
Ready to take it on. We can work in different ways, but I suggest breaking the project into steps and completing each resource separately. We need to clarify the order details, write to me! I use python, uv, github, docker.
Budget: 6000 UAH Deadline: 3 days
Hello! Do all 580 services have the same page structure as competitors, or are there some that require a separate approach to parsing?
I will clarify the timeline and budget in personal correspondence.
I propose to execute the project as follows:
1. I will develop a parser in Python using BeautifulSoup and Selenium for websites with dynamic content.
2. I will set up data storage in Google Sheets and automatic price comparison with previous collection.
3. I will implement a Telegram bot using aiogram with commands /run, /last_report, /status, and a weekly schedule via cron or APScheduler.
Thank you for considering my proposal. I am excited about the possibility of working with you!
Budget: 27000 UAH Deadline: 30 days
Good day. I write programs for automating various processes. I can write such a bot. Python + Playwright + Telegram API. It is better to store in Google Sheets and in an SQLite database - this way there will be an opportunity to review the database yourself. Yes - I have experience - that is why I indicated such a term. Yes - I provide 30 days of free technical support after the completed project. 33,000 UAH / 30 days
Budget: 10000 UAH Deadline: 10 days
Good day, I have already worked with such laboratories, we can discuss the details of the project. The price and deadline are conditional, the final will be after discussion. Thank you in advance.
Danilo Kanivets
Winning proposal- Projects 54
- Rating 5.0
- Rating 4 654
Budget: 6000 UAH Deadline: 4 days
Good day, I am a Python developer with extensive experience in developing Telegram bots of various complexity. I can complete your order quickly and efficiently. Write to discuss the details, I am ready to start today. I will also upload your bot to the server for stable operation 24/7 and I will provide technical support for the bot for another month. This is included in the cost.
Budget: 6000 UAH Deadline: 5 days
Hello! I have experience in creating Telegram bots with automatic launch and complex parsers in Python. Previously, I made stable solutions with error logging and data comparison, which will be suitable for your price monitoring. What is the most problematic part right now - parsing specific websites or integration with Google Sheets?
Budget: 6000 UAH Deadline: 12 days
Do you have a mapping of service name correspondences between competitors (DILA, Sinevo, Medlab, CSD, Nikolab, DniproLab), or should we create it within the project?
We have experience with parsing and Telegram bots (price monitoring, reports in TG). We propose the stack: Python (Playwright + Requests/BS4), aiogram, APScheduler, gspread; retries, logging, accounting for promotions and cities. The data at the start will be in Google Sheets (separate sheets: services/history/errors); for scaling — PostgreSQL. We do not recommend SQLite for regular collections. The deadline is up to 12 days, budget — $1500. We will implement /run, /last_report, /status, and auto-start on Monday at 09:00. We are ready to start this week and provide support after launch — we will send a brief plan and a pilot on 100 positions.
Proposals concealed
Proposals are currently absent
-
Dmitro Malishevsky 4 MayПідкажіть, будь ласка, що сталось з попереднім таким замовленням?
Щось пішло не так? Можливо, є якісь додаткові умови або складності, які потрібно знати перед початком роботи?
Current freelance projects in the category Data Parsing
Set up automatic daily updates of product availability on our website on prom.ua. We have a supplier who sends a price list of products in Excel format to our email every day. The items on our website and in the supplier's price list are the same. The values in the "stock" column are either out of stock, a number, or more than a box - these need to be updated on the site to either Ready for shipment or Out of stock. Items that are not in the supplier's price list should remain unchanged. Please propose a solution, timeline, and budget. Thank you in advance for your response, I look forward to collaborating with a specialist.
Hello! I am looking for a performer for ongoing collaboration who is knowledgeable about Opencart. A person who is available and has a positive attitude) Parsing, uploading products in two languages UA + ru, as well as forming the necessary markup immediately I want to complete the work in several stages. 1. Update stock for all suppliers and completely remove outdated products from the site and database. 2. Refinement of the product category, specifically parsing subcategories. 3. Parse new items in old categories. 4. Parse new suppliers into new categories.
A project needs to be implemented for collecting and structuring a large array of images from open web sources (initially 2000 images). The task includes: - automated image collection; - uploading files in the highest available quality; - classifying images by categories. Expected results: - a structured image database; - a clear cataloging system; - delivery of the results via Google Drive or another agreed method;
Good day! Two tasks need to be completed: 1. Develop a product parser from an external website (10–40 thousand items, marketplace) with structured data saved in MySQL for subsequent output in WordPress. 2. Install and configure n8n on VPS, as well as organize AI content processing: prompt setup, text rewriting, image processing, SEO optimization, and text checking for AI detection. You can estimate the cost of completing both the entire project and each task separately. .
Task: one dashboard with all business metrics — advertising, funnel, payments, manager performance, revenue planning. Data is pulled automatically via API. Scope: only the YCL direction (employment in Europe). Kommo has other directions — only YCL funnel deals will be included in the repository (filter by funnel/tag to be agreed upon).1. Data Sources (Integrations) Kommo CRM — leads, deals, funnel stages, responsible persons, sources, dates of transitions between stages (must keep history), reasons for refusals, custom deal fields (see point 2). Stripe — payments, amounts, statuses (success/failure/refund), linked to deals. Meta Ads — expenses, impressions, clicks, CPL, leads by campaigns (currently operational). Google Ads, Reddit Ads, LinkedIn Ads — planned; architecture — extensible connectors without core rework. SEO/organic— Google Search Console + GA4. Cross-link: traffic source → lead in Kommo → payment in Stripe (UTM, deal ID in Stripe metadata — propose the mechanism). 2. Mandatory Cuts (Deal Fields in Kommo) Each metric must be filtered/grouped by: Client Citizenship (Kenya, Nigeria, India, etc.). Residence Status: lives in their country / expat (already in Europe). These are two different segments with different cycles, conversion rates, and checks. Country of Placement / Service: Poland, Serbia, Slovakia, Germany (ZAV). Manager, team, traffic channel, period. If any fields are missing in Kommo — the executor indicates which fields need to be added, the client adds them.3. Funnel and Leading Indicators Data by funnel, for each stage — summary and leading metrics: Traffic → lead: leads, CPL by channels + day-to-day expense/click dynamics. Lead → qualification: conversion + first response speed, touches/calls to the manager per day, unanswered leads. Qualification → contract/invoice: conversion + sent offers, stalled deals (days in stage above norm). Invoice → payment: payments, average check + unpaid invoices, failed payments. Summary: revenue, ROMI by channels, run rate to monthly plan. 4. Deal Cycle Average and median lead → payment cycle (business benchmark ~4 weeks), cycle trend over time. Breakdown of cycle by stages (how many days a deal sits at each stage) — to see which stage is dragging. List of deals that have stalled at a stage longer than normal. Cycle breakdown by segments: citizenship, residence status, country of placement, manager. 5. Early Warning of Decline (Key Block) Since the cycle is ~4 weeks, today's leads = payments in a month. The system must: Compare leads/qualifications of the current week with the moving average (4 weeks) and issue an alert if there is a downward deviation: “leads -X%, with a 4-week cycle expect a payment decline in the week [date].” Build payment forecast for 4 weeks ahead from the current pipeline: deals at each stage × historical conversion of the stage × remaining cycle. Highlight in red weeks where the forecast is below plan — with time to react. 6. Additional Payments and Sales Planning In the Kommo deal card, the date and amount of the planned additional payment are stored. The system must: Collect a calendar of upcoming additional payments: total expected, by weeks/months. Highlight overdue additional payments (date passed, no payments in Stripe) — a separate list for follow-up. Calculate the monthly plan as: plan − already paid − scheduled additional payments = how many new sales are needed (in money and in deal units at average check). Weekly schedule: additional payments + forecast of new payments against the weekly plan. 7. Manager Performance Daily snapshot for each manager: touches/calls, conversations, sent offers, payments — for each day separately, with a chart over the period. Progress on personal plan compared to monthly pace (ahead / on pace / behind). Benchmarking with colleagues. 8. Visualization and Roles “Traffic lights” (green/yellow/red) for key metrics relative to norms/plans; progress scales; trend graphs; mobile adaptive. Roles: CEO — everything; COO — entire funnel and managers; team lead — their team; manager — their metrics and position relative to colleagues. 9. Reports and AI Automated reports on schedule (daily summary, weekly report) in the dashboard and/or messenger. Free-form queries (“how has CPL from Meta changed over 2 weeks?”) — LLM over the repository. Alerts in the red zone and according to the rules from points 5–6. 10. Technical Expectations and Staging Repository (PostgreSQL/BigQuery or equivalent) + ETL: Kommo webhooks + periodic synchronization (15–60 min). Frontend: custom or BI tool — propose with justification; requirements for roles, traffic lights, forecasts, and AI queries must be implementable. Stages: (1) audit and metrics map → (2) MVP: Kommo + Stripe + Meta, funnel, traffic lights, roles → (3) deal cycle, early warning, additional payments and plan → (4) SEO, AI reports, alerts → (5) new advertising channels. Payment is staged, with a demo for each stage. In the response, indicate: similar projects (end-to-end analytics), stack with justification, timeline and cost estimates by stages, monthly ownership cost (hosting, tokens, licenses).