# AutoLead – Beta Version Expectations

# AutoLead – Beta Version Expectations ## Project Overview AutoLead is an intelligent vehicle acquisition platform designed for professional used-car dealers. The objective is not simply to collect classified ads, but to help professionals identify the best purchasing opportunities faster and make better buying decisions. The Beta version is intended to validate the concept with real users before developing the more advanced versions (V2, V3, V4 and V5). --- # Current Status The project has already been started by another developer. Some components have already been implemented, including: * User authentication * Database structure * CSV import backend * Initial application architecture * Software Requirement Document (SRD) You will have access to all existing documentation and source code. The objective is to continue the project on a clean and scalable architecture. --- # Main Objective of the Beta The Beta must demonstrate that AutoLead can automatically collect vehicle listings, analyze them, and present them in a simple interface for professional users. The Beta is **not** expected to include every planned feature. The priority is to build a stable, reliable and scalable foundation. --- # Expected Features ### User Authentication * Secure login * User account management --- ### Vehicle Acquisition Initially through CSV import. The architecture must later allow multiple acquisition methods, including web scraping and APIs. --- ### Vehicle Database Store every imported vehicle with: * Brand * Model * Year * Mileage * Fuel type * Transmission * Price * Seller information * Publication date * Source --- ### Vehicle List Display all detected vehicles. Allow filtering and searching. --- ### Vehicle Detail Page Each vehicle should have its own detail page. The page should display: * Vehicle information * Photos * Seller information * Analysis * Contact button --- ### Favorites Allow users to save interesting vehicles. --- ### Seller Contact The user must be able to quickly contact the seller. --- # AutoLead Scoring Engine The scoring engine is the core value of AutoLead. Even if the Beta contains only a simplified version, the architecture must be designed to support future scoring. The scoring engine will eventually include six indicators. ## ICP Price Consistency Index Determines whether the asking price is attractive compared to the market. --- ## ICK Mileage Consistency Index Evaluates whether the mileage is coherent with the vehicle's age. --- ## IR Profitability Index Estimates the profit potential. --- ## IL Liquidity Index Estimates how quickly the vehicle could be resold. --- ## IC Confidence Index Evaluates the reliability and completeness of the available information. --- ## IRM Mechanical Risk Index Identifies known mechanical risks related to the vehicle model or engine. This feature can initially be simplified but must be anticipated in the application architecture. --- # User Experience The application should remain: * Fast * Simple * Intuitive * Professional A dealer should understand the quality of a vehicle opportunity within a few seconds. --- # Code Expectations I expect: * Clean architecture * Modular code * Reusable components * Well-documented functions * Maintainable code * Scalable database * Good naming conventions The Beta must become the foundation for all future versions. --- # Future Versions The project will continue after the Beta. Future versions will introduce: * Advanced scoring * AI-powered vehicle analysis * Automatic opportunity ranking * Smart notifications * CRM features * Multi-source vehicle acquisition * Dealer network management * Analytics dashboard For this reason, scalability is extremely important from the beginning. --- # Development Philosophy AutoLead should never replace the professional buyer. It should assist professionals in making faster and better purchasing decisions. Every feature should answer one of these questions: * Does it save time? * Does it increase profitability? * Does it reduce buying risk? If the answer is "no", the feature probably does not belong in AutoLead. --- # Communication I value transparent communication. If technical issues arise, I expect them to be discussed early. Regular progress updates are very important. My goal is to build a long-term relationship with a developer who believes in the project and can contribute to its evolution over the coming years. I look forward to working together.