Stop guessing where revenue is stuck.
I help service businesses find where revenue is stuck, 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 revenue journey
The constraint is usually after first contact.
A lot of businesses assume the problem starts at the top of funnel. In practice, revenue often gets stuck after someone enquires, when the next step is slow, unclear, or poorly owned.
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 bottleneck 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. Enquiries were coming in. Interest was there. But somewhere between the first touch and the next commercial decision, good opportunities were getting stuck.
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 constraint because reporting stopped at "lead generated."
My background sits across digital transformation, CRM, lifecycle marketing, MarTech, reporting, 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.
Featured venture: 2nd Bell.
Revenue constraint review
2nd Bell helps service businesses find where revenue is stuck and what to fix first.
Many companies assume they need more leads. But often the real issue is what happens after someone enquires, or after a quote, or after the first sales conversation.
2nd Bell looks at the journey from spend and source quality through enquiry, response, booking, quote, payment, and repeat revenue. It uses weekly signals to show the current constraint so the team can make one clear monthly decision about what to fix first.
Revenue constraint design, supported by AI where it earns its place.
AI is part of the work, but it is not the magic trick. The value is making the revenue journey visible, accountable, and easier to run. Once the constraint is clear, AI can help with follow-up, routing, reporting, and CRM hygiene. If the workflow is broken, AI just creates more noise faster.
Experience behind the point of view.
Digital transformation and operating design
Years spent working where strategy, systems, teams, and execution all have to line up in the real world.
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.
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
Revenue constraint 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 revenue constraint first?
Because a lot of businesses are already paying to generate interest. The faster win is often fixing the bottleneck 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 constraint design. That includes CRM thinking, lifecycle and reporting context, operating discipline, and AI architecture where it supports commercial execution.
If revenue is getting stuck, start there.
That is the work 2nd Bell is built to do. Find the constraint, make the handoff visible, fix the follow-up system, and then decide where AI belongs.