API integration is OK

About the project and tasks We have a small sales department (sales department head + 2 managers) and a database of about 220 active clients. There is an urgent need to implement a simple CRM as an operational level so that managers can record calls, agreements, and statuses in the sales funnel in real-time, while management can see which clients are "stuck" at a certain stage. At the same time, we actively use AI analytics (Claude) for working with exports, reports, anomaly detection, and P&L analysis. Therefore, the CRM is needed as a clean data source from which quality exports can be generated. What needs to be done (Stage 1 — Implementation) Audit and solution selection. Finally determine the platform together with us. We are considering Ukrainian solutions (KeyCRM or SalesDrive) as integration with Ukrainian telephony and Nova Poshta is important. We are also open to considering Pipedrive. System setup. Creating a sales funnel, client cards, and configuring fields according to our specifics. Integrations. Connecting telephony, messengers, and Nova Poshta. Data import. Correct transfer of the existing client base (about 220 contacts) from current files. Training. A brief briefing for the sales department head and two managers on the rules for managing deals to ensure data cleanliness and quality in the CRM. Further tasks (Stage 2 — Support) Technical support and refinement of automations during the work process. Monitoring the correctness of data exports for further AI analytics. Who we are looking for A specialist with experience in implementing KeyCRM, SalesDrive, or Pipedrive (please include examples or cases in your response). A person who understands the principles of building sales analytics and can configure data exports without "garbage". A responsible specialist ready for long-term cooperation and project support. In your response, please indicate Your experience with KeyCRM, SalesDrive, or Pipedrive. Estimated cost and time for basic setup for our team (3 users). Whether you are ready to further administer the system and under what conditions.

Unpack and sort the database in XL format by cities Unpack and sort the database in XL format by cities Unpack and sort the database in XL format by cities

About the Company Trading company. We work with a product group of more than 2000 items across different categories.Current Situation Currently, the nomenclature is maintained in Google Sheets — data is consolidated by tabs (categories). Tab Structure: Product name Price groups: cost price, wholesale, retail Characteristics: weight, quantity per package, etc. Important: the number of columns varies for different product categories, as they have different characteristics.Why the Current Solution is Inadequate Google Sheets does not allow setting access rights at the level of individual columns. We need to: Grant users rights to view certain columns (for example, only cost prices) Grant rights to edit certain columns (for example, retail prices) While restricting access to other columns in the same tabWhat Needs to Be DoneMain Requirements Flexible Rights Management System Access at the level of individual columns (read/write) Assignment of rights by roles or users Management of rights without the involvement of programmers Support for Different Data Structures Different product categories have different sets of characteristics Adding new columns/characteristics without programming Independence from Developers Administration by internal staff Adding categories, columns, users — through the interface Integration with ERP Exporting current prices to our ERP system Export or automatic integration via API Data Analysis Using AI (preferably) Ability to analyze the entire nomenclature list Enrichment, verification, recommendations — if you have ideas, please describeExpected Result A working solution in which: The nomenclature is structured by categories with different sets of characteristics Column rights are flexibly configured (view/edit) Data is exported to ERP The team can manage the system independentlyWhat We Need from You When Responding Describe in general terms how you envision the solution: What tool/platform do you propose

A deep technical verification of three PDF files for authenticity and possible signs of editing or forgery is required. Not only a visual assessment of the documents is needed. The performer must have a good understanding of the internal structure of PDF files and be able to analyze: file metadata; PDF structure and individual objects; creation history and possible editing; software used; embedded fonts, images, layers, and other elements; possible signs of re-saving, conversion, modifications, or backdating of the document; any technical discrepancies that may indicate manipulation of the files. Based on the verification results, a clear written conclusion regarding each file must be provided, indicating the identified signs, risks, and limitations of the verification. We are considering specialists who have practical experience in digital forensics, PDF document analysis, metadata, or verifying electronic files for authenticity. In your response, please briefly describe your experience, methods, and tools that you use for such verification.

General information It is necessary to develop a simple minimalist web system, the main purpose of which is to maintain a client database, create appointments for visits, and automate the process of confirming visits via SMS, sending one-time links through the API from the service itself. The project is being developed in stages. In the first stage, it is necessary to implement only the basic functionality (MVP) so that the system can be used in real work. After launch and testing, it will gradually be expanded with new modules.Main functionality of the first stage User authorization; Client database; Creating and editing appointments; List of appointments (or a simple calendar); Switching between points of sale; Integration with the SMS operator via API; Sending SMS with any text or link for visit confirmation; Confirmation or cancellation of the visit by the client via a one-time link; Displaying the confirmation status directly next to the client's appointment. At the initial stage, instead of a full calendar, the use of a simple list of appointments by days is allowed. Each day should contain a chronological list of bookings indicating the time, client's name, service, employee, and confirmation status. Later, this list can be replaced with a full calendar without changing the system structure. The system must have the ability to switch between points of sale. Each point of sale has its own list of appointments (or calendar), but they all use a common client database.