Diagnose
We review how enquiries move through your business and where momentum starts breaking.
HOW 2ND BELL WORKS
A clear path from unclear follow-up to a cleaner revenue workflow.
2nd Bell starts by finding where qualified demand loses momentum, then helps fix the first practical workflow that improves response, ownership, follow-up, and visibility.
We do not start with a platform decision. We start with the current lead flow and the points where buyers are quietly going cold.
Process View
Review to measure, in four stages.
Four-stage path
01
Stage 01
Review
Current flow checked
02
Stage 02
Score
Gaps made visible
03
Stage 03
Fix
First workflow improved
04
Stage 04
Measure
Change tracked clearly
The process is designed to move from diagnosis to action to measurement without jumping straight to tools or a bigger platform decision.
THE SIMPLE VERSION
Diagnose the breakage. Fix the first workflow. Measure what changes.
Fix
We define and build the first workflow worth improving, without adding unnecessary complexity.
Measure
We track response, ownership, follow-up, booked next steps, and whether the process is easier to trust.
PROCESS
From first review to first fix.
The process is deliberately narrow. The goal is not to redesign the whole business. The goal is to find the highest-value follow-up gap and make it visible enough to fix.
01
Lead Leakage Review
A short fit check to understand your enquiry flow, current follow-up process, and whether the sprint is worth doing.
02
Current flow mapping
We map the actual path from enquiry to response, ownership, follow-up, and booked next step.
03
Lead Leakage Score
We score the key gaps across capture, speed, routing, ownership, follow-up depth, messaging, CRM discipline, and visibility.
04
Priority fixes
We rank the most important gaps by commercial impact, not by tool preference or internal politics.
05
First workflow build
We design and build, or prepare, the first practical workflow to improve response, ownership, follow-up, and visibility.
06
Review and optimise
We review what changed, what still feels manual, and what should be improved next.
FIRST STEP
The first review is a fit check, not a sales trap.
The first call is designed to understand whether your follow-up system is actually the problem. If the sprint is not useful for your situation, we will say so.
Context
What you sell, who you sell to, and where enquiries come from.
Current flow
How enquiries move through forms, email, WhatsApp, CRM, spreadsheets, or people.
Break points
Where response, ownership, follow-up, or visibility usually fails.
Fit decision
Whether the Lead Leakage Sprint is the right next step.
30-DAY SPRINT
A focused sprint built around the first useful fix.
The sprint is designed to get from unclear follow-up to practical action within 30 days.
Week 1
Map the current flow
Review enquiry sources, CRM or spreadsheet setup, inboxes, WhatsApp process, forms, routing, and follow-up behaviour.
Week 2
Score the gaps
Identify where opportunities slow down, lose ownership, or fail to progress toward a booked next step.
Week 3
Design the first workflow
Define the handoff rules, follow-up rhythm, scripts, automation points, and reporting view needed to fix the biggest bottleneck.
Week 4
Build or prepare the first fix
Implement the first workflow where possible, or prepare a clear implementation-ready workflow spec if the build needs additional scope.
Scope Note
Some builds may need extra scope if they require complex CRM configuration, custom integrations, or multi-market rollout.
OUTPUTS
What you leave with.
The deliverables are designed to make the follow-up problem visible and actionable.
Lead Leakage Score
A practical score of response, routing, ownership, follow-up, CRM discipline, and automation gaps.
Leakage Map
A clear view of where enquiries slow down, disappear, lose ownership, or fail to reach a booked next step.
Priority Fixes
A ranked list of the gaps most likely to improve commercial outcomes first.
First Workflow Plan
A practical recommendation for the workflow worth fixing before anything else.
Operating Rhythm
A simple way to keep response, follow-up, ownership, and visibility from slipping again.
SCOPE GUARDRAILS
What this is not.
The process works because it stays focused. We do not pretend every lead problem needs a huge transformation project.
This Is Not
A full CRM migration
A paid ads management package
A generic AI strategy workshop
A custom software build
Unlimited automation requests
A replacement for sales ownership
A dashboard project nobody owns
An attempt to automate a broken process before clarifying it
If the first workflow proves valuable, we can scope a larger implementation path after the sprint.
CLIENT INPUTS
You do not need perfect systems. You do need access to the current reality.
The work is only useful if it reflects how enquiries actually move through your business.
Website forms or enquiry paths
CRM, spreadsheet, or pipeline screenshots
Example emails or WhatsApp follow-up flow
Lead source overview
Current response process
Sales handoff rules, if any
Sample reports or dashboards, if used
Approximate monthly enquiry volume
Reassurance
No sensitive access is needed before the first review. Access requirements are agreed only if the sprint moves forward.
TOOLS, CHANNELS, AND AI WORKFLOWS
We work around the systems your team actually uses.
Most follow-up problems do not live inside one clean platform. They usually sit across a mix of tools, channels, people, habits, handoffs, and half-used automations.
2nd Bell starts with the process first, then looks at which tools can support it. That may include CRM cleanup, automation, AI-assisted follow-up, inbox workflows, reporting, or better handoff rules.
Lead channels
Website forms
Email
WhatsApp
LinkedIn
Paid ads
Referrals
Landing pages
Calendly
CRM and pipeline tools
HubSpot
Salesforce
Pipedrive
Zoho CRM
Airtable
Google Sheets
Notion
ClickUp
Monday.com
Automation and integration tools
Zapier
Make
n8n
Airtable Automations
HubSpot Workflows
Google Apps Script
Webhooks
APIs
AI and workflow tools
ChatGPT
Claude
Gemini
Perplexity
Microsoft Copilot
Google AI Studio
OpenAI API
Anthropic API
Custom GPTs
Claude Projects
NotebookLM
Cursor
Codex
Relevance AI
Lindy
Gumloop
Relay.app
Vector databases
RAG workflows
Sales and outreach tools
Apollo
Instantly
HeyReach
Clay
Lemlist
Smartlead
Mailchimp
Brevo
Customer.io
Intercom
Tidio
Reporting and visibility
Looker Studio
Google Analytics
Google Tag Manager
HubSpot Reports
Salesforce Reports
Airtable Interfaces
Sheets dashboards
Power BI
Metabase
Tool coverage depends on access, complexity, and the workflow being fixed. The sprint starts with the process, not the software.
These are examples of systems and tools 2nd Bell can review, work around, connect, or consider depending on the workflow. They are not a claim of official partnerships or deep end-to-end implementation in every platform listed here.
WHAT COMES AFTER
Stop, optimise, or scope the next fix.
The sprint is designed to create clarity without locking you into a huge project.
Stop with the score
You keep the score, leakage map, priority fixes, and first workflow recommendation.
Continue monthly optimisation
Use the monthly support period to improve follow-up rhythm, reporting, and team adoption.
Scope a larger implementation
If the first workflow proves valuable, we can scope a larger CRM, automation, or visibility improvement.
FAQ
Questions about the process.
Do we need a CRM before working with 2nd Bell?
No. Some teams use a CRM, some use spreadsheets, inboxes, WhatsApp, or a mix. The first step is to understand the current flow.
Do you need access to our systems?
Not before the initial review. If we move into the sprint, we agree what access is needed. In many cases, screenshots, walkthroughs, and sample flows are enough to begin.
Will you recommend a new CRM?
Only if the current setup is clearly blocking the workflow. We do not start by pushing a platform.
Can you work with WhatsApp-led sales flows?
Yes. For many Hong Kong and APAC teams, WhatsApp is part of the real sales process. The issue is usually ownership, follow-up, and visibility.
Is this an AI automation project?
Not by default. AI may help later, but only once the workflow is clear. We do not build AI agents just because they sound impressive.
How long does the sprint take?
The core sprint is designed around 30 days, depending on access, complexity, and how quickly inputs are provided.
What happens if the problem is demand, not follow-up?
Then the sprint may not be the right next step. We will say so during the review.
What happens after the sprint?
You can stop with the outputs, continue with monthly optimisation, or scope a larger implementation if the first workflow proves useful.
Ready to see where the process is breaking?
Book a short Lead Leakage Review and find out whether your follow-up system is worth fixing before you spend more on ads, tools, or headcount.
No CRM migration pitch. No long-term commitment from the first review.