Budget: 3000 UAH Deadline: 4 days
I will do contact parsing. Python + Selenium/requests. It is necessary to know the source (which websites, social networks, directories) and which fields to collect. The result in CSV/Excel. Send the details in DM.
Отримати базу моб. ном. та імен (якщо є) користувачів, які цікавляться побутовою технікою, водоочисними системами та кулерами.
OLX Україна
Маркетплейси: Rozetka (бажано), Prom, Hotline (як бонус)
Інші відкриті джерела, де є релевантна ЦА
Географія: великі міста та передмістя України (Київ, Львів, Дніпро, Одеса, Харків тощо)
Вік: 25–55 років
Стать: переважно чоловіки
Достаток: середній та вище
Інтереси:
Побутова техніка
Фільтри для води
Зворотний осмос
Кулери, пурифайєри
Супутні товари для кухні
Моб. ном. тел.
Ім’я (якщо є)
Тип інтересу: продавець / покупець / шукає / продає товар
На старт — 200 контактів для тесту
Після перевірки якості — збільшення обсягу
Таблиця Google Sheets / Excel
Поля: ім’я | номер телефону | джерело | посилання | короткий опис інтересу
Дані мають бути актуальними
Тільки реальні користувачі, без ботів
Телефони перевірені (не дублікати)
Тестова вибірка: 2–3 дні
Budget: 3000 UAH Deadline: 4 days
I will do contact parsing. Python + Selenium/requests. It is necessary to know the source (which websites, social networks, directories) and which fields to collect. The result in CSV/Excel. Send the details in DM.
Budget: 27000 UAH Deadline: 14 days
Hello! I am the project manager of Business Atlas. Your task is our profile: my experience in process automation allows us to gather a quality database. That is why for data collection, we should choose our solution:
• Instead of manual copying, we will set up a script on Make/n8n that will automatically extract data from the necessary sources.
• We will use AI to check relevance and determine the type of interest (seller/buyer), based on our experience in the case of "AI search for B2B companies and relevance verification."
• The system will automatically check numbers for duplicates and enter them into Google Sheets according to your format, similar to the case of "Automatic lead qualification in Google Sheets via Make."
• You will receive a ready table with structured data (name, phone, source, description), ready for calls or mailings.
We have implemented over 15 complex ecosystems for companies like Genesis, Ajax-IT, and Convert-lab.
Which of the sources (OLX or Rozetka) should we focus on when preparing the test sample?
Budget: 1000 UAH Deadline: 1 day
Hello, Ms. Lyudmyla! In what sense are you interested? As buyers? As dropshippers? Or something else? I will gather for you a database that is as large and up-to-date as possible. Let's make arrangements.
Budget: 5000 UAH Deadline: 3 days
Ready to discuss with you the work on creating a script for website parsing, the price is indicated.
Budget: 26999 UAH Deadline: 4 days
Good day! I am ready to complete this project. Extensive experience in developing various applications.
Budget: 2500 UAH Deadline: 3 days
Good day.
I am engaged in data parsing in Python. I can collect contacts from OLX and other sources in the required categories.
Budget: 2000 UAH Deadline: 3 days
Hello, Lyudmyla!
We are FlipFactory, specializing in data parsing and automation of contact collection. We have ready-made solutions for working with OLX, Rozetka, Prom, and other Ukrainian marketplaces.
What we offer:
• Automatic collection of contacts from OLX (sellers/buyers of household appliances, filters, coolers)
• Parsing Rozetka and Prom — extracting open data of sellers in the required categories
• Deduplication and verification of numbers — only unique, relevant contacts
• Ready Google Sheets table in your format (name, phone, source, link, description of interest)
We will create a test sample of 200 contacts in 3 days. After confirming the quality — we will scale the volume.
We use our own scripts in Python/Node.js with proxy rotation, which guarantees stability and relevance of data. Experience in parsing 50+ projects.
We are ready to discuss the details in private messages!
Budget: 900 UAH Deadline: 2 days
Hello, I am ready to complete your task, I will do everything clearly, qualitatively, and attentively. Please write in private messages to discuss the details. Thank you!
Budget: 1000 UAH Deadline: 3 days
Good day!
I professionally engage in data parsing and verification. I am ready to qualitatively collect a contact database from OLX, Rozetka, Prom, using proxies and API. I guarantee the relevance, uniqueness of the data, and the formation of a Google Sheets table.
Contact me in private messages for discussion!
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).