Contact person: Business Client

Phone:Show

Email:Show

Location: Argentina

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"**MVP Development Specification**

**Goal:**
Develop a **minimum viable version (MVP)** of a platform designed to connect **repair professionals (technicians)** and **field agents (“walkers”)** who visit B2B locations (cafes, bars, rental properties, hotels, etc.).

The system must be **ready for scaling** and future integration of AI modules, but at this stage — only the **core business logic** should be implemented.

---

### **General Development Parameters**

**Timeline:** 3 weeks
**Budget:** up to **$2,000**
**Technologies:** Node.js / Python backend, PostgreSQL or Firebase, Telegram Bot API, Web ([login to view URL] or React), scalable rest api.
**Infrastructure:** AWS / Vercel / Railway (developer’s choice).
**Architecture style:** Clean modular structure, allowing new modules to connect via API hooks and WebSocket events.
**Interface language:** English (localization support to be added later).

---

### **1. Core MVP Modules (Phase 1)**

#### 1.1. User Registration & Roles

* **Technicians:** Registration, Telegram verification, basic profile (name, category, city, photo, experience).
* **Field Agents (“Walkers”):** Separate registration, requires manager approval.
* **Admin Panel (CRM Core):** User management, leads, and statuses.

#### 1.2. CRM Core

* Lead management: create, update status (new / in progress / completed / rejected).
* Lead assignment to technician or walker.
* Fields: object type, address, description, photo, client contact.
* Action history (log tracking).
* Report export (CSV / Google Sheets).

#### 1.3. Telegram Bot

* Registration for technicians and field agents via bot.
* Receiving and confirming leads.
* Notifications: new leads, status updates, reminders.
* Built-in mini CRM panel for agents.
* Inline buttons support (e.g., “Accept Lead”, “Postpone”, “Close”).

#### 1.4. Landing Page + Application Form

* Simple landing page (React/[login to view URL]) describing the platform.
* Application form for technicians (“Apply for training / onboarding”).
* Integration with CRM.

---

### **2. Field Ops Modules (v1.0)**

#### 2.1. AI Route Planner (simplified version)

* Route generation for visiting businesses by category (cafes, rentals, bars, etc.).
* Manual tagging: visited / closed / interesting.
* Simple map interface (Google Maps API).

#### 2.2. AI Lead Logger (v1.0)

* Meeting log form: photo, notes, contact person, status.
* Auto-sync with CRM.
* Built-in note templates.
* *Note:* ai logic will be added later — for now, only the architecture and mock api endpoints are required.

---

### **3. Integrations & API**

* **Telegram Bot ↔ crm** (via rest api).
* **Field Ops Modules ↔ CRM.**
* Predefined (inactive) API endpoints for future modules.

---

# **4. Admin Panel (v1.0)**

* Dashboard with leads, users, and basic statistics.
* Ability to manually add technicians and walkers.
* Activity report for agents (meetings, leads, successful deals).

---

#**5. ui/ux**

* minimalistic, clean, and light interface.
* Mobile-responsive design.
* In Telegram: focus on simplicity — buttons, short forms, clear notifications.

---

### **6. Future Architecture**

* All data and APIs must be structured with scalability in mind.
* Modular design — each component should function as a standalone or easily extractable microservice.

---

### **7. Expected Deliverables (after 3 weeks)**

* Fully functional **Telegram bot** for technicians and walkers.
* **Admin panel** for lead and user management.
* **Landing page** with submission form integrated into CRM.
* **Basic route and lead logging system** for field agents.

---

### **8. Reserve / Future-Ready**

* Architectural space for future **AI integrations** (no implementation required at this stage).
* Ability for quick deployment and updates." (client-provided description)