Founder of 2nd Bell

Founder of 2nd Bell. AI architect for revenue workflows.

I help service businesses find and fix the hidden gaps between first enquiry and booked conversation, using practical workflow design, CRM thinking, and AI where it actually helps.

In short

Most businesses do not need more leads first. They need to stop losing the leads they already paid for.

Scroll to follow the handoff

The leak is usually after first contact.

A lot of businesses assume the problem starts at the top of funnel. In practice, good opportunities often go quiet after someone enquires.

Forms, WhatsApp, referrals, email, paid campaigns, and sales follow-up can all be active at the same time, but response speed, ownership, CRM visibility, and follow-up rhythm are still weak. Reporting says "lead generated" and the actual handoff disappears from view.

Why I started 2nd Bell.

I did not start 2nd Bell because the world needed another AI consultancy.

I started it because I kept seeing the same commercial leak. Businesses were spending money on ads, content, referrals, partnerships, and sales activity. Leads were coming in. Interest was there. But somewhere between the first enquiry and the booked conversation, good opportunities were going quiet.

Sometimes the response was too slow. Sometimes ownership was unclear. Sometimes WhatsApp, email, CRM, and sales follow-up were all telling different stories. Sometimes nobody could see the leak because reporting stopped at "lead generated."

My background sits across digital transformation, CRM, lifecycle marketing, MarTech, and AI workflow design. Over time, that made one thing obvious: more automation does not fix a broken handoff. It often exposes it. 2nd Bell is my focused answer to that problem.

AI architecture, applied to revenue workflows.

AI is part of the work, but it is not the magic trick. The value is making lead handling visible, accountable, and easier to run. Once the workflow is clear, AI can help with follow-up, routing, reporting, and CRM hygiene. If the workflow is broken, AI just creates more noise faster.

Lead leakage reviews
Revenue workflow design
AI-assisted follow-up systems
CRM visibility and hygiene
Email and WhatsApp handoffs
Founder and operator advisory

Experience behind the point of view.

1

Digital transformation and operating design

Years spent working where strategy, systems, teams, and execution all have to line up in the real world.

2

CRM, lifecycle marketing, and MarTech

A practical view of what actually happens after demand is created, where follow-up breaks, and what visibility leaders usually do not have.

3

Reporting, workflow visibility, and APAC operating context

Enough time inside dashboards, handoffs, and regional operating realities to know that "poor conversion" often means a broken workflow, not weak demand.

AI workflow design with restraint

AI belongs in the workflow when it makes the process faster, clearer, or more accountable. Not before.

Read the full background

What To Know

Who this is for

Service businesses, founders, and operators with live demand but weak handoffs after first contact.

What the work covers

Lead leakage reviews, CRM and follow-up workflow design, and practical AI support where it helps.

What matters most

Visibility, accountability, and a workflow the team can actually run.

A few useful questions, answered clearly.

Why lead leakage first?

Because a lot of businesses are already paying to generate interest. The faster win is often fixing the leak between enquiry and booked conversation before buying more traffic.

Where does AI fit?

After the workflow is clear. AI can support routing, follow-up, reporting, and hygiene, but it should not be used to hide a broken process.

What is the broader capability behind 2nd Bell?

Revenue workflow design. That includes CRM thinking, lifecycle and reporting context, operating discipline, and AI architecture where it supports commercial execution.

If leads are coming in but conversations are not getting booked, start there.

That is the work 2nd Bell is built to do. Find the leak, make the handoff visible, fix the follow-up system, and then decide where AI belongs.