Internal CRM
Lead Tracker
A lead-ops CRM with roles, a call queue, appointments, invoicing and a client portal.
- Services
- App or CRM
- Automation
- Stack
- pnpm workspace, Fly.io, Vitest
- Updated
Context
Lead Tracker is the CRM an operations team works in. It holds the work queue, invoicing and receivables, and a portal for the business's own clients.
It is private software, so the picture on this page is a sketch, not a screenshot.
Problem
A lead-ops team runs on speed and clean handoffs. The people working the queue need the next item ready the moment one is done, and the people on the money side need to know what has been invoiced and what is still owed.
Different people need different views. Staff work the queue and the numbers, and the business's own clients sign in to a portal that shows only what is theirs.
Approach
We built it as a pnpm workspace with three packages: the web app, a worker, and the shared code both of them import. The worker runs on Fly and takes the slow jobs off the request path, so the screens stay quick.
Roles decide what each person sees, from the work queue to receivables. One codebase serves four web projects, so the rules live in one place instead of drifting apart across copies.
The test suite is the safety net: over 500 test files, so a fix in one corner of the app cannot quietly break another.
Outcome
Its codebase became our CRM chassis. The deal desk and the export CRM in our work both started from it rather than from an empty folder.
- Test files in its suite
- Over 500
- Web projects served from one codebase
- 4
Stack
- pnpm workspaceweb, worker and shared packages
- Fly.iothe background worker
- Vitestover 500 test files
Tell us what you are working on.
A few lines about your business is enough to start. We reply with questions and a plain next step.