Skip to content
Sales Tooling Let’s talk
Sales Tooling

Executive Performance CRM

Lightweight CRM for a field sales team: visit logs, follow-up dates and pipeline status in an Android app and a web dashboard, replacing a WhatsApp group used as a system of record.

ReactNode.jsAndroidFirebase
Executive Performance CRM — Sales Tooling case study by Chetan Sharma
Client
Services business, Delhi NCR (via NodeAscend)
Year
2025
Role
Full-stack and Android build
Type
Web App
The brief

What needed solving

Every conversation lived in chat, so nothing could be reviewed later. Managers could not tell who had been called on, what was promised, or which lead had gone quiet for eleven days — because none of it was written down anywhere queryable.

Approach

How it was built

(01)

Designed the entry form first, from the salesperson's side of the table: three taps to log a visit, photo attached, next follow-up date set by default.

(02)

Everything the field does offline queues on the device and syncs when the network returns.

(03)

The dashboard reports on the log, not on promises — pipeline movement, days since last contact, and visits that never turned into a follow-up.

(04)

Deliberately small: no modules for things nobody asked for, because an unused CRM is worse than a group chat.

Outcome

What changed

The group chat stopped being the record. Follow-ups are dated, visible and chased; and the weekly review meeting reads a screen instead of arguing from memory.

LoggingThree taps, works offline
ReviewPipeline and staleness on one screen
AdoptionUsed by the field team without policing
Field workflow designReact dashboardNode.js API with Firebase authAndroid app for visit loggingOffline queue and syncWeekly report views
Process

The same six stages,
every project

(01)

Discovery

Clarify the goal, users, constraints, current systems, success measures, and delivery risks.

(02)

Architecture

Choose the right structure, integrations, data model, security boundaries, and technology stack.

(03)

Design

Map important journeys and responsive states before expensive decisions are locked in.

(04)

Development

Build in reviewable milestones with clean code, documented decisions, and visible progress.

(05)

Testing & Launch

Validate functionality, performance, accessibility, security, and production readiness.

(06)

Support & Improvement

Monitor real use, resolve issues, and prioritize improvements using evidence.

Have something similar in mind?

Tell me the outcome you need and the deadline you are working to. I will tell you honestly what is possible.