<aside> 💡

The Vision: I built this because commercial CRMs have evolved into "Management Surveillance" tools. Solo entrepreneurs don't need clunky reporting bloat—they need a high-velocity, mobile-first ecosystem to track leads and ROI on the road.

</aside>

Project Overview

Role: Lead Developer / Product Architect Stack: Vanilla JS, Node.js, Firebase (Auth & Firestore), CSS3 Focus: Mobile-First UX, Real-Time Data Sync, Sales Analytics

The Market Gap

The Corporate Failure
The Market Gap
The Closed Loop Solution

The Stack: Why These Tools

Technology	Reasoning
Vanilla JavaScript (ES6+)	I chose NOT to use a framework initially to ensure I mastered DOM manipulation and Asynchronous patterns. This ensures the app remains lightweight and fast on mobile browsers.
Firebase Firestore	Chosen for Real-Time Synchronization. A lead added on a mobile device while on the road must be instantly visible on a tablet or laptop without manual syncing.
Firebase Auth	Security is paramount. I implemented JWT-based authentication to ensure that a solo entrepreneur’s lead data—their most valuable asset—is encrypted and private.
CSS Grid/Flexbox	Used to create a "Fluid UI" that feels like a native mobile app but runs in a web browser, avoiding the friction of an App Store download.

Technical Architecture

Cloud Infrastructure: Built on IBM Full Stack principles. Used a NoSQL Firestore schema (Users > UID > Leads) to ensure enterprise-grade data isolation.
Front-End Polish: Adhered to Meta Front-End standards, utilizing Advanced CSS Grid and Flexbox for a fluid mobile experience without the weight of heavy frameworks.
The Engine: Powered by a Node.js development environment. The logic handles asynchronous cloud handshakes using async/await to prevent UI freezing.

The Development Journey

Dec 15 – Dec 28, 2025: Architecture Phase:

The Decision: I moved from simple arrays to a Relational NoSQL Schema in Firestore.

The Logic: Structured the database for "High-Read Performance." I optimized the data so the "Pipeline Total" can be calculated instantly on the mobile home screen.

Bug Encountered: "Index Drift" in local arrays during testing.

The Solution: Transitioned to UUIDs. I learned that for a mobile app where connectivity might be spotty, having unique, non-sequential IDs is critical for data integrity.