📌 About the project
The company is engaged in the import of cars (USA, Korea, Europe, China).
In the sales department, there are about 60 managers, with up to 5000 leads per month.
The task is to automate the quality control of calls and lead scoring based on AI.
🎯 Project goal
To create a system that automatically:
— receives call recordings
— makes transcriptions
— analyzes dialogues according to specified logic
— assigns scores
— records the results in amoCRM
❗ Important: the result must be usable in business, not just a demonstration (MVP).
⚠️ IMPORTANT (to avoid misunderstandings)
— The scoring logic and evaluation criteria have already been formulated (will be provided)
— Not a "general analysis of calls," but a maximum accuracy matching the specified logic of 95% or higher
— The performer must assess the timelines considering this accuracy in advance
— Extending timelines after the project starts without objective reasons is unacceptable
🔧 WORK STAGES
The work is divided into stages with separate acceptance:
1️⃣ Stage 1 — Infrastructure and transcription: 5 - 7 days ($300).
- creating a server
- receiving calls from Ringostat
- transcription (OpenAI/ Claude.ai / Whisper or similar)
- transferring data to the system
✅ Result:
there are correct texts of calls
2️⃣ Stage 2 — Analysis and scoring, calibration of accuracy: 10 days ($500).
— determination:
• client needs
• objections
• quality of manager's work
• deal stage
• agreements
— implementation of scoring:
• call rating (0–100)
• overall rating for the manager based on the analysis of their calls
• lead classification (cold / average / warm)
❗ Acceptance criteria:
— analysis accuracy of at least 95% on the test sample
— compliance with the provided scoring logic
3️⃣ Stage 3 — Integration with amoCRM (up to 5–7 days) - ($800).
— recording results in the deal
— comments after the call
— filling in fields
4️⃣ Stage 4 — Logic of actions and signals
— recommendations: what to do with the client
— identifying problematic situations
— signals for the manager and ROP
Examples:
— selection not sent on time
— objection not processed
— client "cooled off"
5️⃣ Stage 5 — Dashboard and analytics (7 days)
The system should display:
📊 For ROP:
— manager ratings
— where clients are lost
— recurring mistakes and recommendations
— conversion by stages
📊 In breakdown:
— by department
— by branches
— by specific manager
⏱ With the ability to select the period:
day / week / month / quarter / half-year
📌 All data is updated automatically
📌 IMPORTANT REQUIREMENTS FOR LOGIC
The system must take into account:
— depth of client responses
— purchase timelines
— readiness for the next step
— behavior in dialogue
❗ Example logic:
— gave many answers + has a budget → warm
— does not respond → cold
— wants to come / check the car → signal
(detailed logic will be provided)
📊 Volume
Currently about 90,000 - 100,000 minutes of calls per month, but the staff is constantly growing and may increase to 300,000 minutes of calls per month
📌 Scaling
The pilot is launched in one department (Lviv) to check the correctness of the system's operation.
❗ Scaling should not require reworking the system from scratch.
The architecture of the solution must initially provide for operation with multiple branches.
In the case of a successful pilot, the system should be scaled to all branches without changing the logic and without additional payment for the scaling itself.
Discussion is allowed only for infrastructure costs (servers, API, storage), if they directly depend on the volume of load.
📌 REQUIREMENTS FOR THE RESULT (ultimately)
The work is considered completed if:
— the system works automatically
— data is correctly recorded in CRM
— scoring corresponds to the logic
— analysis accuracy ≥ 95%
— the system can be used in work
— the dashboard displays information correctly
📌 REQUIREMENTS FOR THE RESULT for the current task (now, at the intermediate stage)
- complete the first stages with the condition of transferring access, instructions to the server and resources needed for use
- stages 2-5 will be completed later, in separate tasks
📌 Who we are looking for
Not just a developer, but a person who:
— understands sales
— knows how to work with business logic
— does not complicate the system
— can explain in simple words, without complex terminology
— can assess timelines BEFORE starting work
📌 Additionally
We only consider performers who:
— are ready to work in stages
— fix timelines and results
— do not change timelines after the start without agreement
