Budget: 6000 UAH Deadline: 1 day
Hello, Karl!
Recently, I implemented exactly such a bot for monitoring and managing subscriptions. You can check out this case: https://freelancehunt.com/showcase/work/telegram-bot-dlya-dobavleniya-zakryityiy-kanal/1887337.html
Also, if you have a sole proprietorship, I suggest, as in the case, to remove the manual payment verification mode and do everything automatically.
Feel free to reach out, I would be happy to discuss your project in more detail.
Budget: 2000 UAH Deadline: 4 days
Hello! I have reviewed the project, I can complete it, I have the necessary experience.
Budget: 8000 UAH Deadline: 10 days
Good afternoon, I will gladly take on the development. Do you have any preferences regarding the admin panel stack, or should I choose at my discretion? Feel free to reach out. The price and deadlines are approximate.
Oleksandr Stinkovyi
Winning proposal- Projects 118
- Rating 5.0
- Rating 9 922
Budget: 2000 UAH Deadline: 1 day
Hello.
I am developing bots for Telegram on NodeJS. I am ready to take it on. Write to me, we will discuss.
Budget: 5000 UAH Deadline: 5 days
I can complete your order in Python or NodeJS, all according to your specifications. I may not have many reviews, but I will approach your order very responsibly and will do it in the shortest time possible and with the highest quality.
Budget: 5000 UAH Deadline: 7 days
Hello!
We are ready to offer the development of a simple and effective Telegram bot for managing subscriptions. The bot will include manual subscription issuance, payment processing, link generation for access, and automatic removal of access upon subscription expiration.
Bot functionality
1. Subscription management
Manual subscription issuance:
The administrator confirms the payment and manually issues a subscription specifying the duration (number of days).
Link generation:
Automatic creation of personal links for access to groups/folders.
Support for settings to bind the link to a specific subscription.
Access removal:
Upon subscription expiration, the bot automatically removes the user from the group/folder.
2. Admin panel
Administrator panel:
View active subscriptions (username, group, validity period).
Ability to manually extend, modify, or cancel subscriptions.
Notifications about subscription expirations for administrators.
3. Payment management
Manual processing:
The user sends a screenshot of the payment confirmation.
The administrator verifies and confirms the payment through the admin panel.
4. Ease of use
Interface:
Several buttons for main functions:
"Confirm payment."
"Create subscription."
"View active subscriptions."
Intuitive process for users and administrators.
Technical implementation
Modular architecture:
Subscription issuance.
Access management.
User data processing.
Mechanics:
Using the Telegram Bot API (for example, with libraries like aiogram or pyTelegramBotAPI).
Simple database (SQLite or JSON) for storing subscription and access data.
Hosting:
Deployment on VPS/Docker for stable operation.
What you will receive
A ready-made Telegram bot with the described functionality.
Configured and deployed bot on the server.
Documentation for working with the bot.
The source code includes comments to simplify further modifications.
We are ready to discuss the details of your project and offer an optimal solution. The bot will be as simple to use and reliable in operation as possible.
- Projects -
- Rating -
- Rating 363
Budget: 4000 UAH Deadline: 5 days
Hello!
I am engaged in the development of Telegram bots using Python aiogram3.
My portfolio: Freelancehunt
Write to me, we will discuss the details of the order, I will complete the work in a short time. I will also help set up the bot on permanent hosting.
Budget: 4400 UAH Deadline: 2 days
I will create a Telegram bot for managing subscriptions. The bot will support multiple tariff plans, with the possibility of manual payment processing. After uploading a payment screenshot, the administrator confirms the payment and manually grants access. The bot automatically removes participants from channels after the subscription period expires. Link generation for access will be built-in, possibly with replacement for folders for convenience. The interface is simple and user-friendly, perfectly suited for managing subscriptions without unnecessary complexities.
Budget: 1000 UAH Deadline: 1 day
Have you published this ad 2 times?
I have already responded to another one.
=============================
Budget: 10000 UAH Deadline: 7 days
Hello. I have extensive experience in developing Telegram bots. I am ready for collaboration.
Budget: 5000 UAH Deadline: 5 days
Hello.
We are engaged in software development, creating websites from scratch, as well as their refinement.
We work with: WordPress, 1C, Opencart, Shopify, WIX, Python, JavaScript, C++, C#, Unity 3D, SQL, Microsoft SQL Server, WPF, WinForms.
We have experience in: System programming, Project management in development, Information security, Game programming, etc.
We will complete your work, regardless of its complexity.
After the work is completed, we offer project support for 14 days.
We look forward to collaborating!
Budget: 5000 UAH Deadline: 10 days
Ready to complete your task, I will create a bot in Python. I will write in Python, and I will also help set it up on the server if needed.
Budget: 4000 UAH Deadline: 5 days
Good day
I have implemented such TG bots multiple times
I created them using python aiogram
I am ready to help
Budget: 5000 UAH Deadline: 3 days
Good afternoon. I will write a Telegram bot in PHP. I have my own bot, but it controls one group. You have several, so I don't think it will be simple and there will be several buttons.
Budget: 4000 UAH Deadline: 7 days
I will write a bot for you in nodejs and host it. Feel free to contact me.
Budget: 5000 UAH Deadline: 5 days
Hello, Karl!
I specialize in developing Telegram bots and I am ready to create a simple and effective bot for managing subscriptions. I will solve the problems of manual processing of subscriptions and payments, provide the generation of links for sign-ups and access control. I will also implement an admin panel for checking subscriptions. I guarantee high-quality implementation in a short time.
Let's discuss the details!
Budget: 1500 UAH Deadline: 2 days
Hello!
I have extensive experience in developing Telegram bots based on the Python language and the aiogram library. I am familiar with all the specifics of this work.
I guarantee full support. From development to uploading to hosting and further maintenance.
I would be happy to collaborate!
Budget: 3000 UAH Deadline: 2 days
Good evening, I am ready to complete your task quickly and efficiently, I have extensive experience in bot development. Please write to me in private messages, we will discuss the details. I will be happy to help you)
Budget: 5999 UAH Deadline: 2 days
Good day. I have already developed a nearly identical bot, I can make the changes you need and your project will be ready. Write to me, I will be happy to collaborate.
Budget: 2000 UAH Deadline: 3 days
Hello! I have reviewed the project and am ready to start working. I am sure you will be satisfied with the result.
Budget: 3000 UAH Deadline: 7 days
Hello Karl, I am a python developer with extensive experience in creating telegram bots, I am interested in your order. I suggest we move to private.
Budget: 1000 UAH Deadline: 1 day
Good afternoon, I am ready to implement your bot, waiting for your feedback.
Budget: 1000 UAH Deadline: 1 day
Good afternoon
Write that I am ready to complete
To perform these tasks
I will be happy to help
Proposals concealed
Proposals are currently absent
-
Aleksey Avdiyenko 4 January 2025А как сейчас дела в оккупированной орками Каменке? Я из Никополя, считай соседи, только город твари кошмарят ежедневно.
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).