A system is required that integrates client registration processes, task management, financial accounting, and analytics. The main focus is on automating routine tasks, minimizing manual input, and cross-auditing data. Notion (project and task management) Notion business logic is used as a central hub for tasks, deals, and reports. When a deal is created in Amo CRM, a task card is automatically generated in Notion. Volunteers and employees update task statuses in Notion → changes are synchronized with Amo CRM, their task statuses are changed through the Telegram bot interface.
Requirements: API integration: Fields in Notion: Task name, Status (To Do/In Progress/Done), Deadline, Responsible. Implement bidirectional data synchronization between Amo CRM and Notion, with the Telegram Bot delineation Delineation of rights: Volunteers see only tasks marked “Available to volunteers”.Financial data (income/expenses) is available only to managers.
Support is needed for the self-tour program, catalog database servers, and the online server. There are 5 database servers.
The client database has been collected over several years from various sources, so the phone numbers are recorded in different formats, one client exists under multiple IDs, cities are entered manually in different languages, and the region is almost never filled in. Because of this, it is impossible to properly segment the database. What needs to be done: 1. Database audit (paid separately, first stage). How many cards, how many phone numbers are out of format, how many duplicates, how many unique city entries. Based on the results — a refined estimate of the remaining work. 2. Standardization of phone numbers. All numbers should be brought to the format +380XXXXXXXXX. Numbers that cannot be unambiguously recognized should not be deleted or guessed, but listed separately. 3. Merging duplicates. Rule: one phone number = one client ID. At the same time, one client can have an unlimited number of numbers. Order history, emails, addresses, tags, and custom fields must be preserved. 4. Parsing cards that have many numbers "attached" to them. 5. Cities and regions. Names of settlements — from a single directory in Ukrainian (API of Nova Poshta or KATOHTG). The region must always be filled in so that all clients from Kyiv and the region can be exported with one filter, not separately for Brovary, separately for Irpin, etc. 6. Protection against re-contamination: normalization of phone and city at the input (website forms, integrations, manual entry) + regular background checks of new entries. Requirements: — practical experience with the SIMLA / RetailCRM (v5) API: exporting, updating, merging cards, request limits; — experience with data deduplication tasks; — understanding of Ukrainian address directories. Working conditions: full backup before any changes; initially a dry-run with a report on planned changes for approval, and only then launch on the live database; log of all operations with the possibility of rollback. No irreversible deletions without approval. In your response, please include: — timelines and cost
It is necessary to compile a large and up-to-date database of contacts of Ukrainian scientists, educators, researchers, doctoral candidates, and graduate students using only open sources. The result should be in Excel or CSV format and contain at least full name, email, place of work (university or research institution), position, and a link to the source from which the contact was obtained. It is essential to minimize duplicates and, if possible, verify the validity of email addresses. For data collection, official websites of universities and research institutions, faculty profiles, department pages, institutional repositories, journals on the OJS platform, ORCID, OpenAlex, Google Scholar, ResearchGate, Crossref, PDFs of scientific articles, as well as other open academic resources can be used. The use of automation (parsing, API, Python, etc.) is encouraged if it does not violate the rules of the respective services. The main goal is to gather the most complete database of contacts from open sources.
A centralized server system for collecting and storing data from Planfix, 1C, Meta Ads, and Google Ads is needed, as well as a web dashboard for displaying and analyzing this data. All data, change history, calculations, and aggregated metrics must be stored exclusively in the server database. The dashboard should not store or duplicate business data. It must retrieve the necessary information from the server database via API according to user requests and display it in the form of KPIs, charts, tables, and detailed reports.
We are looking for support for a project based on Yii , we need to make edits and improvements to the database, there is partially a connection with the previous contractor .....................