Budget: 300 UAH Deadline: 5 days
Be glad to help.
- Projects -
- Rating -
- Rating 100
Budget: 150 UAH Deadline: 1 day
Good day, ready to cooperate.
Email: [email protected]
Have experience in this work, please contact us.
Budget: 500 UAH Deadline: 2 days
Hello, great experience in filling websites, please contact us.
Budget: 500 UAH Deadline: 1 day
Ready to perform!
by: cherrymilk2
Budget: 500 UAH Deadline: 3 days
Скайп krava_891
Budget: 400 UAH Deadline: 2 days
Good day . I will do it in a couple of days. Write to Ls we will discuss details)
- Projects -
- Rating -
- Rating 248
Budget: 400 UAH Deadline: 3 days
Hello to you! I love and know how to write parsers. Interested .
Budget: 500 UAH Deadline: 2 days
Ready to get to work.
My Skype: Iraira1026
Budget: 500 UAH Deadline: 3 days
Hello to you! Ready to discuss the details of the work. There is work experience. Examples of portfolio.
Budget: 200 UAH Deadline: 1 day
Hello, I was interested in your offer!
Ready to discuss flight work!
My portfolio is: Freelancehunt
My contacts:
Email: [email protected]
Skype: Alina_sone
Budget: 499 UAH Deadline: 1 day
Good day . I have a lot of experience with Excel. Ready to perform this work for you quality and in time. You are also ready to perform your tasks regularly.
Describe in detail what you need. Let’s start work. A good day. with respect for Volodymyr.
with respect to Vladimir.
HTTPS://www.freelancer.com/u/vkalach.html
HTTPS://freelance.ru/vkalach/
Budget: 499 UAH Deadline: 2 days
Believe it to the professionals.
I do it quickly and efficiently, I have experience!
Write in personal messages and we will discuss all the details!
- Projects -
- Rating -
- Rating 83
Budget: 500 UAH Deadline: 2 days
Ready to start. turn to
Budget: 500 UAH Deadline: 2 days
Good day . I have experience in filling websites, ready to work.
My portfolio:
Freelancehunt
Budget: 500 UAH Deadline: 2 days
Ready to perform.
Write in private, let’s discuss details.
Budget: 200 UAH Deadline: 3 days
Prepared for cooperation, period of 1-2 days
Budget: 500 UAH Deadline: 3 days
Hello to you! Ready to work.
- Projects -
- Rating -
- Rating 171
Budget: 500 UAH Deadline: 1 day
Good day ! Interested in your task. There is experience on various platforms. Email to [email protected], Viber 0933351675
Budget: 1000 UAH Deadline: 1 day
Hello to you. Ready to cooperate with you. Experience in work 3 years. Let’s write, we will discuss. Ready to start right now.
Budget: 499 UAH Deadline: 1 day
I will do it quickly and quality.
Budget: 500 UAH Deadline: 2 days
Hello, ready to do it.
Oleksandr L.
Winning proposal- Projects 384
- Rating 5.0
- Rating 13 143
Budget: 500 UAH Deadline: 2 days
Hello to you!
Please call me, I will be happy to cooperate.
_________________________________________
Scape: Prof-studio 1
Budget: 500 UAH Deadline: 2 days
Go to turn.
I do it.
Proposals concealed
Proposals are currently absent
Current freelance projects in the category Data Parsing
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;
Channel requirements: 1. Content language: Russian or Ukrainian (mixed RU/UA content is allowed) 2. Number of subscribers: At least 500 subscribers 3. Activity: The last post published no later than 32 hours ago 4. Comments: Comments must be open under the posts (through a group or embedded) 5. Quantity: Minimum 15,000 lines 6. Theme: War, news, politics, fights, trash/gore, sports, cars, crypto, fishing, and others Data to be collected for each channel Mandatory fields: Channel name username (link) Number of subscribers Theme (news, crypto, humor, business, etc.) Language (RU / UA / MIX) Date and time of the last post Presence of comments (yes) File format: Google Sheets / Excel (.xlsx)
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).