01
Scattered leads
Contacts arrive through different channels and do not always enter a clear, prioritized queue.
Case study
PROGN
AI-assisted CRM with WhatsApp integration for clinics
My flagship product is a CRM for clinics that need to manage leads, qualification, conversations, WhatsApp, scheduling, tasks, reports, and automation in one controlled sales workflow.
Team inboxLead profileSales pipelineDaily dashboardAI and human supportReporting
This private system is shown through interface screenshots, workflow details, and fictional data to protect business rules and sensitive information.
Shows
A working CRM dashboard
Metrics, filters, and pipeline views come together so the team starts the day knowing where to act.
Solves
Clear follow-up priorities
Leads no longer live only in WhatsApp. Each one has a stage, source, lead score, and next step.
Why it matters
Decisions backed by operational data
Managers can see volume, bottlenecks, and opportunities before asking for follow-up or changing acquisition efforts.
Challenge
When sales run through WhatsApp, the operation needs structure
Leads arrive through WhatsApp, landing pages, and forms. Without a clear queue, the team loses context, priority, and the right follow-up timing.
02
Fragmented history
Conversations, follow-ups, and decisions remain buried in isolated messages or individual team members' memory.
03
Manual follow-up
Without connected tasks and scheduling, high-intent opportunities can go cold simply because no one followed up.
04
Limited visibility
The clinic knows inquiries are coming in, but cannot clearly see where the pipeline is getting stuck.
Solution
An AI-assisted CRM that connects WhatsApp with a visible sales workflow
PROGN brings conversations, the pipeline, scheduling, and AI-assisted intake together, making the next step clear before a team member takes over.
01
New lead arrives
A contact comes in through WhatsApp, a landing page, or a form and enters the CRM with a visible source, stage, and owner.
02
Qualification
AI-assisted intake helps organize intent, urgency, and context before a team member steps in.
03
Pipeline and conversations
The team tracks each lead by stage, conversation, task, promised follow-up, and sales priority.
04
Scheduling and next steps
As a lead moves forward, the workflow connects appointments, tasks, and follow-ups so nothing is forgotten.
Product screens
A dashboard, pipeline, conversations, and reports built for day-to-day operations
The screens below show the working CRM with fictional names, metrics, and conversations to protect customer information.
Operations dashboard
An at-a-glance view of lead volume, lead score, source, and distribution across pipeline stages.
- Helps the team prioritize contacts before opening every conversation.
- Surfaces bottlenecks in response needs, engagement, and overloaded pipeline stages.
- Turns disconnected WhatsApp activity into a daily management routine.
Sales pipeline
Organizes opportunities by stage, so the team can see which leads are new, qualified, in conversation, or close to booking.
- Each card includes enough context to choose the next action.
- The team can spot stalled leads without relying on memory.
- Managers can update stages, priorities, and ownership with more control.
Centralized conversations
Combines the contact queue and conversation history to preserve context when a lead moves from AI-assisted intake to the team.
- Reduces scattered screenshots and conversation history across phones.
- Shows source, summary, and lead score before a team member replies.
- Supports a clear handoff while preserving the human side of the conversation.
Reports and acquisition
Completes the workflow with metrics on channels, lead quality, and points where conversations lose momentum.
- Compares lead sources and scores to evaluate acquisition quality.
- Helps identify bottlenecks before increasing ad spend.
- Turns conversation activity into operational data for better decisions.
Features
Leads, pipeline, conversations, scheduling, tasks, and reports in one product
PROGN was built as a day-to-day operations tool, not just a contact database.
AI and WhatsApp
Automation that organizes the work without removing the human touch
AI supports intake and context. Team members remain responsible for negotiation, sensitive conversations, and important decisions.
01
AI-assisted intake
AI identifies intent, summarizes context, and helps the team understand the lead before responding.
02
WhatsApp as the main channel
WhatsApp becomes part of the sales workflow instead of sitting in a separate inbox with no operational context.
03
Human handoff
When a conversation needs judgment, negotiation, or personal attention, a team member steps in with the context preserved.
04
Quality controls
Automation supports the workflow, while the team remains responsible for rules, oversight, and the quality of each interaction.
Human handoff
The team steps in with history, intent, and the next action in view
The handoff keeps context intact when a conversation moves from AI-assisted intake to a team member.
01
Context preserved
Summary, stage, source, and conversation history follow the lead to the person responsible.
02
Clear ownership
The team knows who took over, what comes next, and when the follow-up needs to happen.
Reports and operations
Visibility to prioritize the day and improve the pipeline
Reports and dashboards turn conversations into a manageable routine by showing who needs attention, where work is getting stuck, and which tasks are overdue.
01
Daily overview
A prioritized queue shows pending follow-ups, open conversations, and opportunities that need action.
02
Pipeline metrics
Volume, bottleneck stages, stalled leads, and results by period are visible without a parallel spreadsheet.
03
Operational view
Owners, managers, and team members can see where the process is moving and where it needs adjustment.
Security and governance
Access controls, permissions, and careful public exposure
Because the system handles lead data, conversations, and sales operations, the public demo avoids sensitive implementation details and uses fictional data.
01
Role-based permissions
Access can separate conversation, management, and operations responsibilities when needed.
02
Operational traceability
History, status, and ownership reduce decisions that happen without a record in the pipeline.
03
Fictional portfolio data
Public screens replace real names, conversations, and metrics with safe examples.
04
Private business rules
Internal integration details, prompts, automation logic, and database structure are not exposed in the case study.
Tech stack
Technology structured for a real product
The stack supports the interface, backend, database, WhatsApp, AI, webhooks, reporting, and role-based operations.
Tech stack overview
The technology supports the day-to-day product experience, data, integrations, security, logs, and automation.
Next.jsReactTypeScriptNode/NestJSRelational databaseWhatsAppAI/RAGWebhooks
01
Built for daily operations
Screens support recurring work across the inbox, lead records, pipeline, schedule, tasks, and reporting dashboard.
02
Data and permissions
The system supports authentication, roles, history, traceability, and clear responsibility by user.
03
Integrations
WhatsApp, AI, webhooks, and automation connect lead acquisition, conversations, and next steps.
04
Safe product demonstration
Sensitive implementation details stay private, while the public demo uses fictional data and controlled workflows.
Next step
Does your clinic need a better way to manage leads and follow-up?
If your clinic is losing leads, relying too heavily on WhatsApp, or needs a clearer workflow for conversations, the pipeline, and scheduling, message me to see whether PROGN is a fit or custom software makes more sense.