Synas Labs · internal system
Lead Radar
The system Synas built for its own pipeline: signals, qualification, CRM, and follow-up on one connected data model, instead of chat threads and spreadsheets.
What problem does it solve?
- Promising leads are noticed in many places and recorded in none of them.
- Nobody can say why one lead was prioritized over another.
- Follow-up depends on memory, so overdue leads go unnoticed.
What did we build?
- 01
Signals
An observed opportunity is recorded with its source, the pain, and the evidence, then promoted into a lead when it is worth pursuing. Automated discovery from public sources is designed but not connected yet. - 02
Qualification and scoring
Promoting a signal writes a point-in-time score snapshot with its rationale. Humans still decide whether to pursue. - 03
CRM and lifecycle
Company, contact, opportunity, and activity in one operating record, not trapped in someone’s inbox. - 04
Follow-up
One rule set plans the next follow-up when a lead is created, qualified, or sent a proposal, and overdue follow-ups surface for a person.
How does it work?
Lead Radar · pipeline structure
Internal buildSignal
- new
- promoted
Lead
- new
- needs review
- qualified
- discovery
- proposal
- negotiation
- won
- lost
- passed
Opportunity
- identified
- discovery
- proposal
- negotiation
- won
- lost
Actual status values from the Lead Radar data model. No client records are shown.
From signal to follow-up
- 01Signal
- 02Score
- 03Lead
- 04Opportunity
- 05Follow-up
What is it built with?
- Next.js and TypeScript
- PostgreSQL with Drizzle
- Role-based access, enforced on the server
- A tested follow-up rule set
What are the results?
This is a Synas-built system, so there are no client results to report. Results will appear here only when a client system can report real numbers.
What are the limits?
This is Synas’s own internal system. It is not a client project and not a product for sale. Automated discovery of signals, CRM sync, email, and calendar connections are not live.
Next step
Want something like this?
Start with a Workflow Audit on one workflow. We map it, show where it stalls, and tell you what to automate first.