Business project
LeadFlow
A module for qualifying trade-fair leads and running the B2B sales process – from the first call to a signed exhibitor form.
Context
Leads come from visitor registrations, forms and research. Consultants qualify them by phone and pass the promising ones to sales reps, who handle the offer, negotiation and the signed exhibitor form.
Challenge
A multi-stage process shared by three roles. Each role needed its own view of the same data, a clean handover without losing context, and visibility of where leads drop out.
Consultant
- To contact
- In contact
- Invitation sent
- Confirmed visitor
- Hot lead: handover
Sales rep
- Interested in offer
- Offer sent
- Negotiation
- Form signed
The manager sees both lanes at once: funnel, refusal reasons, agent comparison and stale leads.





Consultant, queueScreen 1/5
Get to know the contact, call and log the next step – in one view
Queue split by work state. To contact, scheduled, to review and done, each with a live count, so the consultant always knows what is next.
One-click “Next contact”. Keeps the calling rhythm without going back to a list.
Qualification facts above the fold. Fit, research confidence, call attempts and owner – the four things needed before dialling.
Calling sits next to the context. In-browser telephony; only the assigned consultant can call and log a result, others get a read-only preview.
Consultant, contact cardScreen 2/5
Everything needed for a warm call, in reading order
Research first. Company profile and areas of activity explain why this contact matters before the call starts.
Relationship history. Previous registrations and the CRM link prevent cold pitches to existing clients.
Chronological contact log. Every call attempt, e-mail and note with author and time – handover without losing context.
Manager, dashboardScreen 3/5
Where leads get lost – and why
Today at a glance. Today’s batch, leads in progress, confirmed visitors, hot leads and refusals.
Funnel counted by stage transitions. A lead that was confirmed and later refused counts in both places, so drop-off between stages is honest.
Refusal reasons as input. Grouped reasons become material for improving the call script.
Agent comparison and stale leads. Workload, confirmations and conversion per agent, plus leads with no movement for over 7 days.
Sales rep, boardScreen 4/5
A sales board that starts where qualification ends
Stages from the real process. Interested in offer, offer sent, negotiation, form signed – with counts per column.
Cards carry the deal context. Company, contact person, event and requested booth size, visible without opening the card.
Time in stage. How long a lead has waited, so nothing goes cold unnoticed.
Interaction states, empty viewScreen 5/5
Empty states that explain the process
Not just “no data”. The empty board tells the sales rep that contacts appear here once a consultant hands them over.
What it enables
- One workflow from the first call to a signed form, with a clean handover from consultant to sales rep.
- Views and permissions tailored to consultants, sales reps and managers.
- Managers see where leads drop out and why – input for improving the call script.
- Duplicate and concurrent-edit protection keeps shared data reliable.











