Budget: 1500 UAH Deadline: 1 day
Hello! I am ready to take on your project and will complete it urgently. I have extensive experience with similar tasks, so there will be no difficulties. If I have piqued your interest, feel free to write; I am happy to collaborate!
Budget: 700 UAH Deadline: 3 days
Hello!!!!
If we are working on p....rams and if this data is somehow actually available on the site, I can do it, so to speak, for a donation!!!
Funds for the account of unmanned systems, and you get the collected data!
I work for a minimum of 700.
I will summarize all received under the report.
rmrf - ..... Well, you got it)))
Oleg N.
Winning proposal- Projects 53
- Rating 5.0
- Rating 1 867
Budget: 700 UAH Deadline: 1 day
Hello! I am ready to complete your task, I have experience working with similar assignments.
Budget: 700 UAH Deadline: 3 days
Good day or Good evening!
I am ready to professionally extract a database (about 3000 contacts) from the logist pro website, including data from profiles. I have experience with web scraping, APIs, proxies, and exporting information to Excel.
Please message me for clarification on the details.
Budget: 700 UAH Deadline: 1 day
Good day!
I understand that it is necessary to download the database from the logist pro website using your account.
What I will do:
— I will analyze the data structure on the site and determine what queries need to be made to obtain the information.
— I will write a script for data parsing using Python and libraries such as BeautifulSoup or Scrapy.
— I will download information about 3000 profiles and save it in Excel format.
— I will ensure testing to guarantee the accuracy of the collected data.
The timeline for the work is minimal, as I am ready to work on the project actively and quickly. Always available and will do everything turnkey.
What specific information about the company do you want to obtain, besides the name and surname?
I will be happy to help you with the implementation of this project!
Budget: 1500 UAH Deadline: 2 days
Hello! I am ready to implement automatic data collection (parsing) from logist.pro. I will write a script in Python that will log in under your account, go through all ~3000 profiles, and collect clean data.
Budget: 1000 UAH Deadline: 1 day
Good evening. I am ready to gather a database. I develop parsers of any complexity. Feel free to contact me.
Budget: 2500 UAH Deadline: 1 day
Good day, I have been in web programming for over 9 years. I work with REST APIs, frameworks, and CMS such as Django, Laravel, Yii2, WordPress, OpenCart, CodeIgniter, etc. I am ready to complete the task. Reviews: Freelancehunt
Budget: 3000 UAH Deadline: 3 days
Good day. I can write a console parser in Python and download all profiles.
Budget: 5000 UAH Deadline: 2 days
I am a NodeJS developer. I am ready to take on this task. Write to me, we will discuss.
Budget: 1200 UAH Deadline: 1 day
Feel free to contact me. I will do it quickly and efficiently.
Budget: 2000 UAH Deadline: 2 days
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.
I look forward to collaborating!
Budget: 1200 UAH Deadline: 1 day
Hello! I can do it!!!!!!!!!!!
Feel free to contact me!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!-----+_+------!!!!!
Budget: 1500 UAH Deadline: 1 day
Good day! The task is clear, and it is technically feasible.
I will write a script that will simulate user actions to safely collect data from 3000 profiles without raising suspicions from the website's security system. The data will be exported into a clean Excel file with all the necessary fields.
A couple of clarifying questions:
1. Is there two-factor authentication (2FA) on the account?
2. Is there a captcha (bot protection) on the site when viewing a large number of profiles?
If everything is standard, I am ready to start in the near future.
Budget: 4500 UAH Deadline: 2 days
Hello. I can implement this project. If it's relevant, write to me, and we will discuss.
Budget: 700 UAH Deadline: 1 day
Good afternoon. I am ready to complete the task. I will export the data for all specified profiles into Excel. I can start immediately.
Budget: 1200 UAH Deadline: 2 days
Hello, I can complete your task. I have experience with data parsing, so I can load and format the data programmatically. I can do it in 2-3 days for a price of 1200 hryvnias.
Budget: 700 UAH Deadline: 1 day
Hello. I will complete everything quickly and efficiently. Write to me. Experience of over 6 years.
Budget: 1000 UAH Deadline: 1 day
Good day, I am ready to complete your task quickly and efficiently. I have extensive experience in creating various parsers. Please write to me in private messages to discuss the details. I would be happy to help :)
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).