Budget: 700 UAH Deadline: 1 day
Hello, I am ready to quickly and efficiently fix the problem for you. Write to me.
I will support your project and fix issues even after the completion is confirmed.Budget: 7100 UAH Deadline: 20 days
I will check the Python parser for Work.ua, find the reason for the slowdown and incorrect data collection, fix the parsing logic, error handling, delays, field structure, and stability of execution.
Do you have logs or examples of pages where it is clear which specific data the parser started to confuse: phone, name, job vacancy, company, city, or contact link?
The budget and deadlines will be discussed in personal correspondence after reviewing the code, examples of erroneous output, and the current method of running the parser.
Budget: 700 UAH Deadline: 1 day
Hello, I create parsers of various complexity, ready to promptly fix your parser and errors.
Budget: 700 UAH Deadline: 1 day
Good day. I have my own parser, I can take a look at yours. If necessary, I can provide my product instead of the non-working one. I will be able to inform you of the cost after familiarizing myself with the problem.
Budget: 1400 UAH Deadline: 2 days
👋 Hello! I'm ready to start working right now. I clearly understand the task and have successful experience in implementing exactly such projects (examples are in the reviews). I will complete the task today, quickly and without unnecessary questions. Let's discuss the details and get started! 🚀
Budget: 700 UAH Deadline: 1 day
Ready to promptly and qualitatively fulfill your order. I have experience working with similar projects, always adhere to deadlines and technical specifications. I would be happy to collaborate!
Budget: 2000 UAH Deadline: 5 days
Good day! We can do everything very quickly, I set a democratic price) I await your feedback. We will fix your parser)
Budget: 700 UAH Deadline: 1 day
Hello!
I have extensive experience in developing systems for parsing and processing data.
I am ready to review your parser and fix the error.
I suggest we discuss the details in private messages.
Budget: 700 UAH Deadline: 1 day
Hello! I am Volodymyr, the founder of the engineering agency Vaysed. The situation you describe is absolutely classic in the field of web scraping. The fact that your script worked perfectly for a whole week and then suddenly lost speed and started collecting incorrect information indicates that the platform reacted to your automated requests or updated its architecture.
The most likely reason for the slow performance is that the platform's anti-bot protection has been triggered. This often manifests as an artificial limitation on server response speeds for your IP address. Additionally, your script may be encountering a hidden CAPTCHA or browser check, causing it to hang while waiting for a response, wasting precious time at each step.
Another critical issue leading to incorrect data retrieval is a change in the HTML structure of the page. This directly indicates that the site's developers have updated the layout. They may have subtly changed class names or selectors, and now your parser continues to search for information using old coordinates, accidentally capturing adjacent text elements or completely empty blocks.
Furthermore, it is worth considering the possible dynamic loading of data. Contacts may have been moved to a separate API request that is activated only when simulating a click on the show number button. Also, do not rule out issues with the network layer: some of your proxy servers may have been blacklisted by the site, causing constant network timeouts and critically slowing down the overall execution cycle of the code.
My team faces similar challenges every day and knows how to work around them. We are ready to conduct a quick audit of your code, update outdated selectors, configure proper browser simulation, and stabilize the script's performance. You can evaluate our engineering approach in more detail on the official agency website https://vaysed.me/. Message me directly, and we will promptly fix your parser so that it works quickly and without errors again.
Budget: 1000 UAH Deadline: 1 day
Good day. I can take a look. I would be happy to collaborate, feel free to reach out!
Budget: 700 UAH Deadline: 3 days
Good day!
I am familiar with your task regarding fixing the parser errors in Python for Work.ua. I have experience with parsing and solving performance issues in scripts.
I am ready to quickly diagnose the problem, fix the errors in the parser, and ensure correct data collection.
Contact me to discuss the details.
Budget: 1200 UAH Deadline: 1 day
Hello. I have extensive experience in developing parsers. What specific problem are you facing now?
Budget: 800 UAH Deadline: 1 day
Hello, I have been writing parsers for about 10 years, I can help with yours. Feel free to contact me.
Hello, I have been writing parsers for about 10 years, I can help with yours. Feel free to contact me.
- Projects 7
- Rating 5.0
- Rating 1 945
Budget: 700 UAH Deadline: 1 day
Good day. I can help with your Work.ua parser.
Most likely, the problem arose due to changes on the Work.ua website, request rate limitations, or changes in the page structure. Therefore, the parser may have started to work slower and retrieve incorrect data.
To begin with, I need the parser code, an example of incorrect data, and several links where it is not functioning correctly.
Budget: 700 UAH Deadline: 1 day
Good day!
Setting up parsers is our specialized area, and the task is clear. "Worked for a week, then broke" is a typical situation, and the reason is usually one of the following:
Work.ua changed the layout/HTML → old selectors pull garbage (hence "incorrectly parses");
anti-bot/rate-limit was activated on your IP → hence "slow" (throttling, delays).
What we will do:
we will analyze the code and find the exact cause;
we will update the selectors for the new site structure;
we will configure proxies and delays to bypass throttling and restore speed.
If you provide the code, we will determine the cause specifically, without guesses.
Let's clarify: are you providing the parser code and do you have a proxy/Work.ua account?
Details about the project will be in private messages. We are ready to start the audit immediately.
Budget: 1000 UAH Deadline: 1 day
Hello! I can fix the error today or tomorrow. I have been working with parsers for a long time, send me the script and I will fix it.
Budget: 700 UAH Deadline: 1 day
Good day!!! What is the parser written in?????? Thank you!!!!!!!
Budget: 700 UAH Deadline: 3 days
Hello! I can complete your task. I have experience. Write to me and we will agree.
Budget: 700 UAH Deadline: 1 day
Hello
I can suggest how to properly modify the parser for faster performance.
Budget: 6500 UAH Deadline: 2 days
Good day! I specialize in Python automation and the development of robust web scraping systems. The problem you described is standard for Work.ua: the service may have changed the HTML structure or enabled protection against frequent requests, causing the parser to slow down and skip data blocks.
I am ready to promptly audit your code, update the selectors, and optimize the request handling (set up proper timeouts, error logging, or connect proxy rotation if necessary).
Since the task requires refactoring and guarantees stability, my minimum cost for such work is $100. In return, you will receive a reliable solution that won't break in a week. I am ready to complete the work within 1 day, waiting for your code for analysis!
Budget: 700 UAH Deadline: 1 day
Good day. I specialize in automation and parsing in Python. I can quickly debug your parser. Write to me, and we will discuss the details.
Budget: 800 UAH Deadline: 1 day
Good day, I can fix it, we can discuss everything in private, and I will start working right away.
Budget: 700 UAH Deadline: 1 day
Hello!
I have reviewed your task - I have relevant experience in similar projects, so I understand how to implement everything efficiently and without unnecessary delays.
I can start working immediately after we agree on the details. Upon completion, I will also assist with setup, deployment, and provide all necessary documentation.
I look forward to collaborating!
Proposals concealed
Proposals are currently absent
Current freelance projects in the category Data Parsing
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. .
It is necessary to perform parsing from Viber channels (Total number - 49 channels, about 80 thousand subscribers).
An independent service handler for Excel files is required for the existing microservices system. The task involves creating a reliable pipeline for receiving, validating, and transforming data from tables into a structured database format. Functional tasks: Development of an API based on gRPC for receiving processing commands and returning execution statuses. Implementation of file parsing logic: reading large volumes of data (XLSX), cleaning, type checking, and mapping to business models. Implementation of a data access layer (Repository/Unit of Work) for saving results in PostgreSQL via Entity Framework Core. Ensuring thread safety and efficient resource usage (especially when processing large files). Technical requirements: Platform: .NET 10. Architectural patterns: Dependency Injection, CQRS, modular project architecture. Communication: Strictly gRPC. Working with Excel: Use of efficient libraries (e.g., EPPlus, OpenXML, or similar of your choice). Modularity: Code should be organized so that the service is easily scalable and testable. Expected results: A fully functional microservice ready for deployment in a containerized environment. A clean codebase adhering to SOLID principles. Documented .proto files. Basic unit tests for critical data processing nodes. Candidate requirements: In your response, please specify: Your experience with .NET in microservices architecture. Examples of how you organize DI and modularity in your projects. Experience with Excel libraries in .NET. Willingness to work with gRPC contracts.
Good afternoon. I need a keyword parser that outputs results through a Telegram bot. How it should work: Automatic search on 4 websites for keywords that change from time to time. Search queries are sent every few minutes. The words are uploaded in the form of a .txt file. The Telegram bot should have buttons: start bot, stop bot, download file (downloads a file with active keywords), upload file (uploads an edited file with new words). The bot should ignore previously found results, i.e., it should not indicate the same ad twice. The result comes to the bot in the form of a link with a photo, but just a link is sufficient. P.S. searching websites without API, VPS with 6TB and 50 IPs are already available. For detailed information, please contact me via private message.
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).