As a result, all agreed functionality works correctly, and the outcome meets expectations. I am satisfied with the collaboration.
Budget: 27000 UAH Deadline: 14 days
Vadim, I see here not just automation, but a working tool for daily use: rotation, scheduler, monitoring, and Excel synchronization need to work without manual adjustments. I have already done Python automation, parsing, and integrations with databases and external services, so I will quickly dive into your MVP logic, Playwright, and SQLite. I will pay special attention to universal categories and queue stability. I am ready to discuss details and risks.
Budget: 27000 UAH Deadline: 14 days
Look, there's a nuance here - if stage 1 is already working and the code can be expanded without rewriting the foundation, then 27,000 UAH and 12-14 working days seem like a reasonable estimate for stage 2. If after the review it turns out that the working version relies on temporary solutions, I would simplify things - a short technical check of the code within the marketplace, then a final breakdown by modules.
Regarding implementation, I wouldn't complicate it - separate services within the application for rotation, scheduling, URL monitoring, account groups, and Excel synchronization. Playwright works through saved profiles, SQLite stores statuses and history, and PySide6 displays the queue and errors in a way that the manager sees not magic, but a manageable tool. It seems to me that the main risk is not in the buttons, but in the stability of accounts, limits, and the behavior of Bazoš.cz.
From similar experience Ingello
> https://business.ingello.com/forma-bpm - automation of business processes, statuses, queues, rules, and action logs
> https://business.ingello.com/forma-crm - accounting interfaces, roles, filters, working tables
> https://business.ingello.com/vorfahr - indirectly close in automating product scenarios and system logic
The main profile for such systems - https://systems-fl.ingello.com
What I need from you is the code for stage 1, a test Excel file, a set of test accounts, proxies if they are used, Czech PSČ for probing Bazoš.cz, and a list of categories that we consider mandatory for acceptance. Access can be provided within the marketplace rules.
I want to clarify 2 things, so we don't play architectural shamanism =)
> does stage 1 already have stable session storage for accounts or does this need to be strengthened?
> for sold and inactive, do we definitely delete rows from Excel or is it better to mark them with a status by default?
Budget: 27000 UAH Deadline: 7 days
Hello, I worked on a Desktop application for automating ads on OLX using Python + Selenium, where we processed over 500 ads daily with rotation across 15 accounts and an automatic schedule. It is very similar to your Bazoš.sk project with the same challenges of account management!
I am curious if you plan to integrate a proxy system to work with different regions of Slovakia, considering you use postal codes for localizing ads?
I suggest we get in touch; I will provide you with free technical consultation and we can outline a development plan + I will tell you about my team!
Budget: 26999 UAH Deadline: 13 days
Good day.
I have read the specifications in full. We have experience with similar projects.
The stack Python + Playwright + PySide6 + SQLite + Excel is our specialty. We have done automation with anti-bot circumvention and multi-accounting on several projects.
A few points regarding implementation:
Schedule. APScheduler is suitable, but for PySide6, QTimer is better for the main loop plus a separate thread for publications. It does not block the UI during the bot's operation.
URL monitoring. When checking, it is important to distinguish between types of inactivity: removed by moderation, removed due to time, temporary network error. This helps the manager understand the reason.
Universal engine. Mapping category/subcategory through a separate JSON or YAML file, without recompilation. The manager can add new subcategories themselves.
Excel sync. Matching through product_id as the primary key, title as fallback. When writing via openpyxl, preserving the file formatting.
Limit of 50 ads. In addition to the log, it would be good to make push notifications in Telegram or email to the manager, so they don't have to wait until they open the app.
Probe Bazoš.cz is ready to be done in parallel with the main development.
Before starting, I am ready to show a prototype of one block (schedule or URL monitoring) so you can see the approach to the code.
I await your message in private.
Budget: 27000 UAH Deadline: 14 days
The task is clear: to expand the MVP into a full-fledged production tool with rotation, a scheduler, monitoring, and two-way Excel sync using Playwright + PySide6 + SQLite.
The stack is familiar, I will implement all modules from Stage 2: rotation with intervals per account, reserve status, control limit of 50 listings, scheduling in two modes, status monitoring, universal category engine.
12–14 working days, 27,000 UAH.
Is there already a database schema and UI mockups from the first stage, or are we starting from scratch?
Budget: 27000 UAH Deadline: 3 days
Hello! Your project looks very interesting. I am ready to start working immediately and ensure high quality.
Budget: 27000 UAH Deadline: 12 days
Good day! I develop in Python, have worked on similar projects with React/Node.js, and am ready for collaboration.
Budget: 27000 UAH Deadline: 14 days
Hello. Basically, everything described will be implemented with the specified technologies, but it is still necessary to familiarize yourself with the code before execution to avoid wasting time if the deadlines are critical.
Budget: 27000 UAH Deadline: 14 days
WELL, it’s more like this - for the deadline of 12-14 working days and a budget of 27,000 UAH for stage 2, this looks realistic.
I would simplify it - bring the MVP to a working manager tool through separate modules for rotation, scheduling, monitoring, account groups, synchronization with Excel, and a universal engine for simple categories of Bazoš.sk.
An important nuance I see - with a limit of 50 active listings, the bot should not delete old publications by itself, but should stop the queue by account and show a clear log.
From my feelings, the main risk area here is not the interface, but the stable automation of Bazoš forms, the statuses of listings, and the careful matching of Excel by product_id.
> I will clarify 2 points
> Is the Czech PSČ for probe Bazoš.cz already available, or will it need to be obtained before the start of the check?
> In Palets.xlsx, is product_id present for all rows, or do some products still need to be matched by title?
> Similar cases Ingello
> https://business.ingello.com/vorfahr - close in terms of operation automation, queues, and publication logic through external services
> https://business.ingello.com/forma-bpm - close in terms of statuses, workflows, logs, and task management for the manager
> https://business.ingello.com/prime-eva - indirectly close in terms of product data, integrations, and operational automation
Access to test accounts Bazoš.sk, proxies, the original Excel file, and the current MVP version are needed.
The main page of the team - https://systems-fl.ingello.com
Overall, it’s fine, we don’t need to complicate things - first, we close the stable stage 2, and we leave Bazoš.cz as a separate confirmed stage after the probe =)
Proposals concealed
Proposals are currently absent
Current freelance projects in the category Bot Development
I need a program that will send messages to our database of clients' phone numbers (or emails). With its own proxy. It can be Viber, or Telegram, or email. The program needs to be installed on my computer. (I am waiting for your offers regarding the price.)
Good day, it is necessary to set up automation for reminders to people regarding the auto-webinar with automatic changes of dates and times of the auto-webinar. That is, there is a landing page with the date and time of the auto-webinar, the information should be sent to ManyChat, and ManyChat should send the corresponding reminders one day, 6 hours, 2 hours, 1 hour, and at the moment of the start of the auto-webinar.
Development of a Telegram Mini App (store) with CRM and Nova Poshta integration It is necessary to develop a Telegram Mini App (store inside Telegram).Main functionality A catalog with approximately 20 products is needed. For each product: photo; name; description; price; model selection; color selection; quantity. Order processing The client must have the ability to: view the catalog; add products to the cart; change the quantity; place an order; enter: name; phone; city; Nova Poshta branch number; payment method; order comment. CRM All orders need to be automatically transmitted to the CRM via API. It is preferable that the integration is universal and in the future, the CRM can be changed without a complete redesign of the project.Nova Poshta Integration with the Nova Poshta API is needed or data transfer to the CRM if the creation of the shipping document will be done by the CRM itself.Administrator A simple administrator mode is needed: adding and editing products; changing prices; changing stock levels; adding new colors or models. Important The project must work as a Telegram Mini App (not a regular bot with buttons). The code, database, and all access after the completion of work must belong to me. The architecture must allow for additional features to be connected in the future without a complete redesign. Please inform: Estimated cost. Completion time. What technology stack you plan to use. Do you have experience in developing Telegram Mini Apps and integrating with CRM and Nova Poshta API.
I'm looking for an experienced Python developer who can conduct a full audit of the existing project, fix errors, and bring it to fully stable operation. If necessary, a complete redesign of the project architecture or writing a new implementation while preserving all necessary functionality is allowed. What I will provide The source code of the current bot. A video demonstrating how the bot should work. A complete technical specification with the logic of operation. Main task The goal is to restore the stable operation of the bot and ensure the execution of the full scenario without failures. If the current architecture cannot be effectively fixed, a complete redesign of the project is allowed. The main objective is not to preserve the existing code but to obtain a fully functional, stable, and maintainable product. What needs to be done 1. Conduct a project audit Before starting work, it is necessary to: study the existing code; identify the reasons why the bot stopped working; assess what can be fixed and what is more reasonable to rewrite. 2. Restore all functionality After the work is completed, the bot should correctly execute the entire scenario: registration of a new account; confirmation of login via code from email; authorization; execution of the scenario according to the technical specification; completion of work; transition to the next account. All stages must work automatically without manual intervention. 3. Fix existing errors It is necessary to eliminate any errors related to: authorization; receiving the confirmation code; unstable operation; freezing; unexpected program termination; errors after website updates; incorrect exception handling. 4. Make the project resilient The bot must: correctly handle errors; not enter infinite loops; automatically terminate unsuccessful scenarios; correctly continue operation after non-critical errors; maintain clear logs. 5. Control panel It is necessary to preserve or redesign the control panel. It should allow: to start and stop operation; to change necessary settings; to view the current status; to view the log of operations and errors. The interface should be clear and stable. 6. Code Code requirements: clear project structure; separation of logic into modules; possibility of further support. 7. Compatibility The project must run on a modern version of Python. The contractor must provide a complete list of dependencies and instructions for running. 8. Result verification Before handing over the project, the contractor must demonstrate a fully working scenario on video: project launch; completion of the full cycle; absence of errors; correct operation of all functions. What to provide after completion source code; all modified files; instructions for running; list of dependencies; video demonstration of operation; brief description of the changes made. Important The work is considered completed only after all functionality described in the technical specification and demonstration video works stably without critical errors. If during the audit it turns out that the current project cannot be effectively fixed, a complete redesign is allowed while preserving all necessary functionality. When responding, please indicate immediately: experience with Python; experience in browser automation (Playwright, Selenium, or similar tools); experience with REST API; cost of work; estimated completion time.
A Telegram bot needs to be developed in Stand Pulse for the client's test. The test has 5-7 questions with 5-7 answer options. Based on the client's answers, the bot will calculate scores and provide a result (6 options).